Software Module Chain Hashing for Interference Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software testing methods are inefficient in identifying inter-module interference within complex software systems, as they rely on module version numbers alone, which do not account for the actual impact of changes on other modules.
Innovation Solution
A method utilizing Hash values to update and calculate chain Hash values based on calling relationships among software modules, determining interference by comparing current and historical Hash values to identify affected modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional software testing methods are used, then testing coverage can be achieved, but the testing process is time-consuming and labor-intensive
Solution Approach 1:
The patent creates a mirror software system that replicates the behavior of the original software system under test. This mirror system is generated automatically from the original system's code and structure, allowing automated analysis of software behavior without manual testing. The copying approach enables comprehensive coverage while reducing time consumption through automated comparison and anomaly detection.
Solution Approach 2:
The patent replaces manual mechanical testing processes with automated electronic analysis. By using automated tools to generate the mirror system, execute tests, and analyze results, the system eliminates the need for human testers to manually execute each test case, thereby significantly reducing testing time while maintaining or improving coverage.
2Reliability
If comprehensive software testing is performed, then system reliability can be improved, but device complexity increases
Solution Approach 1:
Instead of creating multiple separate testing tools and frameworks, the patent creates a single mirror software system that replicates the original system's structure and behavior. This unified approach simplifies the testing infrastructure while enabling comprehensive reliability verification through automated comparison between the original and mirror systems.
Solution Approach 2:
The mirror software system serves multiple functions simultaneously: it replicates the original system's behavior, executes tests automatically, performs anomaly detection, and generates test reports. This multi-functional approach reduces the need for multiple separate testing components, thereby reducing overall system complexity while maintaining comprehensive testing capabilities.
3Productivity
If automated testing tools are introduced, then testing efficiency can be improved, but ease of operation decreases
Solution Approach 1:
The automated testing system is designed to operate autonomously, automatically generating the mirror software system, executing tests, detecting anomalies, and producing reports without requiring manual intervention. The system serves itself by automatically managing the entire testing workflow, which maintains high efficiency while simplifying operation for users who only need to initiate the process.
Solution Approach 2:
The system performs preliminary actions by automatically generating the mirror software system and configuring the testing environment before actual testing begins. This pre-configuration eliminates the need for operators to manually set up complex testing parameters and environments, thereby maintaining efficiency while improving ease of operation.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
Disclosed are a testing method and apparatus of a software system, an electronic device and a computer-readable storage medium. The method includes: updating, when a part of software modules of the software system are changed, Hash values of the changed software modules; calculating chain Hash values of unchanged software modules according to a calling relationship corresponding to each software module; and judging whether the chain Hash values of the unchanged software modules are the same as corresponding historical chain Hash values, and if a chain Hash value of any of the unchanged software modules is different from a corresponding historical chain Hash value, determining the unchanged software module to be interfered.