Software Test Reordering via Hardware Interaction Recording
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing methodologies are inefficient, requiring the full suite of test processes to be run repeatedly, which is costly in processing resources and development time, especially when addressing issues with specific hardware devices or features.
Innovation Solution
A method that records hardware device interactions during initial test processes and reorders subsequent test processes based on these interactions to prioritize testing on specific hardware devices or features, allowing for quicker detection of ongoing problems without running the full test suite.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the full suite of test processes is run repeatedly to ensure complete structural coverage, then testing completeness is improved, but testing time and processing resources are worsened
Solution Approach 1:
The patent segments the full test suite into individual test processes and further divides them into two groups: a first group of test processes that interact with the specific hardware device, and a second group that do not interact with it. This segmentation allows the system to run only the relevant first group when testing for hardware defects, rather than executing the complete test suite, thereby reducing testing time while maintaining effectiveness for hardware-related issues.
Solution Approach 2:
The patent applies partial action by running only a subset of test processes (those in the first group that interact with the specific hardware device) rather than the full test suite. When a hardware defect is suspected, the system performs partial testing with the first group, which is sufficient to detect hardware-related issues without the overhead of executing all test processes, thus reducing time and resource consumption.
2Productivity
If test processes are reordered to prioritize hardware-specific tests, then defect detection speed is improved, but test process management complexity is worsened
Solution Approach 1:
The patent applies preliminary action by pre-categorizing test processes into groups based on their interaction with specific hardware devices before actual testing begins. The system identifies and separates test processes into a first group (interacting with the hardware device) and a second group (not interacting) in advance. This pre-organization enables rapid switching between full-suite testing and targeted hardware testing without requiring complex real-time decision-making during test execution.
Solution Approach 2:
The patent uses feedback mechanisms to determine which test group to execute based on testing objectives. The system monitors whether a hardware defect is suspected and automatically selects the appropriate test group (first group for hardware defects, second group for software defects). This feedback-driven selection simplifies test process management by providing clear decision rules rather than requiring complex manual orchestration.
Data Source
AI summary
A method is provided for testing a computer system, which system includes an interface supporting connection to one or more hardware devices. The method comprises initially performing a plurality of discrete software test processes in a first order of performance. For each test process, by reference to the said interface, the hardware device interactions occasioned by each said test process are recorded. Subsequently the said test processes are run in a second order of performance, which second order is derived from the record of hardware device interactions. A computer system configured to implement the method is also provided.