Peddle - The State of Test Automation in 2017

This was a talk I did on the current state of test automation at Peddle in 2017. If you have any questions, feel free to reach out to me on twitter.

Transcript

1. The State of Test Automation eniedojadlo evanniedojadlo
2. Where were we before test automation? • Zero automated tests • Our “test coverage” was manual • The idea of a regression suite is to kickoff all of those tests on production as well as staging
3. What’s our current test automation stack?
4. • 84 UI tests that run nightly • Looking forward, planning test automation based on priority which can be viewed in the automated test guide • Developing critical and major regression tests which will be added to the regression suite • Developing UI tests for each Sprint How many UI tests do we have?
5. • Weekly and daily data generation on staging which is being added within the next sprint How many integration tests
6. • We would want to focus unit tests on priority items and go down from there • Let’s not focus entirely on coverage but instead focus on the value of the unit test How many unit tests?
7. • Indicates that the problem has been addressed or was due to a page timeout (we are working on improving our staging environment) • Indicates that this is a reviewed and confirmed problem and needs to be resolved (brittle test, bug, integration failure, etc.) ChatOps workflow
8. • Increase staging server performance as this directly correlates to load testing • Adding more tests into the release pipeline, I have created drafts within the test automation roadmap • Add unit tests to CI, this will be done on code check-in • Add specified UI automation to staging environment e.g. run unit tests → run UI tests What do we need?
9. • Load testing on staging using jmeter/blazemeter • Review visual automation when we have a strong set of UI automation actively running • Update the URL so that we have production tests running as well as staging • Various cleanup and refactoring e.g. splitting up our page objects, restructuring our directories What do we need?
10. • Automate the majority of our regression suite What do we need?
11. Questions?