Implementing Automated Tests
Explore strategies for automated testing in software development, focusing on both delayed and early automation. Understand how early automation improves collaboration, reduces rework, and helps deliver higher-quality software efficiently.
We'll cover the following...
Most teams prefer to write automation scripts after development is complete; only a few know techniques to tackle this exercise in parallel with development. I will explore both options in the next sections under delayed and early automation topics, respectively.
Delayed automation
A delayed test automation process is straightforward. First, developers build a new functionality; afterward, testers write test cases and automate them. Since the automation takes place later in the flow, I call it delayed.
The simplicity of the described approach makes it most popular among development teams. However, you must know that there are downsides to this process:
- When testers start writing test cases, they often discover edge cases that developers missed during coding. This finding takes work back