Typically in organizations, there are multiple projects and products in development. Many organizations like to have a common Test Automation solution across these products in an effort to standardize the framework. However, this is not such a good idea! Each product should be tested using the tools and technologies that are "right" for it. Yet, these different products should talk to each other and the integration between them needs to be tested in an automated way.
In this deck, I describe why it is not a good idea to have a common test automation framework. Instead, using a demo of TaaS, I describe a new way to automate the integration testing between different products, which use different tools and technologies as a development and testing stack.
Thoughts? How do you deal with the need for a uniform testing system across your applications?
Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.
