Testing policies

Unit Tests & Code Coverage

The first type of test we use in our project are unit tests.
They are here to make sure our code works as intended and don't have sides effects.
Concerning coverage, there is only one category of code that needs a full code coverage, and that is the libraries.
The CI/CD runs them at varying levels of expectancy depending on the branch.

for a deep dive into our unit testing refer to the following document : unit testing

Integration Tests

Integration Tests are here to ensure that different components or systems work together as expected. In our case it we have two kinds of integration test:

data relations

• Online server => local database
• Local database => backend
• backend => frontend

system relations

• WIP

The first category is especially important in our project because each relation in crucial to the reliability of our application.
For example if the backend recieve all the rights information and analyze a potential threat but doesn't report it to the user, the software becomes useless.

for a deep dive into our integration tests refer to the following document : integration testing

End-to-End Tests

Simulate real user scenarios to test the full application flow

WIP

Security & Performance Tests

Evaluate system speed, responsiveness, and stability under load.
Test for SQL injection.

WIP