Epic Code Analysis Linking User Stories to Test Coverage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The disconnect between software development and quality assurance processes often leads to software releases that do not fully meet user expectations, resulting in untested or under-tested code, which increases maintenance costs.

Innovation Solution

A system and method for analyzing code coverage in relation to user stories by integrating development and testing processes, using a user story analyzer, build mapper, and machine learning to ensure comprehensive test coverage and alignment with user requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If development and testing processes are treated as separate processes, then each process can be managed independently with simpler coordination, but the code coverage and test alignment with user stories deteriorates

Engineering Contradiction:
Improveprocess coordination complexityVSAvoidcode coverage
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent merges the development and testing processes by introducing a unified system that integrates code change detection, test selection, and execution. The test management system receives code changes from the development process and automatically selects and executes relevant tests, creating a combined workflow that ensures comprehensive code coverage while maintaining process integration.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces several intermediary components that bridge the development and testing processes. The build mapper acts as an intermediary that maps code changes to affected functionality, the test selector serves as a mediator that chooses appropriate tests based on code changes, and the test executor coordinates test运行. These intermediaries enable seamless integration between development and testing while maintaining clear process boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive test coverage is ensured through integration of development and QA processes, then code quality and user story alignment improve, but the system complexity and implementation difficulty increase

Engineering Contradiction:
Improvecode qualityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the integrated system into distinct functional modules: a build mapper that maps code changes to affected functionality, a test selector that chooses relevant tests, a test executor that runs selected tests, and a report generator that produces coverage reports. Each module performs a specific function and can be independently implemented and maintained, reducing overall system complexity while achieving comprehensive code coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements self-service mechanisms where the build mapper automatically identifies affected functionality from code changes, the test selector autonomously selects appropriate tests based on the identified changes, and the report generator automatically produces coverage reports. This automation reduces manual intervention and simplifies the implementation of comprehensive testing integration.

Inventive Principle:
Principle #25Self-service

3Device complexity

If manual analysis of code changes and test coverage is performed, then the system implementation is simpler with fewer automated components, but the time consumption and productivity decrease

Engineering Contradiction:
Improveautomation levelVSAvoidanalysis speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements preliminary action by having the build mapper pre-process code changes and identify affected functionality before test selection occurs. The system proactively maps code changes to affected user stories and functionality, preparing the information needed for test selection in advance. This preliminary analysis automation significantly reduces the time required for manual code change analysis while maintaining system simplicity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250238351A1System and method for epic code analysis for a user story
Publication Date: 2025.07.24 TRICENTIS ISRAEL LTD
  • US20250238351A1 patent drawing
  • US20250238351A1 patent drawing
  • US20250238351A1 patent drawing

AI summary

A system and methods are provided that are configured for analyzing code coverage in relation to user stories. The system includes a non-transitory memory and one or more hardware processors that cause the system to perform operations comprising receiving a user story definition for software code and analyzing the software code by managing executions of tests for determination of the code coverage of the software code in relation to the user story definition, performing the tests using one or more test runners, determining test results, performing the analysis of the code coverage based at least on the test results, and determining whether the software code is ready for a release or the tests require a refinement for a further analysis. The operations may further comprise outputting information associated with whether the software code is ready for the release, or the tests require the refinement for the further analysis.