So your team have embraced automated testing and created a large suite of UI focused end-to-end tests. Now they take over an hour to run, they are brittle and consume hours of hours to update and fix. Meanwhile, every day the suite gets bigger and slower as more automated tests are added. What do you do? How can you keep the value of the automation you have created without having to throw everything out and start again?
Sometimes it’s easy to blame the tools, but have you stepped back and considered the design of your checks. Are they managing data correctly, do they have to carry out many steps to achieve their goal, are you simply testing too much in one automated test?
In this workshop, you’ll get to take part in fixing a suite of checks that suffer from common problems of brittleness; long build times, large maintenance costs and poor feedback. Throughout the workshop, you’ll analyse and evaluate automated tests to identify the various actions they carry out. Based on what you identify, we’ll explore and propose new design patterns and tools that will enhance your pre-existing test, then implement them. All without losing the value of the automated test. The skills you learn can then be adapted to your own suites of automated tests, to make them reliable, informative, speedy and maintainable.
By the end of this workshop, participants will be able to:
This course is designed for Developers, SDETs and Automators who are comfortable with programming and have experience of automating end-to-end UI tests.
Please bring a laptop, OS X, Linux or Windows that you can install software on and connect to easily wifi with.