Automated Test Selection by Object Risk Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing methods are inefficient as they often require comprehensive re-testing of entire systems after updates, wasting resources on non-affected components and missing critical ones, due to lack of automated testing based on criticality attributes of affected computer objects and processes.
Innovation Solution
An automated method that compares updated computer objects with the installed version, analyzes changes, and organizes relevant tests into a plan, executing only necessary automated tests based on criticality ratings and dependencies, while allowing for manual testing of unaffected but critical components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If comprehensive re-testing of entire systems is performed after updates, then reliability of software processes is ensured, but time and resource consumption increases significantly
Solution Approach 1:
The patent segments the testing process by dividing the system into individual computer objects and their associated processes. Instead of testing the entire system, the analysis tool identifies and segments only those computer objects that are actually affected by the update, allowing targeted testing of specific segments rather than comprehensive system testing.
Solution Approach 2:
The patent applies local quality by assigning different testing priorities and depths to different computer objects based on their criticality attributes. Critical computer objects receive thorough testing while non-critical objects receive minimal or no testing. This localized approach ensures that testing resources are concentrated on areas where they are most needed.
2Loss of energy
If risk-based subsets of processes are tested, then testing resources are conserved, but critical computer objects in less critical processes may be missed
Solution Approach 1:
The patent changes the parameter used for selecting test subjects from process criticality alone to computer object criticality attributes. By analyzing attributes of individual computer objects rather than relying on process-level risk assessments, the system can identify critical objects even in less critical processes, ensuring they are included in the test scope.
Solution Approach 2:
The patent implements feedback by using the analysis tool to automatically identify affected computer objects and feed this information back into the test selection process. This closed-loop approach ensures that the testing scope is dynamically adjusted based on actual update impacts, preventing both over-testing and under-testing of critical objects.
3Productivity
If automated testing is implemented based on criticality attributes, then testing efficiency improves, but system complexity increases
Solution Approach 1:
The patent introduces an analysis tool as an intermediary between the update package and the automated testing system. This intermediary analyzes the update, identifies affected computer objects based on their criticality attributes, and generates a tailored test scope. By inserting this intermediary layer, the system achieves automated efficient testing without requiring direct complex integration between update management and testing frameworks.
Data Source
AI summary
A system, computer readable medium, and method for automatically testing computer objects affected by an update package. The exemplary method may compare computer objects/instances in an update package with those of the installed version of the computer application. A set of computer objects that have changed in the update package as compared to the installed version may be generated. The changes to each of the computer objects in the set of changed objects may be analyzed to determine if an automated test is related to the changed object. If an object has a related automated test assigned to it, the object may be placed in a separate list for testing. The automated tests of the changed objects in the separate list may be organized into a test plan. The automated tests may be executed according to the test plan. The system may have servers and computer processors to implement the method.