Details of the testing process and policies ensuring that new features are accompanied by corresponding unit tests to maintain comprehensive test coverage.
Midaz is dedicated to maintaining high standards of software quality. To achieve this, we use both unit and integration tests throughout our codebase. These tests are integral to our development process, ensuring that each component functions correctly and integrates seamlessly.
Running Tests
To execute the tests, use the following command in your terminal:
make test
This command runs the predefined test suite, which includes both unit and integration tests.
Continuous Integration
- GitHub Actions: Our tests are integrated with GitHub Actions, automatically running as part of our continuous integration pipeline. This ensures that all code commits meet our quality standards before merging.
Unit testing policy
- New Features: As part of our testing policy, any new feature introduced in Midaz must include corresponding unit tests. This practice helps ensure that new code does not negatively impact existing functionality.
- Test Coverage: We aim for comprehensive test coverage as a benchmark for software quality.
Test Outputs
- Terminal Outputs: Test results appear directly in the terminal, providing developers with immediate feedback to quickly identify and resolve issues.
- Automated Test Pipeline: Tests also run automatically as part of our continuous delivery pipeline, supporting consistent quality and reliability across the software.