TDD in Legacy Code - Component Tests - Backend
How can Backend & Frontend teams get isolated feedback whether their part works, without waiting for the slow Acceptance Tests?
🚀 Join the ATDD Accelerator waitlist
🔒 Hello, this is Valentina with a premium issue of the Optivem Journal. I help Engineering Leaders & Senior Software Developers apply TDD in Legacy Code.
Testing the Frontend in isolation
Previously, in Frontend Component Tests in Legacy Code, we saw that the Frontend team can get feedback whether the Frontend works in isolation, by stubbing out the Backend. This means they don’t have to wait for the Backend team.
Testing the Backend in isolation
Similarly, the Backend team can get feedback whether the Backend works in isolation, by stubbing out External Systems. Backend Component Tests are independent of Frontend Component Tests, hence can be written in parallel.
Here are the steps to introduce Backend Component Tests in Legacy Code. You’ll get tasks to implement in your GitHub Sandbox Project. ⬇️⬇️⬇️