The future of test automation
Automation is here to stay. But who does what, if at all, is definitely going to change. Testers writing automated tests are not going anywhere, but the tools they use might change.
Less and less companies are going to be wanting to develop their own framework. The “quick and easy” promise of 3rd party tools such as 21 take the hearts of executives and soon these people will only find positions working for companies with a need to test proprietary technologies.
Automation testing is not just testing
It’s full DevOps and a complex cycle that includes multiple components: Set up an environment for testing, set up test runners, unified reporting. It’s no longer just a “software project” but a full blown product. Scripting is just one of many use-cases.
Viewing that as a product you have to take into account the use cases, the users (testers, PM’s, devs, product, etc.), technology stack, what’s tested today and also what could be tested tomorrow!
Think about the framework. No One size fits all
Enterprises are dealing with a wide range of applications, some internal, some external, and are often a mix of web and mobile based apps, the tool chain and testing strategy is not a “1 size fits all”. Within enterprises you would typically find different testing frameworks, some open-source, some commercial, that match the existing skills, objectives, and app type. Quality is top of mind for all enterprises, therefore, they aim for high degree of automation testing and coverage across larger scale of devices/web browsers to ensure they reduce as many risks as possible.
Choosing a framework should be done per project and based on the available skill-set, the business scenarios and the aspect we want to test (e.g API/functional/UI/performance).
We are entering a new era of code-less tools that are aiming to simplify test automation creation for web and mobile, and reduce the maintenance. The term “code-less” is no longer a relevant term. Today these tools are sophisticated machine learning based tools. To succeed in that journey, these tools need to pick up where the current market is at today with Selenium/Appium and prove the added value through taking similar scenarios (flaky or not) and automating them at scale, running them time after time with reliability and consistent result. In 6-12 months the market will be in a different place than today with more practitioners mixing between code and no-code scripts