Test Code Generation from Tagged Documentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for testing web applications require manual validation and automation script re-recording with changes to the user interface, leading to increased development time and expense, as well as difficulties in traceability and evaluation due to disconnects between quality assurance and management personnel, and external auditors.
Innovation Solution
A tool that automatically generates executable test instructions from tagged test action objects in a test specification document, allowing for independent generation of test code before the application is stable, and enabling changes to the user interface without re-recording automation scripts, with support for multiple execution tools and languages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If automation scripts are created by recording manual operations, then test automation can be achieved, but the scripts need to be re-recorded when the user interface changes, increasing development time and expense
Solution Approach 1:
The patent introduces test documentation as an intermediary artifact between requirements and automation scripts. The test documentation contains tagged test action objects that serve as a stable intermediate representation, allowing scripts to be regenerated from documentation rather than re-recorded from scratch when UI changes occur.
Solution Approach 2:
The patent establishes test documentation with tagged test action objects before automation script creation. This preliminary structuring of test cases in a documentation format with identifiable action objects enables future script generation without requiring re-recording, as the foundational test structure is already in place.
2Extent of automation
If automation scripts are created by recording manual operations, then test automation can be achieved, but the process increases development expense
Solution Approach 1:
The patent creates reusable test documentation templates with tagged test action objects that can be copied and adapted for different test scenarios. This copying mechanism reduces the need to create automation scripts from scratch, thereby reducing development expense while maintaining automation capabilities.
Solution Approach 2:
The test documentation with tagged test action objects serves multiple functions: it acts as requirements documentation, test case specifications, and automation script source. This multi-functionality eliminates the need for separate documentation and script creation processes, reducing overall development expense.
3Reliability
If test cases are manually executed through the user interface, then quality assurance validation can be performed, but the process is time-consuming and requires manual interaction
Solution Approach 1:
The patent enables test documentation to be automatically processed and converted into executable automation scripts without manual intervention. The tagged test action objects in the documentation self-describe the test actions required, allowing automated script generation and execution, thereby reducing testing time while maintaining quality assurance validation.
4Extent of automation
If automation scripts are bound to a specific automation tool, then the scripts can be executed by that tool, but the scripts cannot be played back on other tools, reducing adaptability
Solution Approach 1:
The patent creates tool-agnostic test documentation with standardized tagged test action objects that can be processed by different automation tools. The documentation serves as a universal source that can be transformed into scripts for multiple different automation tools, enabling adaptability and versatility across different tool platforms.
Data Source
AI summary
Systems, methods, and other embodiments associated with test code generation based on test documentation are described. In one embodiment, a method includes identifying a tagged test action object in a test specification document; mapping the identified test action object to an executable test instruction; and providing the executable test instruction for execution to test an application through a user interface associated with the application. The example method may also include storing executable test instructions as an executable test routine, validating test routines to confirm the presence of specified test instructions, and logging execution of the test instructions.