Test Case Generator Interface for Non-Coding Engineers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Test engineers with limited coding knowledge face challenges in generating and executing test cases for computer systems and devices, as they require detailed understanding of underlying software code.
Innovation Solution
A method and system for test case generation that displays a list of test case functions via a user interface, allowing users to select and assemble test cases without needing to know the underlying code, using a repository of atomic actions that can be executed transparently for device testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If test engineers directly use development application code to create test cases, then testing precision and reliability improve, but the difficulty of operation increases significantly for engineers with limited coding knowledge
Solution Approach 1:
The patent introduces an intermediary layer between the development application code and the test engineer. This intermediary automatically extracts atomic actions from the development code, transforms them into selectable test case functions, and manages the code execution transparently. Test engineers interact with this intermediary through a simple interface without needing to understand the underlying complex code, thus maintaining testing reliability while improving ease of operation.
Solution Approach 2:
The system enables test case generation to serve itself by automatically extracting testable atomic actions from development application code without human intervention in the code extraction process. The system self-manages the transformation of development code into test case functions, automatically handling the complexity of code parsing and function identification, thereby relieving test engineers from the burden of coding expertise.
2Manufacturing precision
If test engineers need to understand detailed software code to create effective test cases, then test case quality improves, but the complexity of the testing process increases
Solution Approach 1:
The patent segments the monolithic development application code into discrete atomic actions that can be independently identified and transformed into test case functions. Each atomic action represents a single, testable unit of functionality. This segmentation allows the system to process complex code in manageable pieces, maintaining test case quality by preserving the integrity of individual functions while reducing the perceived complexity for test engineers through simplified selection interfaces.
3Ease of operation
If a user interface is provided for test case function selection, then ease of operation improves, but the device complexity increases due to additional interface components
Solution Approach 1:
The patent creates a simplified copy or representation of the development application's functional structure in the form of selectable test case functions. Instead of requiring engineers to navigate and understand the actual complex development code, the system presents a copied, abstracted view where functions are displayed with their essential characteristics (names, descriptions) without exposing the underlying code complexity. This copying approach maintains ease of operation while managing interface complexity by presenting only the necessary information.
Data Source
AI summary
An aspect includes displaying a list of test case functions via a user interface. Each of the test case functions includes a corresponding set of instructions that is extracted from a development application, and each of the test case functions is configured to execute an atomic action with respect to a test case. The set of instructions is transparent to a user of the user interface. An aspect further includes receiving, via the user interface, a user-inputted selection of the test case functions from the list. For each test function of the selected test case functions, an aspect includes displaying, via the user interface, a field for receiving a device identifier for a device subject to the test case; receiving, via the user interface, a user-inputted device identifier; assembling the test case from the selected test case functions and the device identifier; and executing the test case for the device.