Code Coverage Rate Merging via Change Record Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods struggle to consolidate overall code coverage rate test data for software codes corresponding to an operation system from disparate test data acquired by different personnel.

Innovation Solution

A method and apparatus for determining code coverage rate by obtaining and processing coverage rate test data, determining code branches, and merging historical and current test data based on code change record identifiers to achieve comprehensive coverage rate data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If coverage rate test data are collected from different personnel working on the same code branch, then the quantity of test data increases, but the complexity of merging and consolidating the data increases

Engineering Contradiction:

Improvequantity of coverage rate test dataVSAvoidcomplexity of merging test data

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments coverage rate test data by code change record identifiers, dividing the merging task into manageable units. Each data set is associated with specific commit IDs, allowing independent processing and merging of segments from different personnel without requiring complex global coordination.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-processing coverage rate test data to tag and organize them with code change record identifiers before merging. This preliminary organization of data with metadata enables automated merging processes without requiring complex real-time coordination during the consolidation phase.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If coverage rate test data from different personnel are merged, then the completeness of overall coverage rate data improves, but the time required for data processing increases

Engineering Contradiction:

Improvecompleteness of coverage rate dataVSAvoidtime for merging test data

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The patent uses copying by creating a mapping relationship between different code change record identifiers and their corresponding code branches. Instead of complex multi-to-many merges, the system copies and associates data with standardized identifiers, enabling efficient consolidation through identifier-based lookup and aggregation.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent applies parameter changes by transforming coverage rate test data into a standardized format with unified code change record identifiers. By changing the parameter representation of data from personnel-specific formats to a common identifier-based format, the merging process becomes a simple aggregation operation rather than a complex integration task.

Inventive Principle:

Principle #35Parameter changes

3Measurement precision

If code coverage rate data are updated to reflect latest changes, then the accuracy of test results improves, but the frequency of data processing increases

Engineering Contradiction:

Improveaccuracy of coverage rate dataVSAvoidfrequency of data processing

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The patent implements feedback by establishing a mechanism where coverage rate test data are continuously updated and merged based on new code change record identifiers. The system provides feedback loops that detect new commits and trigger automated data merging, ensuring accuracy while maintaining efficient processing through event-driven updates rather than continuous scanning.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS20250110858A1Code coverage rate determining method and apparatus

Publication Date: 2025.04.03 BEIJING VOLCANO ENGINE TECH CO LTD

AI summary

A code coverage rate determining method, comprising: obtaining coverage rate test data to be processed and determining a code branch corresponding to the coverage rate test data to be processed, the coverage rate test data to be processed indicating a coverage rate of a software code corresponding to a first code change record identifier; obtaining historical coverage rate test data corresponding to the code branch, the historical coverage rate test data indicating a coverage rate of a software code corresponding to a second code change record identifier; in case that the first code change record identifier or the second code change record identifier includes a latest code change record identifier corresponding to the code branch, merging first coverage rate test data into second first coverage rate test data in accordance with the position of the first software code in the second software code, to obtain target coverage rate test data.