@@ -2,6 +2,8 @@ The tests depend on annotations to execute correctly. If you're not sure what an
The following annotations are used to setup some things before the tests actually run.
If you are creating a new test, all of the following annotations should be applied to the `public class` line at the top of the file unless otherwise specified.
## @GameTest
The GameTest annotation requires a String parameter. This parameter is the module that you are creating your test for. If you are creating your test in the GameShared module, your annotation line will look like the following: **@GameTest("GameShared")**.
...
...
@@ -9,3 +11,19 @@ This annotation initializes the logger and tells it where to log the data at. It
## Reset Annotations
There are various annotations throughout the codebase that are responsible for resetting different things. An example of this would be the **@ResetReportObserverConnector**, which simply resets the **ReportObserverConnector** singleton. This will be true for most of the other annotations with the word "Reset" at the beginning. There are some annotations that do more than just reset the singleton, but the point of them is to reset the singleton to an **initial** state. Sometimes this might also require adding things to the singleton.
