QA automation needs to expand its reach in such a fast-paced world, not all things can be fixed in the sprint or cycle that they are found in. To accomplish this, most people talk about some common buzzwords such as “Shift Left” or “test early and often”. Which just means test sooner. Other people talk about CI/CD which should always be implemented where possible. But there is more you can do, especially if you work with a lot of data coming from different sources or content. We need to automate the entry of data and validate the content even before it gets into the system.

Takeaways from the topic:

• I will give a couple of examples of what we ran into, how we used RPA (Robotic Process Automation) on one of the issues, and how we developed another tool that validates the content. Both solutions have improved quality and shortened the data validation cycle. I will also demonstrate how to identify opportunities where QA can step in, even before QA’s full engagement. QA automation shouldn’t be just about testing the code or the content, but it should be about improving the quality and increasing the productivity of the entire team.