The Evil Tester Show Alan Richardson

This episode covers the Test Automation Pyramid, created by Mike Cohen in 2008-2009 in the book "Succeeding With Agile". We will go beyond the diagram and look at the model that supports it. Then deep dive into the model to explore it's meaning in relation to Automated Execution Coverage, not Testing.


- The model was created by Mike Cohen in 2008-2009 in the book "Succeeding With Agile."


- The original model focused on UI, service level, and unit level automation.


- Over the years, different interpretations and variations of the model have emerged.


- The term "service level" in the model has led to ambiguity and different interpretations.


- The diagram in the model is a simplified representation of a deeper underlying model.


- The focus should be on achieving coverage at the most appropriate level in the system.


- The model addresses the importance of avoiding duplication and redundancy in automated coverage.


- The process and team structure can impact the effectiveness of the model.


- The model can be reframed as an automated execution coverage pyramid.

The most common Testing Entities that I've encountered over the years are:


Test ConditionTest ScenarioTest CaseTest Script

In my Testing I pretty much now have:


Test IdeaTest Log (Execution Log)

Is there any value in the original Testing Entities? There might be if we view them as logical concepts, but not really as physical artifacts.

Top 3 Phrases that should carry trigger warnings for the Test Community:


- Manual Testing


- Test Automation


- Quality Assurance


In this episode I'm going to talk about Manual Testing.


So that's your Trigger Warning.


And I'm going to talk about what we might want to say instead of "Manual Testing"

Episode 017 - Manual QA is Dead - The Evil Tester Show


Manual QA is dead. Companies are getting rid of their QA teams. Quality Control performed manually is phasing out of style. What can we do instead? Become coaches, assistants or advisors? We could become developers? Or we could be better testers. QA and Quality Control is not Testing. This might be how people learn.

In episode 16 of The Eviltester Show we are looking at Test Automation Biases, what they are, how to avoid them, and how to evaluate your own biases.


00:00 What is an Automation Bias?


00:29 Treat all opinions as biased


01:50 Automating a GUI is Slow and Flaky


03:36 Automate through the API


05:23 Code Free Automating is Bad


06:17 Tool X is Better than Y


07:04 Postman is Better than Insomnia


08:54 Python is Better than Java


10:24 Seeing Through Biases


12:52 Try it, then decide


13:17 Page Objects vs Screenplay


14:52 Take Responsibility


16:11 External Experience


17:02 Start Small, Make Progress


17:50 Do not ignore issues


20:34 Be Real rather than Believe


21:18 Keep Options Open


22:48 Be Aware of your biases


23:19 It takes time

In this episode we have a discussion of a UK government guide to exploratory testing.


https://www.gov.uk/service-manual/technology/exploratory-testing

The aim is not to criticise the document, the aim is to use it as a base from which to see how far our thoughts diverge or overlap with the document. I want to know what I can learn.


Show notes are here:


https://www.eviltester.com/show/015-exploratory-testing-gov/


This podcast, was originally released to Patreon supporters in January of 2019,


https://patreon.com/posts/what-is-testing-23907385

I read through the document and try to understand the intent and meaning behind statements and offer my own thoughts.