Test automation is as fundamental thing than code.
If you write code, you also write tests.
Plan and budget time for creating and fixing tests
How much you should automate?
I’ve always said ..
“automate everything. Aim for 100%”
I might be wrong..
Forget Complete Test Automation
It is a lot of work to maintain tests.
If you try to automate everything, it might be that you won’t get your investment back.
Find the most critical paths that gain most value.
Any quick wins?
Test automation is investment
You won’t get fast return.
You won’t get benefits on current release.
You’ll get your investment back, when running the tests on several releases
Do small investment first
LearnTry things
Maintenance
Maintenance is the killer of everything
It is better to have less tests that are easy to maintain and work than a lot of tests that are unstable
What tools you should use?
Use tools that..
are opensource
Developers are willing to use and learn
Support the language your developers use ..
Who should do the automation?
The best automation results are lead by developers who have put energy into it.
Don’t outsource test automation effort
consultantsother teamsqa department
The best automation results are lead by developers who have put energy into it.
Implement gatekeepers
“If any of the tests have failed, it will send a “Failure” status to the GitHub API which stops that specific pull request from being merged into our master branch. The second status is a master branch status check which prevents all pull requests from being merged when the