Automated Test Case Creation from Version Control Repositories

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software testing processes are hindered by the high manual effort required in creating, updating, and managing test cases, leading to noncompliance with the software development lifecycle and resulting in audit gaps and governance issues.

Innovation Solution

A system and method that automates the creation, execution, and management of test cases by scanning version control repositories and source code management systems, integrating with various testing frameworks, and uploading results to a system of record, reducing the need for manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual approaches are used to create and manage test cases in a system of record, then test case creation and management can be performed, but the process becomes time-intensive and noncompliant with SDLC

Engineering Contradiction:

Improveautomation of test case creationVSAvoidtime-intensive manual activities

Core Design Contradiction:

Extent of automationVSLoss of time

Solution Approach 1:

The system enables self-service automation where the test management system automatically scans version control repositories, detects test code and files, creates test cases, executes them, and uploads results to the system of record without requiring manual human intervention for these routine tasks

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical processes (human operators physically creating and managing test cases) with an automated computational system that uses scanning, detection, and API-based interactions to perform the same functions

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If manual approaches are used to update test cases and upload results, then test case management can be performed, but compliance with SDLC and audit requirements is compromised

Engineering Contradiction:

Improvecompliance with SDLCVSAvoidease of manual test case management

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements continuous feedback loops where test results are automatically captured, uploaded to the system of record, and used to trigger updates to test cases, creating a closed-loop system that ensures ongoing compliance with SDLC requirements

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by automatically creating test cases from detected test code before execution, and by pre-configuring the upload mechanism to ensure results are immediately captured and compliance is maintained throughout the testing process

Inventive Principle:

Principle #10Preliminary action

3Productivity

If test cases are managed manually in a system of record, then test case storage can be achieved, but the process becomes difficult and time-intensive

Engineering Contradiction:

Improveefficiency of test case managementVSAvoidcomplexity of test case management system

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The test management system performs multiple functions through a single integrated platform: scanning version control repositories, detecting test code, creating test cases, executing tests, capturing results, and uploading to the system of record, thereby improving productivity without proportionally increasing operational complexity

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10007597B2Software testing management

Publication Date: 2018.06.26 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC

AI summary

A system may scan a version control repository to detect a first code and/or a first file written for a first test framework. The system may create a first test case in an SOR in response to detecting the first code and/or the first file. The system may scan the version control repository to detect a second code and/or a second file written for a second test framework with the second test framework being different from the first test framework. The system may create a second test case in the SOR in response to detecting the second code and/or the second file.