Work Item Delta Code Coverage Mapping for Consistent Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing techniques provide delta code coverage (DCC) only at line, file, or branch levels, making it difficult for developers and QA teams to identify work items with low DCC, leading to inefficient and error-prone manual processes, especially as team size increases, and failing to enforce consistent DCC criteria across different types of work items.
Innovation Solution
A method and system for computing delta code coverage information at the work item level by fetching details from a source code management tool, identifying lines added, modified, or removed, and associating them with commit details to calculate DCC percentage for each work item, enabling accurate identification and enforcement of DCC criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If delta code coverage is provided only at line, file, or branch level, then measurement precision is improved, but ease of operation deteriorates as it becomes too low-level for developers to quickly use and act
Solution Approach 1:
The patent introduces a new dimension of aggregation by computing delta code coverage at the work item level, which is an upper-level abstraction compared to traditional line/file/branch levels. This dimensional change allows developers to view coverage information in terms of meaningful work units (features, bugs, tasks) rather than granular code elements, making the information more actionable and easier to interpret while maintaining the underlying precision of line-level measurement.
Solution Approach 2:
The system segments the codebase into work items (features, bugs, tasks) and computes delta code coverage separately for each work item. This segmentation allows developers to identify which specific work items have low coverage and need attention, rather than having to manually analyze individual files or lines. The segmentation is achieved by tracking the mapping between code changes and associated work item identifiers.
2Reliability
If manual analysis of source control is performed to identify work items with low DCC, then reliability is improved, but loss of time increases and productivity decreases
Solution Approach 1:
The system enables self-service by automatically computing and presenting delta code coverage information at the work item level, eliminating the need for developers to manually analyze source control data. The system autonomously performs the time-consuming tasks of fetching commit details, identifying affected files and lines, computing coverage metrics, and presenting results in an actionable format, thereby reducing both time loss and manual effort while maintaining reliable results.
Solution Approach 2:
The patent introduces an intermediary system that acts as a bridge between the source control system and developers. This intermediary automatically fetches commit details, correlates code changes with work items, computes delta code coverage, and presents the information in a user-friendly format. This intermediary eliminates the need for developers to directly query source control and perform manual analysis, significantly reducing time loss while maintaining the reliability of the data.
3Adaptability or versatility
If team size increases, then adaptability is improved, but device complexity increases making it difficult to manually enable quick action on commits
Solution Approach 1:
The system provides a universal solution that works across teams of any size by automatically computing delta code coverage at the work item level. The system handles multiple users, multiple repositories, and various work item types through a unified approach, eliminating the need for manual processes that become unmanageable with larger teams. The multi-functionality is achieved by integrating with source control systems and work item tracking systems to provide comprehensive coverage analysis regardless of team composition.
4Adaptability or versatility
If baseline DCC requirement varies by work item type, then adaptability is improved, but ease of operation deteriorates as no system exists to enforce work item wise DCC checks
Solution Approach 1:
The system implements dynamic DCC baseline requirements by allowing different minimum coverage thresholds for different work item types (e.g., features, bugs, tasks). The system automatically applies the appropriate baseline to each work item based on its type, enabling flexible and adaptive quality standards without requiring manual configuration for each work item. This dynamic approach makes it easy to enforce varied DCC criteria across different categories of work while maintaining operational simplicity.
Data Source
AI summary
A processor implemented method for computing delta code coverage information for work items are provided. The method includes fetching details associated with one or more files touched between a start tag and an end tag from a source code management (SCM) tool; fetching one or more lines that are one of added, modified, or removed, for a given file, between the start tag and the end tag; fetching commit details; determining a map with work item id as key and a list of delta lines corresponding to the work item and computing, using a delta code coverage module, delta code coverage information corresponding to the fetched work items, by obtaining a list of delta lines for checking a number of delta lines covered as per the given coverage file for each work item id in the map.