TDD in Legacy Code - E2E Tests

In Legacy Code, E2E Tests are often performed manually. This makes it inconvenient to jump to introducing Acceptance Tests. Let's see how we can introduce automated E2E tests as a preparatory step.

🔒Hello, this is Valentina with a premium issue of the Optivem Journal. I help Engineering Leaders & Senior Software Developers apply TDD in Legacy Code. This article is part of the TDD in Legacy Code series. To get these articles in your inbox every week, subscribe:

---

Legacy Code has Manual E2E Testing

In Legacy Projects, QA Engineers often perform manual E2E tests based on written test procedures.

Hard to jump to ATDD with Manual E2E Tests

Like E2E Tests, Acceptance Tests test the functionality from the End User perspective (except that Acceptance Tests use External System Stubs rather than External System Test Instances).

It’s very hard to jump straight into writing Acceptance Tests retroactively when there aren’t even any automated E2E tests in place.

Convenient to automate E2E Tests before ATDD

It’s convenient to start with automated E2E Tests, and then transition to Acceptance Tests, by swapping out the External System Test Instances with External System Stubs).

Here are the steps for writing E2E Tests in Legacy Code. You’ll get tasks to implement in your GitHub Sandbox Project. I’ll review & provide feedback in the comments: ⬇️⬇️⬇️