Skip to content

Testing Standards

Mike Lyttle edited this page Jun 24, 2021 · 1 revision

Testing Standards

Unit Tests

Relevant unit tests should be reviewed and created or updated as needed for every task that adds or modifies code.

A minimum of 80% line coverage is expected for both the front-end and back-end. Machine-generated files and pass-through controllers in the back-end can be excluded from coverage.

Components in the front-end should have unit tests for their functions, but the templates should be covered by UI Tests instead.

Functional Tests

Relevant functional tests should be reviewed and created or updated as needed for every user story.

Functional tests are separated into UI Tests and End-to-end Tests.

UI Tests

UI Tests should use fixtures to mock external calls and be written to ensure the application behaves correctly when it receives expected data.

End-to-end Tests

End-to-end Tests should minimize the use of fixtures and test the overall functionality of the application, including communicating correctly with external services.

Clone this wiki locally