Testing methodology

This is the standard to the project's testing. Down below are when and how we write tests for our components. For more detailed information about how to write a specific test, you can read the specific test pages:

• Testing with xUnit
• Testing with Jest
• Accessibility Testing
• Testing Mobile Frontend

When to write test:

• The developer should NOT create tests for front end components, we should in those cases have manual interactive testing (From different developer).
• The developer should always create unit tests before writing the actual code.
• The developer should add the test to the regression testing suite. [WIP]

How we work with tests:

• Tests are a part of the definition done for every code task.
• No code should be merged or submitted as a pull request without relevant testing.
• Tests must be maintained when code is changed.
• A failing test should block the merge.
• Tests should be reviewed in a code review.
• Bug fixes should always include a test that tries to reproduces the bug.
• Regression tests must be update when new functionality is introduced.
• Test coverage is a team responsibility.
• Tests should be mapped to the requirement/issue they validate.