A test case automatic filling method and device

Abstract

The invention discloses a test case automatic filling method and device, relates to the technical field of test document processing, and efficiently and automatically completes the verification requirements assigned by other levels to this level. The main technical solution of the present invention is: a demand relationship tracking table corresponding to different levels of demand documents is created in advance, each row in the demand relationship tracking table stores the demand numbers of different levels and the demand numbers of different levels in the same line are pre-existing If the tracking relationship is set, then after obtaining the requirement tables assigned by other levels to the target level, according to the requirement relationship tracking table and the demand table, further analysis to know that the target requirement number corresponding to the verification requirements allocated by other levels is the same as that under the target level Which requirement number is relevant, and then the target requirement number is filled into the test template where the requirement number under the target level is located, and the verification requirements assigned to this level by other levels are filled into the relevant test cases of this level.

Description

technical field [0001] The invention relates to the technical field of test document processing, in particular to a test case automatic filling method and device. Background technique [0002] Testing is an important process in the entire product life cycle. Good test documentation can provide better guidance for testing work. Usually, testing should include at least three documents: test plan, test case, and test report, among which: The test plan determines the allocation of requirements. The test case not only describes the specific process of test execution, but also completes the coverage of the requirements. The test report is the proof of completing a round of testing. [0003] As far as test cases are concerned, the more detailed the test steps are described, the less prone to deviations in actual test execution, the more complete the requirement coverage, and the more conducive to the management of use case-requirement tracking relationship. For the needs of this l...

AI Technical Summary

Problems solved by technology

[0005] 1. There are many errors caused by human factors

Assuming that the test at this level is a subsystem confirmation test, it needs to cover the requirements from other levels of testing (such as system confirmation test, system integration test, subsystem integration test, software confirmation test, software integration test). The numbering format is different. Secondly, in the process of manual filling, symbols such as space brackets may be missing. These will cause troubles for the subsequent use of the Reqtify tool to export the tracking matrix. Among them, the Reqtify tool software is specifically for file-based, high-level Customizable, easy-to-use requirements traceability and impact analysis

[0006] 2. The process of manually checking the coverage relationship of requirements is relatively cumbersome

Assuming that the test at this level is a software confirmation test, and now we need to cover a requirement from the system confirmation test, the first thing we need to do is to find out which requirement of this level is related to this system confirmation requirement, and then check which requirement is from this level Use case coverage, and finally add Source in this use case, but how to find out which requirement of this system confirmation requirement is related to this level. In this case, you can only follow the system confirmation requirement -> system integration architecture -> sub The order of system confirmation requirements -> subsystem integration architecture -> software confirmation requirements is confirmed one by one. At this stage, the Reqtify tool only supports the export of 2-level requirement tracking relationships. If the above-mentioned 5 levels are involved, manual confirmation is still required

[0007] 3. Low efficiency

Especially when other levels have a large number of requirements assigned to this level of verification, if the verification is carried out according to the process described in the above 2 steps one by one, the workload is extremely huge, and the time to complete the coverage will be infinitely extended

Images