Automated Test Case Generation from Execution Logs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The conventional methods for software testing are laborious and inefficient, requiring manual creation and maintenance of test cases, leading to duplication of efforts, incomplete documentation, and increased development time, especially for exploratory or ad hoc testing scenarios, which can result in discrepancies and uncertainty in test metrics.

Innovation Solution

A system and method for dynamically creating and documenting automated test cases, where pre-defined automated test blocks are used to generate and run test cases programmatically, allowing for the creation of dynamic automated test cases that can be easily maintained and executed, with a corresponding manual test case documentation for clarity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual test cases are created and automated conventionally, then test coverage can be improved, but the labor and time required increases significantly

Engineering Contradiction:

Improvetest coverageVSAvoidtime to create and maintain automated test scripts

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system enables automated test case generation by having the testing tool automatically create test cases from test execution logs and results, eliminating the need for manual script creation. The system self-documented test cases are automatically created and stored in the test repository based on the execution data

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary documentation by automatically creating test case templates and structures before full automation is implemented. Test case metadata and frameworks are prepared in advance, reducing the effort needed during actual test execution and automation

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If exploratory or ad hoc testing is performed without documentation, then testing flexibility is maintained, but test metrics become unreliable and uncertain

Engineering Contradiction:

Improvetesting flexibilityVSAvoidtest metrics accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The system implements feedback mechanisms by automatically capturing test execution results, logs, and metrics from exploratory testing sessions. This feedback is used to automatically update and document test cases in the repository, ensuring that even ad hoc testing contributes to documented test metrics and quality measurements

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary layer between exploratory testing activities and the test repository. This intermediary automatically documents test cases and metrics without interfering with the flexibility of exploratory testing, allowing testers to explore freely while the system captures and documents the activities for metric accuracy

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If test cases are manually propagated to automated scripts, then updates can be made, but synchronization between manual and automated versions becomes difficult

Engineering Contradiction:

Improvetest case update capabilityVSAvoidsynchronization complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system inverts the traditional approach by automatically generating test case documentation from automated execution data rather than manually creating scripts from documentation. This reversal eliminates the synchronization problem by making the automated version the source of truth, with manual documentation automatically derived from it

Inventive Principle:

Principle #13The other way round (Inversion)

4Extent of automation

If automated test scripts are created for every test case, then test automation coverage improves, but maintenance effort and complexity increase

Engineering Contradiction:

Improvetest automation coverageVSAvoidmaintenance effort

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The system segments test automation into modular, reusable components and templates. Instead of creating monolithic automated scripts for entire test cases, the system breaks down test logic into smaller, independently maintainable units that can be selectively applied, reducing overall maintenance complexity while maintaining high automation coverage

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS9710367B1Method and system for dynamic test case creation and documentation to the test repository through automation

Publication Date: 2017.07.18 EMC IP HLDG CO LLC

AI summary

A set of automated unit test components is stored. The automated unit test components include executable code for testing a backup system. The set of automated unit test components are displayed on an electronic screen. A selection of a subset of the unit test components from a user is received. An automated test case is created based on the selected subset of automated unit test components. The automated test case is stored. After the automated test case is created, the automated test case is parsed to derive a manual test case corresponding to the automated test case. The manual test case is stored.