- Training Calendar
- Live Online Training
- At A Glance
- Our Team
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
3. Test Automation
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
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
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.
Anil Jaising is a Certified Scrum Trainer®, Certified DevOps Institute Trainer and a Certified Training from the BACK of the Room – Virtual Edition Trainer. Anil teaches Certified Scrum Master (CSM) and Certified Scrum Product Owner (CSPO), Advanced Scrum Master (A-CSM) workshops from Scrum Alliance He also teaches Training from the BACK of the Room In Room and Virtual Edition). He is also the chief product owner of a telemetry plugin At A Glance on Atlassian Jira.