E2E Test Design Anti-Pattern: “Each test case, in one test script file, passed on its own but failed when run together”

Understanding and Avoiding Inter-Test Dependency Failures in Automated E2E test scripts

Non-Medium Members: Read this article for free on Substack.

In this E2E Test Design Anti-Pattern series:

• “Test script fails after the first successful run”
• “Each test case, in one test script file, passed on its own but failed when run together”
• “The full test script passes, but certain individual tests in it fail” (upcoming)

This article is based on my father’s new book End-to-End Test Automation Anti-Patterns, but presents simpler (and alternative) examples.

Announcing new book, “End-to-end Test Automation Anti-Patterns”

This article covers a common anti-pattern during developing automated End-to-end (E2E) tests scripts, where test cases in one test script file pass when executed independently, but fail when the test script is run together.

First, let’s go through an example user login test script, containing two…