How to Optimize Automated Testing with Everyone’s Favorite Butler
Test automation best practices were discussed for Parallelizing tests with orchestrated Jenkins pipelines and using ephemeral test slaves, keeping the test jobs simple and self-contained within their test-data dependencies.
Andrew also covered the use of Jenkins to invoke test tools via plugins and scripts sourced from SCM.
Andrew addressed “Testing 101” (in today’s automation world) and walked through the shift-left paradigm in quality with the following aspects-
- Testers are developers
- Test code = production code
- Conway’s law
- Measure quality
- Link tests to use-cases
- Radical parallelization
- Fail faster…
- Kill the nightlies
- Copy artifact
Making sense of scattered test results is still a challenge… There still isn’t enough tooling or a solution to give you a “quality OK” sense every time something changes -
- Many test tools for each test levels, no single place to validate if “this release” is good to go live!
- Traceability, requirement coverage
- Minimize MTTR
- Have I tested this enough
- Support for failure analysis