Test Strategy

Test Approach

Quality Assurance will be implemented adhering to the Shift Left testing model. This is focused on performing testing as early as possible in the software development lifecycle to validate functionality being delivered is ‘production ready’. This reduces costs by identifying defects earlier, where remedial actions are most cost effective and decreases the possibility of project delay by taking a proactive approach towards quality assurance.

Test Principles

• Unit and Integration tests must always accompany any development work in a pull request.
• The scope of testing is agreed between the development team through example mapping and amigos sessions.
• Tests should be self documenting. BDD will be used for integation tests and name decorators for unit tests.
• Any manual testing will be documented, evidence gathered and attached to the Repo for full visibility.
• Test Automation is favoured over manual testing, with an automated regression suite built iteratively which runs on every PR.

Functional Testing

Unit Tests

• Use NUnit
• Mock out external dependencies

Integration Tests

• Use NUnit
• Use Speclow BDD to make tests self documenting
• Use FluentAssertions
• Use dockerized external dependencies such as MongoDB, RabbitMQ and MinIO
• Local execution will be carried out by using a docker-compose file
• Pipeline execution will use GitHub services to create external dependencies and services will be created using docker-compose.test file

End to End Tests

Manual Tests

Non Functional Testing

Performance Tests

Security Testing

SCA

License Scanning

SAST

DAST