Selenium Timeline
-
Mike decides to use Selenium as their testing framework
Before sprints begin
-
Charlie and John try to set up infrastructure for Selenium Sprint #1
-
Engineers are done with the infrastructure Sprint #2
-
Every engineer can automate 2-3 tests every day if there are no tests that needs to be fixed. Sprint #3
-
Sprint #4
-
...
-
Sprint #8
-
30%Got to 30% test coverage Sprint #9
-
Setting up the GitLab CI/CD Pipeline Sprint #10
-
Never ending cycle: Run tests -> Fail -> Fix the tests -> Retry -> Repeat.
Results:
Get to 30% coverage in 5 months Test scripts clog the deployments 90% Test coverage is impossible to achieve!