Testing principles
Next to the GitOps principles, we have our own set of testing principles:
- Start small and iterateBetter to have some tests from the start than have none at all.
- Automate everythingAutomation leads to more efficiency and quality.
- Fail earlyTesting should start as soon as possible, this ensures robust software.
- Tests are deliverablesBy delivering a test, you can prove you tested the feature. The test can be re-used in later stages of development.
- Testing is a common responsibilityTesting should not be the responsibility of one person in the team, but a team effort.
Test process
Section titled “Test process”We encourage to use the following process when developing tests:
- Testing should be incorporated from the moment a new feature is designed.
- When refining a feature, the possibility for test automation should be discussed as well as the test scenario’s that are possible for that feature.
- Together with building the feature, the tests should be built and executed.
- The tests should be a deliverable when deploying a new release. That way clients can also run the tests in their pipelines.
