Automated Software Test Failure Tracking via EOT Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing consistently-failing software tests in a software development management system is time-intensive and laborious, especially with frequent testing of large numbers of tests across multiple versions of a software application, making it difficult to identify and update tasks effectively.

Innovation Solution

A system and method that utilize a failed test detector to analyze Evidence Of Test (EOT) files to identify consistently-failing tests and automatically create or close tasks in the software development management platform, ensuring that tasks are assigned to developers for investigation and resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual evaluation of test results is performed to identify consistently-failing tests and update tasks, then task management accuracy is maintained, but time consumption and labor intensity increase significantly

Engineering Contradiction:
Improvetest result evaluation efficiencyVSAvoidtime to identify and update tasks
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically evaluating test results, identifying consistently-failing tests, and updating tasks without human intervention. The automated system monitors test outcomes, compares results across multiple executions, and independently manages task creation, updates, and closures based on detected test failure patterns

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual evaluation process with an automated computational system. Instead of human reviewers manually analyzing test results, the system uses automated algorithms to process test data, detect failure patterns, and trigger task management actions, substituting human labor with machine-based automation

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated detection of consistently-failing tests is implemented, then time consumption is reduced, but system complexity increases

Engineering Contradiction:
Improvetask update speedVSAvoidautomation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The automated system is segmented into distinct functional modules: test result collection, failure pattern detection, task identification, and task management execution. Each module handles a specific aspect of the automation process, making the overall complex system manageable through functional decomposition and independent component development

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If manual task management is performed for each test failure, then task accuracy is maintained, but labor intensity and operational complexity increase

Engineering Contradiction:
Improvetask management easeVSAvoidprocess complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges multiple discrete manual operations into a single automated workflow. Instead of separately evaluating test results, identifying failing tests, determining consistency patterns, and updating tasks as distinct manual steps, the system combines these operations into an integrated automated process that executes seamlessly without human intervention

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240143492A1Automated tracking of consistent software test failures
Publication Date: 2024.05.02 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US20240143492A1 patent drawing
  • US20240143492A1 patent drawing
  • US20240143492A1 patent drawing

AI summary

A system that includes a failed test detector and a task updater can automatically update tasks associated with consistent failures of software tests in a software development management platform. The failed test detector can use a set of evidence of test (EOT) files that indicate software testing results over a period of time to identify tests that are consistently failing when executed against versions of a software application. The task updater can automatically create tasks associated with such consistently-failing tests in the software development management platform. The task updater can also automatically close existing tasks associated with tests, in the software development management system, if the failed test detector determines that those tests are no longer failing consistently.