Test Data Comparison System for Software Quality Coverage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software testing becomes increasingly complex with the rise in software complexity, and manual testing is repetitive, making it challenging to ensure robust quality coverage, especially in identifying diverse test actions that automated testing may miss.

Innovation Solution

A system comprising a history engine, comparison engine, and suggestion engine that compares manual test data to historical data to identify diversity, alerting testers when actions are too similar and suggesting more diverse actions, thereby enhancing quality coverage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual testing is performed to ensure robust quality coverage, then testing depth is improved, but testing time and effort increase

Engineering Contradiction:
Improvequality coverageVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements feedback by comparing current test data against historical test data and providing real-time guidance to testers. The comparison engine analyzes similarity between test actions and provides feedback through alerts and suggestions, enabling testers to adjust their actions to achieve more diverse coverage without increasing time investment

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system enables self-service by automatically tracking and analyzing test data diversity without requiring manual intervention. The history engine and comparison engine work autonomously to monitor test actions, identify patterns, and provide guidance, freeing testers from manual diversity tracking while maintaining high quality coverage

Inventive Principle:
Principle #25Self-service

2Productivity

If automated testing is used to improve efficiency, then testing speed is improved, but testing creativity and exploratory capability deteriorate

Engineering Contradiction:
Improvetesting speedVSAvoidexploratory testing capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system introduces an intermediary layer between automated testing and human testers. The comparison engine acts as a mediator that analyzes test data, identifies diversity opportunities, and provides suggestions to human testers, enabling them to combine automated efficiency with human creativity and exploratory capability

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If test actions are repeated to ensure coverage, then testing thoroughness is improved, but tester productivity deteriorates

Engineering Contradiction:
Improvetesting thoroughnessVSAvoidtester productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system provides feedback to testers about the diversity of their test actions by comparing them against historical data. This feedback mechanism helps testers understand when they are repeating similar actions and guides them toward more diverse test scenarios, maintaining thoroughness while improving productivity by reducing unnecessary repetitions

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the parameter of test action diversity by analyzing and comparing test data characteristics. The comparison engine identifies patterns and similarities in test actions and provides guidance to vary test parameters, enabling testers to achieve thorough coverage through more efficient, less repetitive actions

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10719482B2Data comparison
Publication Date: 2020.07.21 MICRO FOCUS LLC
  • US10719482B2 patent drawing
  • US10719482B2 patent drawing
  • US10719482B2 patent drawing

AI summary

In one implementation, a test data comparison system can include a history engine to gather test data and maintain a log of test data based on element identifiers of a user interface, a comparison engine to identify a degree of diversity from a comparison of a first data and a second data and determine a second data entered at a first location is diverse from a first data entered at the first location when the degree of diversity achieves a diversity level of a diversity rule, and a suggestion engine to cause a message to be generated based on the comparison.