Difficulty: intermediate
Estimated Time: 30 minutes


Welcome to the Yellow Belt DevOps Dojo Test Automation Strategies module.


The main aim of every software development team is to deliver high quality software to the business at an agreed cadence. Testing is performed in an attempt to ensure that the applications developed are defect free and that applications fulfill business expectations before they are deployed.

The primary objective of the "Test Automation Strategies" module is to help you to understand that a well designed test automation strategy is a key enabler of the speed promised by DevOps practices.

Inadequate planning is one of the main reasons for the failure of test automation initiatives. Test automation plans have to be detailed and realistic. Planning for 100% test automation from day one is an unrealistic, and depending on the test type, potentially an unachievable test automation objective.

Teams should set time aside to define a strategy documenting their approach to test automation. The aim should be to create a cost-effective test automation strategy underpinned by a data driven result-oriented approach.

The secondary objective is to give you an opportunity to virtually participate in a Test Automation Strategy creation real world scenario using Katacoda.

If you have not completed the Welcome module you should do so before continuing with the Test Automation Strategies module.

By the end of the module, you will be able to:

  • Explain the importance of defining a Testing Mission Statement.

  • Outline the challenges facing teams as they move to introduce test automation.

  • List test automation guiding principles.

  • Consider and evaluate different approaches to Test Automation.

  • Describe the test types that comprise the Test Automation Pyramid.

  • Articulate the need for and create a Test Automation Strategy.

  • Understand the implications of testing for each stage of the typical development life cycle.


Congratulations, you have completed the Test Automation Strategies module of the Yellow Belt DevOps Dojo Stripe 2

As per the challenge please set some time aside in your next team meeting to consider implementing or improving your teams' Test Automation Strategy.

That done, we recommend that you take the Test Automation Strategy Implementation module of this course next.

Test Automation Strategies

Step 1 of 13

The Need For Speed

The Pet Clinic development team have started to implement Test Driven Development (TDD). They are adding unit tests as they add new functions and features.

As is to be expected given they have only recently started with TDD the current test code coverage percentage is low.

They also have some automated functional tests with user stories in their backlog to create additional tests for a number of critical flows. As a result Tina and the testers still have to do a lot of manual testing for each release.

With the introduction of TDD and automated functional testing, the team is starting to see encouraging results. Some issues are being detected by tests ran from the team's continuous integration pipeline when developers submit pull requests. Results are however patchy with bugs and performance issues being detected in upper environments.

Paulo, following his regular product backlog grooming meeting with the business, explains to the development team that the pace of change is accelerating and that he expects that a monthly release will soon be no longer viable. He outlines that Brenda and the business are looking for weekly initially and ideally daily releases.

Paulo asks Adam for any observations he has on the performance of the application following the recent introduction of the Fair Trade Pet Products Line. Adam describes that they are seeing spikes in business around holidays, sales events etc., with some performance issues being experienced at peak times.

Paulo calls a meeting and asks Chun for her thoughts as to how the team can build on the progress shown to date and take the next steps in Test Automation.

This is Test Automation Strategies and these are the people that will create the Test Automation Strategy for the Pet Clinic team.

Chun DevOps coach supporting the transformation effort
Paulo Product Owner for the Pet Clinic application
Santhosh Scrum Master who is facilitating the DevOps Kaizen events
Adam IT Admin representative participating in the DevOps transformation.
Dan Developer creating working on the development team that produce the artifacts
Tina Tester responsible for ensuring the team build quality into software they produce
Selma Security Officer responsible for all things security
HAL White Hat Hacker seeking to find and expose security vulnerabilities to the team so they can address them
💡 TIP: Adjust the window size vertical scroller to make the module easier to read ◀▶