Abstract: A generic Test Tool migration system that migrates test cases from one platform to another in different Languages and also incorporate best practices while migration. The system comprises of three phases, a pre-processor, an in-flight module, and a post-processor. The pre-processor scans and reads the entire Source code and passes the output to the in-flight module which converts the Source scripts to a neutral Language and generates a Target Language. The output of the process becomes the input to the post-processor that provides options for resolving the ambiguity, issues, and warnings with best practice suggestions to a user by the Smart (migration) Remedy Engine (SME). The translated code is further improved, validated, reported and logged. The output of the phase is converted Object Repositories, Test Data and Scripts.

Abstract: A generic Test Tool migration system that migrates test cases from one platform to another in different Languages and also incorporate best practises while migration. The system comprises of three phases, a pre-processor, an in-flight module, and a post-processor. The pre-processor scans and reads the entire Source code and passes the output to the in-flight module which converts the Source scripts to a neutral Language and generates a Target Language. The output of the process becomes the input to the post-processor that provides options for resolving the ambiguity, issues, and warnings with best practise suggestions to a user by the Smart (migration) Remedy Engine (SME). The translated code is further improved, validated, reported and logged. The output of the phase is converted Object Repositories, Test Data and Scripts.

Abstract: A Post Migration platform that has a Remediation Engine that checks for errors and warnings in the generated code from the source code, both in a different language. The system provides the options to the user for resolving the ambiguity, issues, and warnings with best practice suggestions. The engine consists of Smart (migration) Remedy Engine 4, a Report Engine 17 and a Log Engine 18. The tool generated files 1 are passed into the Smart (migration) Remedy Engine 4 that checks for syntactic and semantic errors, warnings, uncertainties, and ambiguities in the code, and also analyzes the code for the best practices. The Technical Logs are generated by the Log Engine 16. A report is generated which contains a list of technical errors, warnings and stack traces along with the TODO list.