Configurable System-Wide Test Execution for Operating Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current system-wide integration testing methods for computer operating systems are inefficient and impractical, particularly when dealing with multiple drivers, as they often halt upon the first failure, making it difficult to identify and diagnose issues in a timely and efficient manner.

Innovation Solution

A data-driven testing approach where a set of instructions is executed, and upon identifying a failed test, a second set of instructions is generated that excludes the failed test and focuses on additional or different system aspects, allowing continuous testing without manual intervention, enabling efficient diagnosis of system errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the testing process stops at the first failure, then the testing resources are conserved and individual failures can be analyzed in detail, but the overall testing efficiency decreases and multiple bugs cannot be identified in a single run

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtesting completeness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the testing process into multiple independent test cases that can be executed sequentially. When a failure occurs, the system logs the failure details and continues executing subsequent test cases rather than terminating the entire test run. This segmentation allows the testing system to identify multiple bugs in a single execution while maintaining the ability to analyze individual failures through detailed logging.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements continuous testing by automatically recovering from failures and proceeding with the next test case. The system maintains continuous operation by logging failure information and transitioning smoothly to subsequent tests without manual intervention, thereby maximizing the utilization of testing resources and identifying multiple issues in one continuous run.

Inventive Principle:
Principle #20Continuity of useful action

2Extent of automation

If manual intervention is required to resolve each failure before continuing, then individual bugs can be thoroughly investigated, but the testing time increases and automation is reduced

Engineering Contradiction:
Improvetesting automationVSAvoidtesting duration
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The patent implements self-service automation where the testing system automatically handles failure logging, test state management, and continuation of subsequent tests without requiring manual intervention. The system serves itself by automatically recovering from failures and proceeding with the test suite, thereby increasing automation extent while managing testing duration through efficient automated processes.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If comprehensive system-wide tests are conducted, then all potential issues can be identified, but the complexity of test management increases and results become difficult to analyze

Engineering Contradiction:
Improvebug detection accuracyVSAvoidtest management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where test results are automatically logged and analyzed. The system provides structured feedback about each test case outcome, failure details, and system state changes. This organized feedback approach enables comprehensive bug detection while maintaining manageable complexity through systematic result tracking and analysis capabilities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent prepares comprehensive test suites in advance with predefined test cases covering various system aspects. By organizing tests beforehand and establishing a structured framework for execution and result collection, the system can conduct comprehensive system-wide testing while keeping management complexity controlled through pre-planned test structures and automated execution frameworks.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10481969B2Configurable system wide tests
Publication Date: 2019.11.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10481969B2 patent drawing
  • US10481969B2 patent drawing
  • US10481969B2 patent drawing

AI summary

Systems and methods to conduct data-driven, system wide tests are disclosed. Instructions for testing an operating system are associated with one or more modules associated with the computing system. When a failed test is identified, a second set of instructions that accounts for the failed test is generated and executed, in order to efficiently identify and target specific issues. Results from these fully configurable testing methods can be communicated and utilized in further applications.