The Test Cases and Scripts Episode

June 4, 2023

AI Summary

5 min read

In a world where testers spend months writing scripts only to discover the system has changed, the host of The Evil Tester Show argues that the entire edifice of test conditions, scenarios, cases, and scripts is a trap. He started his career taking it for granted that professional testing meant creating all of these artifacts, cross-referencing them to requirements, and tracking execution against them. "You couldn't raise a defect unless there's a test case to go along with it," he recalls. That process was so slow and maintenance-heavy that it led companies to conclude: if the only value from testing is following scripts, we can just automate all of it. The host's central argument is that these entities are logical concepts, not physical requirements, and that treating them as physical artifacts makes testing slow, brittle, and ineffective.

The Four Entities as a Derivation Chain

Continue reading the full summary in the app — free to try.

Read Full Summary →

Free • No credit card required

Listen to Audio Summary Open in App

Never miss an episode of The Evil Tester Show

Get every new episode summarized in your inbox — free, ~5 minutes to read.

No spam. Unsubscribe anytime.

What you'll learn

1 (00:00) **Introduction: The Four Test Entities** - The host introduces the core concepts of test conditions, test scenarios, test cases, and test scripts, noting they are logical concepts, not mandatory for effective testing.
2 (00:48) **The Problem with Tool-Driven Testing** - The host describes how early in his career, testing was entirely controlled by these entities and the tools that enforced them.
3 (04:05) **Test Entities as a Model of the System** - The host explains that test cases and scripts are essentially a model of the system, but a poor one.
4 (06:57) **Test Condition as a Logical Concept** - A test condition is a basis for testing, often mapping to an input, process, or output.
5 (09:13) **Test Scenario as a Collection of Conditions** - A test scenario groups related test conditions into a process-oriented view.
6 (09:58) **Test Case: Specificity and Bounding** - A test case takes a scenario and defines specific inputs and expected results.
7 (11:19) **Test Script: The Worst Concept in Testing** - The host argues that test scripts are the most damaging concept, reducing testing to unthinking step-following.

+ Full timestamped outline available in the app

Show Notes

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

Test Condition
Test Scenario
Test Case
Test Script

In my Testing I pretty much now have:

Test Idea
Test 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.