Automation Architect Strategies/Tips

:wave: Hi all, new to the forum.

Recently I was able to move on from a Test Automation Engineer into a testing architecture role. Im not new to setting up POC’s when I was a solo QA but this was early on in learning automation testing. This particular company has ONLY manual testing, so they hired me to start the automation process essentially.

I have ideas in my idea and will be borrowing ideas of course that i’ve used throughout my career, but this will be the first time it’s solely my decision at the direction we go.

Ive more or less decided on tools, but im curious for those that have went into this role, any tips on making it successful? or plans of action once getting in the company and starting. I have ideas but im curious from others who have gone down this role as well.



Here is a compilation of all such tips and strategies for a successful automation framework:

Consideration for Designing a Test Automation Framework - Testing Titbits | Rahul Parwal

All the best :slight_smile:


Just be aware that decisions around automated tests should include more than simply testers.

If you have BAs, they may want to get involved. You may want to choose a Cucumber-style framework if they’re going to want to see them / help write the scenarios.

You definitely want to get developers involved as it makes sense to use a language / technology that they’re familiar with. Ideally, they’re writing some of the tests as well but at the very least they’ll be able to help testers if they get stuck.

You’ll also want to get any other stakeholder’s input. Who is going to want to look at any reporting? Does it have to be “pretty” or is a simple list of tests / results ok. You may also want to think how you would combine test results if you use multiple tools, e.g. separate UI and API frameworks.