In & nbsp; Part 1 of this series,we looked at the test automation pyramid and early triangle-shaped models that help teams visualize their test automation scheme. InPart 2,we ’ ll look at other framework you can use to talk about how to tackle the many challenge of test automation. 

The Agile Testing Quadrants model is useful for thinking about different character of tests, whether they should be automated, and who should participate in automate them. 

• We ’ ll explore variations on the basic Quadrants pattern that might help in different contexts such as continuous delivery.
  
  
• We ’ ll also enclose visual techniques to identify risks and dependencies to consider as you spring your automation strategy. 
  
  
• Finally we ’ ll revisit another adjustment of the test automation pyramid that can identify gaps in your chosen scheme and help you conform as you learn.

Watch the recorded webinar below:

Check out Part 1 and Part 3 as well!

Referenced Material:

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

More Agile TestingChapter on habituate models available athttps: //agiletester.ca/more-agile-testing-the-book/

A Practical Guide to Testing in Devops,Katrina Clokie,https: //leanpub.com/testingindevops

Discovery: Explore behavior using examples,Seb Rose and Gaspar Nagy,http: //bddbooks.com/

“ Lower level automation and testing? Be more precise! The automation Triangulum revisited… again! ” Toyer Mamoojee,https: //toyerm.wordpress.com/2018/10/16/lower-level-automation-and-testing-be-more-precise-the-automation-triangle-revisited-again

The Team Guide to Software Testability,Ash Winter and Rob Meaney,https: //leanpub.com/softwaretestability

“ Your mechanization testing strategy: pyramids, triangles and beyond ”, Lisa Crispin,