Unit tests for SuiteName

[russell-taylor]

Generate artificial cases that you know the answers to

• Mean location for each cluster should be assigned to that cluster
• Test points near the average location of two cluster means to make sure they are properly assigned to the nearest
• Past the boundaries on each axis change the inside/outside behavior

List cases that should be tested and Jane and Dave could find files that test these cases

[russell-taylor]

Code paths to test

• Things triaged first
• Things in ordinary cluster
• Dominant satellite situation; near dominant, near satellite, or near the middle
• 7d distance math may exclude or include things that were judged the other way

[russell-taylor]

Note from Ken: Code paths that should be tested in Suitename:

1. Triage on each of the seven angles.
2. Only one match.
3. Multiple matches, none of them dominant.
4. A dominant but we are not near a satellite.
5. Dominant and satellite, but it's not between them, dominant is selected.
6. Dominant and satellite, it's not between them, satellite is selected.
7. Dominant and satellite, it's between them, dominant is selected.
8. Dominant and satellite, it's between them, satellite is selected.
9. No match.

And orthogonal to all those considerations: A. Outlier becomes assigned through 7D distance calculation. B. Accepted suite becomes de-assigned through 7D distance calculation.

[russell-taylor]

Test angles that are too large in addition to angles that are too low

[russell-taylor]

Add tests for -nowannabe and -string