There's been a lot of exploration of the unit testing of the first module in the system, and that exploration has established some patterns that will appear frequently in unit testing of the other system code as it is written, so they will not be re-examined in any significant detail from this point on unless there's a significant new aspect to them.
Those patterns are as follows:
- Iteration over good and bad value lists that are meaningful as values for the member being tested:
- Standard optional text line values
- Standard required text line values
- Boolean (and numeric equivalent) values
- Metadata values
- Non-negative numeric values (for weight values, in this case)
- Verifying property method associations—getter methods in every case so far, and setter and deleter methods where they are...