Master Test Repository for Automation Script Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The high cost and inefficiency of creating manual steps in automated testing processes, particularly in large and long-lived projects, where automation engineers' productivity is measured by automated steps rather than manual ones, leading to increased expenses and reduced productivity.
Innovation Solution
A method and system that reuse test steps by determining a unique key reference value for automation test scripts, deriving and mapping manual step information from a master test repository, and updating the repository with step descriptions and expected results, enabling the reuse of manual steps for new automation test scripts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automation testing is implemented, then testing efficiency is improved, but cost increases due to traceability requirements between automation steps and manual steps
Solution Approach 1:
The patent creates a master test repository that stores reusable manual step information, which can be copied and reused across multiple automation test scripts. This eliminates the need to recreate the same manual steps repeatedly, reducing the cost associated with traceability requirements while maintaining testing efficiency.
Solution Approach 2:
The patent performs preliminary action by pre-determining and storing manual step information in a master test repository before automation testing begins. This allows automation engineers to directly reuse pre-prepared manual step data, eliminating the need to perform costly traceability analysis during each automation script creation process.
2Reliability
If manual steps are created by human testers, then testing coverage is improved, but productivity decreases due to high cost and time consumption
Solution Approach 1:
The patent creates a universal master test repository that serves multiple functions: storing manual step information, providing reference data for automation scripts, and enabling reuse across different testing scenarios. This single repository structure improves both testing coverage and productivity by making manual step information universally accessible and reusable.
Solution Approach 2:
The system enables automation engineers to self-service by directly accessing and reusing manual step information from the master test repository without requiring human testers to recreate steps. This shifts the workload from manual step creation to automated retrieval and application, significantly improving tester productivity while maintaining comprehensive coverage.
3Productivity
If automation engineers create automated steps, then productivity measurement is improved, but manual step creation becomes a non-value add activity
Solution Approach 1:
The patent extracts the manual step creation task from the automation engineer's workflow by providing a pre-populated master test repository. Automation engineers no longer need to create manual steps from scratch; instead, they extract and reuse existing manual step information, transforming manual step creation from a non-value add activity to a value-preserving reuse activity.
Solution Approach 2:
Manual step information is preliminarily created and stored in the master test repository before automation engineering begins. This preliminary action separates manual step creation from automation script development, allowing automation engineers to focus solely on automated step creation while manually created steps serve as reusable templates, improving both productivity measurement and ease of manufacture.
Data Source
AI summary
Embodiments of the present disclosure relates to a method and a system for controlling automation of testing applications. In an embodiment, automation test scripts read from automation test framework are processed to determine a unique key reference value and map with a plurality of automation test scripts stored in a master test repository. Based on the mapping, manual step information comprising at least a step description and expected result of the mapping automation test script is derived and updated in the master test repository for future references. Thus, the method and the system enables reusing of available manual step information for automation test scripts to generate manual steps thereby, minimizing time and cost involved in creating manual steps for automation of testing applications.