Lesson 13 - Putting Operability Into Practice - Matching Testing Activities to Operability Improvements

🙋 Questions
1

Title: Matching Testing Activities to Operability Improvements

Time: 30 mins - 1 hour

Introduction: Balanced testing is really important to improve your product and team testing culture. All automation means you miss the subtle issues that exploratory testing helps you find for example. Time to get specific with our operability improvements, matching them to the types of testing you need to improve. To do this, I take each category of the runbook template (from the Using Runbooks lesson) and match to the following types:

  • Exploration
  • Automation
  • Performance and Load
  • Resilience

Purpose: Create a list operability improvements matched the testing activities you wish to establish or improve. This will help you and your team with what to tackle first.

Activity:

  1. Review your current testing and identify any gaps you have in the types of testing you do. If you have been trying to implement load testing without much success for example.
  2. Review each runbook category and match to the following areas:
    • Exploration
    • Automation
    • Performance and Load
    • Resilience
  3. Write up your findings and add them to the README.md file in your application repo (or wherever your team stores its documentation.