Automation Asset Migration via Virtual Source Tool Copying
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing test automation tools lack a proper solution for migrating automation assets to new tools, requiring significant time and effort to rewrite scripts and supporting limited enhancements or new technologies, leading to fragmented tool landscapes and high migration costs.
Innovation Solution
A method and system for migrating automation assets by receiving input data from a source application, configuring data types, generating relationships between entities in the source and target applications, and migrating entities based on these relationships, utilizing an asset management system with a processor and memory to facilitate the process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enterprises migrate from existing automation tools to new tools, then they can adopt new technologies and enhance features, but they face high migration costs and significant time consumption for rewriting scripts
Solution Approach 1:
The patent creates a virtual copy of the source automation tool within the target tool environment. The asset management system generates a virtual source tool that replicates the functionality and assets of the original source tool, allowing scripts to execute in the target tool without modification. This copying approach eliminates the need to rewrite scripts while enabling access to new technologies and features of the target tool.
Solution Approach 2:
The patent introduces an asset management system as an intermediary between the source and target automation tools. This intermediary manages the virtualization process, handles asset migration, and facilitates communication between the virtual source tool and the actual target tool. The intermediary abstracts the complexity of migration, allowing seamless transition without manual script rewriting.
2Ease of manufacture
If enterprises maintain existing automation assets in current tools, then they avoid migration costs, but they end up with a fragmented tool landscape
Solution Approach 1:
The patent makes the target automation tool universal by enabling it to execute scripts originally written for the source tool. Through virtualization, the target tool gains the capability to handle both its native scripts and migrated source tool scripts, eliminating the need for separate source tool installations and reducing tool landscape fragmentation.
Solution Approach 2:
By creating a virtual copy of the source tool within the target tool environment, the patent allows enterprises to maintain their existing automation assets without physical migration while consolidating the tool landscape. The virtual source tool resides within the target tool, enabling unified management and reducing complexity.
3Reliability
If existing automation tools are used, then they support current operations, but they cannot support enhancements or new technologies
Solution Approach 1:
The patent creates a dynamic environment where the target tool can adapt to both source tool scripts and native target tool scripts. The virtualization framework allows the system to dynamically switch between executing source tool scripts in the virtual environment and utilizing target tool's native capabilities, providing both reliability for current operations and adaptability for new technologies.
Solution Approach 2:
The patent merges the functionality of the source tool with the target tool by virtualizing the source tool within the target tool environment. This combination allows the system to maintain support for existing operations through the virtual source tool while simultaneously leveraging the target tool's new technologies and enhancements.
Data Source
AI summary
Disclosed herein is a method and system for migrating automation assets in an enterprise system. The method includes receiving, by an asset management system, an input data associated with the automation assets from a source application. Also, the method includes configuring a first set of data types associated with the input data, by identifying a corresponding data type from a second set of data types, configured in a target application. Further, the method includes generating a relationship between each of a plurality of entities associated with the first set of data types and a corresponding plurality of entities associated with the second set of data types in the target application. Finally, the method includes migrating the plurality of entities associated with the first set of data types from the source application to the target application based on the generated relationship.