- Approving Results
- Approved File
- Chain of responsibility (pattern)
- Code Coverage
- Combination Testing
- Comparator
- Continuous Integration
- Convention over Configuration
- Custom Asserts
- Diff Tool
- Disposable Objects
- Edge Case
- Happy Path
- Kata
- Koans
- Mutation Testing
- Namer
- Principle of Least Surprise
- RAII (Resource acquisition is initialization)
- Received File
- Reporter
- Scrubber
- Stringification
- System Under Test
- Test Framework
- test && commit || revert (TCR)
- Writer
- Yak Shaving
- Sayings
Sometimes referred to as Combinatorial testing.
See Testing Combinations.
See Custom Comparators.
Instead of asking the user to specify everything, we make assumptions based on common patterns, so code usually just works "out of the box". This tends to dramatically reduce the amount of clutter, makes things easier, and reduces the amount of surprises.
Objects that implement the RAII pattern.
See Disposable Objects.
This is a pattern where your object constructor opens a resource, such as memory, and your object destructor closes the resource.
This is also known as "Scope based resource management".
See Reporters.
See Using sub-directories for approved files
See Features - whose sections need to be moved around
See How to Scrub Non-Deterministic Output.
See String conversions.
The area of the production code that you are testing. See System Under Test.
- The tests test the code, and the code tests the tests
- Test until bored