Unifying test automation components?
Perhaps my company has a unique product. But I was wondering if there are others who have similar issues.
Legacy code base of existing automation for different types of automation for product or product(s), like GUI automation, web UI automation, API testing, SIP testing, proprietary in-house tools.
Each type of automation uses different tool with different scripting format.
One would think it be a nice idea to unify all that automation within the company to be able to execute from a single test framework, and ideally from a single test scripting format (perhaps keyword-based).
Something like that might help with scripting expertise required to write automated tests, though it would require automation framework engineer to develop and manage the backend that unifies everything.
Re: Unifying test automation components?
To unify the automation approach, you need to find a common ground.
By that I mean every auomation script can be executed in one common way.
I suggest to check whether all scripts can be executed via command line.
Then you can probably integrate everything into ANT/Batch script framework.
Hope this initial idea helps you out.
RSS Feed : Break To Make it Better
A Lazy person could be the best automation professional, if he is not lazy in implementing his ideas to reduce his work. ~Anand Tambey