Put your TestOps shoes on! Improving Quality by Process Automation

Automate everything! That’s the most suitable description of DevOps culture. The culture that quickly created job position with the same name. Position, mostly focused on broadly defined automation, leading to fast product delivery. And the division was pretty simple: DevOps = Process automation, QA = Test automation. But is it the right approach? What about (still more and more) popular “(Dev)TestOps” term?

Classical testers are now also very often responsible for set-up and maintenance of the major part of Continuous Integration or Continuous Delivery environment (especially test automation part). The main problem from the business perspective is, like always, time! E.g. many start-up and companies in a phase of early, dynamic growth cannot afford to waste too much time on test automation. How to speed up the delivery process in that cas? How to quickly generate a valuable increment?

I’ll show you how to improve and speed up testing and delivery process by clever automation in 3 steps:

  1. Automation supporting manual regression testing activities
    • One Click test environment setup
    • Preparing fully readable and executable test cycles and test cases
    • Ensuring that unchanged component is not double-checked or unnecessarily tested
  2. Automation maintaining project workflow, transitions, and statuses
    • Recognizing when an issue is QA ready vs. when it is dev ready
    • Avoiding (very!) common misunderstanding regarding testable issues
    • Assuring that functionalities have been released without reading documentation and changelogs
  3. Automation enhancing bug catching and reporting during testing or normal application usage
    • Comprehensive incorporation of all crashes with bug reporting system
    • Immediate notification based on priority and severity threshold level
    • Automatic preparation and update of reported bugs, including necessary statistics

All of that in the context of 5 good (TestOps’) friends: Test Management Tool (Zephyr), Project Management Tool (Jira), Crash & Log Reporting System (Crashlytics), Communication & Notifications Channel (Slack) and Continuous Integration Tool (Jenkins).

 
 

Outline/Structure of the Case Study

  1. Introduction do TestOps concept - 10min
  2. Continuous/synthetic monitoring - 2-3min
  3. Why we want to automate everything - 2-3min
  4. Automation supporting manual regression testing activities - <10min
    • One Click test environment setup
    • Preparing fully readable and executable test cycles and test cases
    • Ensuring that unchanged component is not double-checked or unnecessarily tested
  5. Automation maintaining project workflow, transitions, and statuses - <10min
    • Recognizing when an issue is QA ready vs. when it is dev ready
    • Avoiding (very!) common misunderstanding regarding testable issues
    • Assuring that functionalities have been released without reading documentation and changelogs
  6. Automation enhancing bug catching and reporting during testing or normal application usage - < 5min
    • Comprehensive incorporation of all crashes with bug reporting system
    • Immediate notification based on priority and severity threshold level
    • Automatic preparation and update of reported bugs, including necessary statistics

Learning Outcome

  • TestOps concept and general rules
  • Understanding that Assuring Quality not always means-testing. It also not necessarily equals test automation.
  • Real examples of how quality can be improved by Process Automation! That consists of:
    • Supporting manual testing activities
    • Maintaining project workflow & transitions
    • Enhancing bug catching & reporting while testing

Target Audience

Automation QAs, DevOps, Test architects, TestOps

Prerequisites for Attendees

Good to be familiar with DevOps approach

schedule Submitted 10 months ago

Public Feedback