When you create a new set of tests, you must add it to the test suite for that project. Those suites are structured to match the layout of the project to make it easy to check that all of the suites are added. For example, look at AllServerTests in the GameServer project. Notice that the tests are in labeled sections for each package and those packages are in alphabetical order. In each section, the tests are also in alphabetical order. This makes AllServerTests match the structure you see in the package explorer in IntelliJ. So, it's really easy to run down that list and make sure it matches what is in the test suite.
Sometimes, tests require other classes that should NOT be in the test suite. In this case, put that class in the list, but comment it out. Like this:
```
// edu.ship.engr.shipsim.model.cheatCodeBehaviors
BuffBehaviorTest.class,
// MockCheatCodeBehavior.class, is used by tests, but isn't a test itself
```
That way, when we try to verify that the test suite matches what's in the project, we know not to worry about that class not being in the list.
