Implementing Automated Tests
Learn about delayed and early automation.
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 to engineers until they resolve the issue and redeploy the application to let the testers verify it again. As you can imagine, this back-and-forth movement yields an