Software Test System for Scenario Requirement Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software test systems face challenges in determining the correctness of internal call sequences and input data for components using application data-driven programming, as they cannot accurately assess specific scenario requirements, leading to increased testing burdens.
Innovation Solution
A software test system comprising an interface module, an execution module, and a determination module that generates test case files and analyzes sub-test call operations to determine test progress information, enabling the assessment of scenario requirements and improving test performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If functional tests are conducted using returned results to determine component correctness, then test coverage is improved, but the ability to access specific scenario requirements for data-driven programming is lost
Solution Approach 1:
The patent segments the test process into multiple levels: component-level functional tests and scenario-level data-driven tests. The execution module analyzes internal call sequences separately from overall operational results, allowing both test coverage and scenario requirement verification to be achieved without losing information about specific business logic requirements.
Solution Approach 2:
The patent introduces an intermediary analysis layer between the component execution and the test results. The execution module acts as a mediator that captures internal call sequences, input data, and scenario requirements as intermediate information, enabling detailed scenario verification without compromising overall functional test coverage.
2Productivity
If data-driven programming is used in components, then programming efficiency is improved, but the complexity of determining correct internal call sequences and input data increases
Solution Approach 1:
The patent enables the system to self-analyze its own internal call sequences and input data through the execution module. The system automatically captures and verifies scenario requirements without requiring manual intervention to trace data-driven programming logic, thereby reducing test complexity while maintaining the benefits of data-driven programming efficiency.
Solution Approach 2:
The determination module provides feedback by comparing actual internal call sequences and input data against expected scenario requirements. This automated feedback mechanism simplifies the verification process for data-driven programming, reducing the manual complexity of determining correctness while preserving programming efficiency.
3Ease of operation
If overall operational results are examined to determine component correctness, then test simplicity is maintained, but the ability to verify specific scenario requirements is lost
Solution Approach 1:
The patent segments the examination process into simple overall result review and detailed scenario verification. The execution module automatically captures scenario requirement information in the background, allowing testers to maintain simple overall testing while still accessing detailed scenario requirements through the captured internal call sequences and input data.
Solution Approach 2:
The execution module performs preliminary capture and organization of scenario requirement information during component execution. By preparing and structuring the internal call sequences and input data in advance, the system enables detailed scenario verification without complicating the overall test operation, maintaining ease of use while preserving information access.
Data Source
AI summary
A software test method and a software test system including a storage device and a processor are provided. A plurality of modules are stored. The processor executes the modules in the storage device. An interface module accesses activated use case information of an electronic device to generate a test case file, so that the electronic device performs a test call operation on the interface module according to the test case file through a component under test (CUT). The interface module includes simulation component interfaces. Executing the test call operation includes sub-test call operations. An execution module respectively analyzes the sub-test call operations performed by the CUT sequentially calling the simulation component interfaces to generate sets of test progress information. A determination module generates and provides a test result to the electronic device according to a test configuration file and the sets of test progress information to improve test performance.