The top 5 challenges that you’re likely to face when migrating an automation framework to service a different platform are: –
- Language and Syntax differences.
- When converting from one framework to another for example, one line in one language may convert to 3 lines in another.
- Implementation/Deployment differences.
- When deploying a framework to another platform it will certainly involve a different implementation method, for example, for java you deploy with a jar file, for net you deploy with packages.
- Having the right resources with the correct skillset.
- Ensuring you have the right resources with the correct skillset to perform the migration or the building of a framework. Primarily they should come from a development background.
- Testing of each module is performed.
- Ensuring the testing of each module is performed can be a challenge as you will require stubs to mimic the integration until it is all integrated at the end.
- Dependency compatibility.
- Ensuring all versions of dependencies are compatible with each other, for example, maven dependencies. This can be a challenge if the dependencies are not compatible with each other the underlying code will fail.
The above challenges are faced when trying to migrate a C Sharp Windows automation framework to a Java Linux automation framework.
A test automation framework is a set of guidelines or rules used for creating and designing test cases. It provides a structure enabling tooling and practice integration that are designed to help testing professionals test more efficiently and effectively. These include coding libraries, coding standards, data-structures, algorithms, processes for storing test results, configuration files and databases.
SQA Consulting have developed a platform, language, phase and application agnostic automation framework called TALOS, the development has taken several years and it constantly evolving.
The main reasons to use SQA’s Automation framework are:
- To reduce work, effort and risk. The framework addresses Functional, API, Mobile, Performance and Security testing using the same processes.
- To expedite execution and outputs.
- To improve testing quality.
- To identify defects early.
- To reduce requirement for specialist resources.
- To reduce human error.
To shift resource focus to more strategic initiatives and
To increase test phase coverage without the need to write specific phase scripts.
