Method and system for controlling changing of software project test requirements

Abstract

The invention discloses a method and system for controlling the changing of software project test requirements. By the method, requirement IDs (identifiers) of the software project test requirements before and after the changing are compared one by one, and then requirement descriptions and requirement names of the software project test requirements before and after the changing are compared one by one to identify functions of changed requirement names, so that a tester can comprehensively control the whole test process and know fairly well, test coverage can be widened and test efficiency can be improved. The system associates the software project test requirements in form of Microsoft Office Excel file before and after the changing by an association module, identifies each field of the software project test requirements and the requirement IDs of the software project test requirements before and after the changing by a requirement ID identification module, and automatically displays the functions of the changed requirement names to the tester by a requirement description comparison module, a requirement name extraction module and a display module. The test work of the tester is simplified, and simultaneously, the tester can comprehensively and accurately control the changing of the software project test requirements.

Description

technical field [0001] The invention relates to a method and system for controlling changes in testing requirements of software items, belonging to the field of computer software testing. Background technique [0002] In the process of software project testing, especially in the Internet field, whether it is the early stage or the late stage of the software project testing process, there will always be the problem of requirement changes. Once the software project testing requirements change and modify, the corresponding project testing during the testing process Requirements have changed accordingly. Since most of the company's internal product demand changes are only notified verbally or by email, there is no internal review and records of related demand changes, resulting in increased demand for some subsequent products, and some did not increase . This will lead to incomplete information obtained from the test and difficulties in maintaining subsequent products. The tw...

AI Technical Summary

Problems solved by technology

In response to this situation, the current solution is as follows: First, most project leaders now also require corresponding personnel to add requirements change documents to manage requirements changes, so that test requirements are updated accordingly, but this method The efficiency is low, and it is difficult to control; second, although the test requirements can be updated, there is no clear document description for which module functions are added for the update of the requirements, and often test executives who do not understand the business will miss the test functions, resulting in The testing of new requirements does not cover comprehensively, which will take more time to find, waste time, and even lead to project delays in severe cases

Images