@@ -10,6 +10,6 @@ In catch2, testing is particularly easy. For details, see the catch2 documentati
- Unit tests should be robust and run very fast.
- avoid extensive physics tests
- avoid statistical analysis with large number of events
-**-> test expected behavior and formulas with minimal input**
-**-> test expected behavior and formulas with minimal input**
- if needed, complicated input-output data/objects must be replaced with simplified (empty) testing counterparts to basically **only** test the basic expectations, not complex behavior.
- unit tests must be as independent of each other as possible. Ideally they only depend on exactly the code they are testing.
