ConTEST 2021 Conference Website - click here

Test automation seems to work well when you think of regression testing, especially when CI/CD processes are concerned. But do we always need to automate everything to cover a huge web application with your tests? Here your testing challenges aren’t about testing everything again and again. They’re about continuously testing changes where errors are introduced that can have an impact on customer experience. And what if automated functional testing and visual comparison are not enough and you still find bugs with new releases? Or perhaps your automated testing is too detailed and too expensive to create, maintain and review? How do you make use of test automation so that it’s effective, without investing too much effort, time and money? An alternative approach might be to define a set of symptoms that make your site feel unwell and work on a way of spotting them before they go live?

During the presentation Radek and Maciej will define a set of health checks that may signal your page is likely to develop some unwanted behavior and will show how they can be automated with an open-source tool and run in the development cycle.

You will find out:
- Which health checks are worth testing for you before you release the most recent version of your code,
- How you can automate testing for a set of symptoms that may affect the state of your page with an open source-tool,
- How much time and effort you could save from automated health checks, with examples of how Maciej and Radek's own teams benefitted.