Automating a test might be a simple task but making a test automatable for multiple scenarios is the winning recipe. Using proper PageObject designs and also understanding where your tests code starts and where the value sits is important, as when you make a mistake with the architecture of the automation projects, fixing the architecture might be costly and time-consuming task.

Once you understand that recipe, that same thought process can go into automating not just other tests but Deployments as well.

Enter the Automation engineer The power, value, and minds of automation testers are becoming a powerful role within organizations, where they do not only want to automate tests but everything else that comes with DevOps as well.

Like automating client feedback to your agile boards from clients, automating deployments of local websites hosted on-site or on cloud platforms (AWS or Azure), Integrating code when a developer merges changes to a branch, and then ultimately deploying the correct code when deploying to production.

For the past 5 years, it has come to me that automating tests and automating deployments and part of the DevOps processes are tightly integrated into each other, and automation testers are geared with the right thinking to fulfill these processes.

The minds, skills, and innovative thinking we as automation testers have are a powerful tool in teams, and I will gladly share my experience with the automation testing community