Testing Standards - Pasarus/FelineAdoptionAgencyMajorProject GitHub Wiki

All committed code must contain it's relevant tests. Because this project will not be utilizing pull requests for checks, it is vital that tests are up to date to check for regression in functionality.

• UI Integration Testing can be written by hand or created using the Espresso test recorder for Android. Specifically as long as functionality is tested properly it does not matter. However Espresso test recorder use must be noted in the generated files or functions.

• Unit tests should be written with the aim to cover most branches of code execution, maximizing test coverage to time spent testing needs to be taken into account, a minimum coverage of 80% of none UI code should be tested.

• Acceptance tests should be drafted in a customer friendly manner.