Continuous Testing is challenging. These six best practices can help steer the path
For any highly competitive industry that relies on a smooth and stable user experience, it is vital that their development teams accelerate release cycles, lower operating costs and ultimately reduce risks. Continuous testing is one way companies can achieve these objectives.
Test Plans: Product level test plans provide overall guidance for product test strategies and policies and indicate the strategy and contract for measuring test coverage.
Test plans should be reviewed by product developers, architects, test engineers and operation staff.
2. Test Coverage Metrics to consider
- Requirements coverage %
- Test Plan coverage %
- Code coverage %
- Function coverage %
- Artifacts coverage %
- Code module coverage %
- Dependencies coverage %
3. Test Automation
- Automation tests that offer the highest level of coverage of the most risky application behavior for the least amount of automation efforts
- 85% to 100% of test automation should be typical. Minimize manual tests
- Delivery and deployment tests are usually fully automated
4. Test Versioning
Tests are as important as the code. All version of test artifacts (test plans, test suites, test cases) should be kept in a secure repository.
A test management database (TMDB) is a repository for meta data that describes tests, test schedules and test results. Examples of meta data include test attributes and tags that describe the purpose and version of a test and test results, the time to execute a test and verdict history. Configure the TMDB as a service.
5. Test Environment Orchestration
- Automatically setup the test environment and resources (physical and virtual) to match the requirements of a test
- Automatically execute the tasks to setup the environment
6. Test Triggers
Test framework should be integrated into the overall continuous delivery pipeline and should be triggered by the previous step in the pipeline
Scrum, Product Management, and DevOps: Simplifying the jargon
The internet and social media are full of Agile, Scrum, Product Management, and DevOps jargon, including incorrect and misunderstood concepts. This could be problematic for a learner seeking knowledge. Without a course with Scrum Alliance, Scrum.org, or DevOps Institute, this knowledge is difficult to achieve.
I would love to hear from you about what you would like us to add to this article that will help you better understand the product owner role. Please share your comments below.