Software test management system and test method

Abstract

The invention discloses a software test management system and a test method.The system comprises a project management module, a demand management module, a test submission management module, a use case management module, a test execution module and a defect management module, when software testing is carried out, a project administrator creates a software test project, and a research and development party newly adds a test submission demand; the test party designs a test case, executes a test plan, records the execution state of the test case and submits a test problem list according to the test requirement, the research and development party processes the test problem according to the test problem list, and the research and development party and the test party jointly complete the software test. The software test management system has good expandability, standard management is provided for the test process, research and development parties approve and test demand information through test parties, the standardization is good, and problems can be found more quickly; and unified management of test data provides a data source for subsequent multiplexing and analysis.

Description

Technical Field

[0001] The present invention relates to the technical field of software test management systems, and in particular to a software test management system and a testing method. Background Art

[0002] As software functions become more and more abundant and software architecture systems become more and more complex, its applications have covered all major areas of society. As the number of iterations of software development increases, communication and exchanges with the testing department become more and more frequent. The limited number of testers in the company needs to test complex software and complete the record of the testing process, making the testing work complicated and chaotic. Therefore, a software testing management system that unifies the management of the R&D department and the testing department is needed to improve the testing efficiency.

[0003] There are many existing test management tools, such as open source TestLink, Mantis, etc., and commercial ones such as TestDirector, Zephyr for Jira, Quality Center, etc. The open source TestLink focuses on use case management, while Mantis focuses on problem management. Use cases and problems cannot be well associated, and there is a lack of management of requirement versions. Commercial tools are not suitable for domestic evaluation agencies and companies due to their price, language, and design management system, and are not suitable for the standardization of evaluation laboratory processes. Moreover, these tools are mainly used in the entire software development process, and do not focus on the management of the testing process.

[0004] The patent document with application number 202311728821.2 discloses a software testing management method, system, device and storage medium, including: creating alarm information for software testing and configuring its corresponding processing personnel information, the processing personnel information is used to determine the authorized user corresponding to the alarm information; when an information processing operation of the authorized user on the alarm information is detected, the alarm information is processed accordingly based on the information processing operation; when a comment operation of the authorized user on the alarm information is detected, the comment content corresponding to the comment operation is obtained; the comment content is added to the alarm information, and all comment content related to the alarm information is displayed.

[0005] The solution embodiment of the document can solve the problems of communication and collaboration difficulties among relevant processing personnel and low software testing efficiency during software testing. However, it also has the problems of poor correlation between the R&D party and the testing party and poor standardization of the testing process.

[0006] Therefore, a practical and efficient software testing management system is needed to solve the problems of faster changing requirements, confusing correlations between use case issues, and uncontrollable testing progress during the testing process, so as to meet the standardization of the testing process. Summary of the invention

[0007] In response to the above problems, the purpose of the present invention is to provide a software testing management system and a testing method, which link the R&D party and the testing party, adapt to changing testing needs more quickly, have good correlation between use case problems during the testing process, make the testing progress easy to control, and better standardize the software testing process.

[0008] The embodiments of the present invention provide a software testing management system and a testing method.

[0009] A first aspect: A software testing management system, comprising: a project management module, a requirement management module, a test management module, a use case management module, a test execution module and a defect management module, wherein:

[0010] The project management module is configured to manage project information and project members;

[0011] The demand management module is configured to manage demand information and demand function points;

[0012] The test submission management module is configured to manage the test submission requirements and the test submission approval process;

[0013] The test case management module is configured to maintain and manage the test cases;

[0014] The test execution module is configured to manage the test plan execution information and the test case execution results;

[0015] The defect management module is configured to manage defect problem information and defect logs.

[0016] Further,

[0017] The project information management includes determining the project name and project identification;

[0018] The project member management includes adding or deleting project members, assigning project roles to project members, and setting project member permissions and responsibilities.

[0019] Further,

[0020] The requirement information includes the name of the tested software version, release time and version description;

[0021] The requirement function point includes the requirement name, automatically generated requirement identifier, requirement type, requirement status and the person responsible for the development of the requirement;

[0022] The requirement management module provides the creation of requirement function points in the form of a tree structure and supports previewing the content of the requirement function points in the form of a mind map.

[0023] Further,

[0024] The test requirements include the version information of the tested software, the access address or installation package address of the tested software, the test environment, the test tasks, the associated required functional points, and the functional points that need to be tested;

[0025] The test approval process management refers to the R&D project manager creating and submitting a test request, and the test manager of the testing party determining whether the content of the test request meets the test requirements and approving it.

[0026] Furthermore, the test case maintenance management includes adding and managing test cases, and the test cases include:

[0027] Use case name, automatically generated use case identifier, associated test requirement function points, test type, test version, and use case steps.

[0028] Further,

[0029] The test plan execution information includes the plan name, the version of the software being tested, the version submitted for testing, the start and end time of the execution plan, the execution plan description information, and the execution case selected for this execution plan, the personnel who will perform the test, and the assignment of the test tasks;

[0030] Associate the version information of the tested software, the version information of the testing software and the test case information, and create a new test plan to assign execution cases;

[0031] The use case execution results include four execution results: not executed, passed, failed and blocked, among which the failed execution result is associated with the problem ticket information.

[0032] Furthermore, the defect problem information includes the reporter, assignee, problem type, severity, problem status, priority, frequency of occurrence, problem description, problem details, and the corresponding version of the tested device, version submitted for testing, test plan execution, test case set, test execution case and test environment information;

[0033] The defect log information management includes the change record after the user modifies the defect problem information and the defect note information newly created by the user.

[0034] A second aspect: A software testing method using the software testing management system of the first aspect, comprising the steps of:

[0035] S1. Project administrators create software testing projects, manage project information, add project members, and assign project member permissions and responsibilities;

[0036] S2. The R&D party creates and publishes test requirement information based on the software test project and adds new test requirements;

[0037] S3. The testing party approves the test request. After approval, the test case is designed according to the test request and the test plan is executed;

[0038] S4. The tester records the execution status of the test case, submits a test problem sheet, and assigns it to the R&D party;

[0039] S5. The R&D party fixes, rejects or postpones the test problem based on the test problem list and provides feedback to the test party;

[0040] S6. The testing party completes the software testing based on the feedback from the testing issues.

[0041] Furthermore, the

[0042] After the R&D party fixes the test problem, it will be sent to the test party for regression verification. If the regression verification fails, the problem will be transferred back to the R&D party until it is fixed or closed;

[0043] After the R&D party refuses to handle the test issue, the test party closes the test issue;

[0044] After the R&D party defers the testing issue, the testing party will track the deferred issue until it is fixed or closed.

[0045] Furthermore, in S4, the test party records the execution status of the test case, including pass, fail or block, wherein:

[0046] After a test case fails, the tester can directly create a new issue ticket or choose to associate an existing issue ticket number;

[0047] After the test case execution is blocked, the test party records the cause of the blockage and provides it to the R&D party. After the R&D party fixes the problem, it sends it to the test party for regression verification.

[0048] Beneficial effects of the present invention:

[0049] 1. The software testing management system of the present invention has good scalability, providing a basis for the subsequent automated execution of integrated testing tools; during the software testing process, the R&D party and the testing party are linked to achieve centralized management of projects, requirements, test cases, test records, and test defects, providing standardized management for the testing process.

[0050] 2. When using the test management system of the present invention, the R&D party shall submit test requirement information after approval by the testing party, and standardize the input of the test requirements; the test requirements are strongly associated with the test cases, and the coverage of the test requirements can be checked through the designed test cases; the identification of test requirements, test cases, execution cases and test problems is uniformly generated to standardize the uniqueness of the test content.

[0051] 3. The test management system of the present invention has a bidirectional association between test cases and defect issues. The corresponding defect issues can be directly viewed by executing failed test cases, and failed test cases can also be directly viewed through defect issues, so that problems can be discovered more quickly, the causes of occurrence can be modified, and regression verification is convenient;

[0052] 4. The test management system of the present invention forms test data resources through unified management of test requirements, test cases, test records and defect data, providing data sources for subsequent reuse and analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is a structural diagram of the software test management system of the present invention;

[0054] Figure 2 A schematic diagram of the process of software testing by the software testing management system of the present invention;

[0055] Figure 3 It is a flowchart of the software testing method of the present invention;

[0056] Figure 4 It is a schematic diagram of the structure of the electronic device of the present invention. DETAILED DESCRIPTION

[0057] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar symbols throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0058] Existing software testing management tools have poor correlation between test cases and test problems, and lack management of requirement versions. Some foreign commercial testing software has poor compatibility with domestic evaluation agencies and companies, low cost-effectiveness, is not suitable for the standardization of evaluation laboratory processes, and is mainly used for the management of the entire software development process, without focusing on the management of the testing process.

[0059] In view of the above problems, the present invention provides a software testing management system. Figure 1 The present invention provides a structural diagram of a software testing management system, which mainly includes: a project management module, a requirement management module, a test management module, a use case management module, a test execution module and a defect management module.

[0060] The project management module is configured to manage project information and project members; project information management mainly includes the determination of project name and project identification. Project information management is mainly configured and managed by the project administrator, who can create project information, including project name and project identification.

[0061] After creating a project, the project management module provides functions such as member management, editing projects, exiting projects, and deleting projects.

[0062] Project member management includes adding or deleting project members, assigning project roles to project members, setting project member permissions and responsibilities, etc.

[0063] Project members include: project administrators, project managers, developers, test managers and testers. The project administrator can manage the entire project process and has the highest authority.

[0064] Project managers and developers belong to the R&D side, and they propose test requirements based on the project; test managers and testers belong to the testing side, and they execute test plans and complete test tasks based on test requirements.

[0065] The specific permissions and functions corresponding to each project member are shown in Table 1.

[0066] Table 1 System project member function authority allocation table

[0067]

[0068] The requirement management module is configured to manage requirement information and requirement function points. R&D users can create requirement information based on the corresponding project. The requirement information includes the version information of the tested software, which includes the version name, release time and version description, etc.

[0069] After creating the requirement information, the requirement management module provides the functions of editing requirements, managing requirements, publishing requirements and deleting requirements. The requirement management function supports the creation of requirement function points in a tree form, and supports previewing the content of requirement function points in the form of a mind map. The requirement function points include the requirement name, automatically generated requirement identifier, requirement type, requirement status and the person responsible for the development of the requirement.

[0070] After the content of the requirement function point is created and the requirement is published, new test requirements can be added in the test management module. Modification is not allowed after the requirement is published.

[0071] The test submission management module is configured to manage the test submission requirements and the test submission approval process.

[0072] The test approval process management refers to the R&D project manager creating and submitting test requirements, and the test manager of the testing party determining whether the test content meets the test requirements and approving it.

[0073] After the requirement information is released, the test management module will add new test requirements. The test requirements include the version information of the software under test, the access address or installation package address of the software under test, the test environment, the test tasks, the requirement function points created in the associated requirement management module, the selection of function points to be tested, and the uploading of attachment information (such as software design documents, user manuals, etc.). The tester can select all or part of the function points for this test.

[0074] After adding a new test request, the test request management module provides the functions of editing, viewing, submitting and deleting the test request.

[0075] After adding a new test requirement, it must first be submitted for approval by the test manager to determine whether the content of the test requirement meets the test requirements. If approved, the next step of the testing process can be carried out; if not approved, it will be fed back to the R&D party, and after supplementing and modifying the content of the test requirement, it will be submitted again. The testing party can use this to manage the standardization of the R&D party's test content.

[0076] The approved testing requirements will generate a testing version round by default based on the selected software version. If the selected version is the first testing, the round is 1, if it is the second testing, the round is 2, and so on.

[0077] The use case management module is configured to maintain and manage test cases; test case maintenance and management includes adding and managing test cases.

[0078] After the test requirements are approved, the use case management module can add new test cases, add new test cases, or use existing test case sets to generate test cases.

[0079] The newly added test case includes the basic information of the test case and the steps of the test case. The basic information of the test case includes: the name of the test case, the automatically generated use case identifier, the associated required functional points for testing (the associated functional points selected for testing), the test type, the version of the test case and the steps of the test case.

[0080] The test case steps include the test case operation steps and expected result information; the test case operation steps include the test case set, summary, initialization conditions, test methods, pass criteria and termination conditions.

[0081] After adding a test case, the case management module provides the functions of editing, viewing and deleting the test case.

[0082] The test execution module is configured to manage the test plan execution information and test case execution results. The test plan execution information includes the plan name, the software version under test, the version submitted for test, the start and end time of the execution plan, the execution plan description information, and the execution case selected for this execution plan, and the personnel who will perform the test, and the assignment of test tasks, etc.

[0083] After adding a test case, the test execution module adds a test plan. The tester executes the test operation on the test case according to the test plan. The test case execution results include not executed, passed, failed, and blocked. After executing the failed case, two methods are provided: adding a new problem ticket and associating a problem ticket. Users can create a new problem ticket or select an existing problem ticket by associating the problem ticket number.

[0084] The defect management module is configured to manage defect issues and defect logs.

[0085] The defect management module adds defect problem information based on the execution of the test plan. The defect problems include the defect reporter, assignee, problem type, severity, problem status, priority, frequency of occurrence, problem description, problem details, and the corresponding version of the device under test, version submitted for test, test plan execution, test case set, test execution case and test environment information.

[0086] After adding defect information, the tester can modify, view and delete the defect information; the R&D party can view and modify it.

[0087] Among them, for the modification of defect problem information, the R&D party can only modify the problem status, assignee, and notes on the repair status of the problem ticket.

[0088] Defect log information management includes the change records after the user modifies the defect problem information and the defect note information newly created by the user.

[0089] The defect management module supports recording log information of problem ticket modifications. A defect list can be formed based on the log information. The defect list supports multiple ways to filter defect issues, such as forward filtering, reverse filtering, etc., so that users can better filter and obtain defect issue information.

[0090] Based on the software testing management system provided in the above embodiment, Figure 2 and 3 As shown, the present invention also provides a software testing process management method, the method comprising the steps of:

[0091] S1. Project administrators create software testing projects, manage project information, add project members, and assign project member permissions and responsibilities.

[0092] Project information includes project name and project logo, etc. Project members include project administrators, project managers, developers, test managers and testers. Project administrators can manage the entire project and have the highest authority. Project managers and developers belong to the R&D side, while test managers and testers belong to the testing side. Different permissions and responsibilities are assigned to R&D and testing personnel at different stages.

[0093] S2. The R&D party creates and publishes test requirement information based on the software testing project and adds new testing requirements.

[0094] Requirement information includes the version information of the tested software, including version name, release time and version description, etc. Requirement information includes two states: new and released. Newly added requirement information is displayed as new, and the requirement information is released after review by the project manager, and the status is changed to released. Unreleased requirement information cannot be used for subsequent testing operations, and if there is unreleased requirement information, new requirement information is not allowed.

[0095] After the requirement information has been released, the project manager or developer can add a new test requirement in the test management, enter the basic information of the software to be tested, and select the required functional points associated with the test for testing.

[0096] In the test demand management, there are four statuses for test demand submission: unsubmitted, submitted, approved, and unapproved.

[0097] After adding a test request, the status is displayed as unsubmitted, and after submitting the test request, it is displayed as submitted.

[0098] S3. The testing party approves the testing requirements. After approval, the testing party designs test cases based on the testing requirements and executes the testing plan.

[0099] After the test request is submitted, the testing party will review and approve the content of the request to determine whether the request meets the test requirements. If it does not meet the requirements, it will be displayed as failed approval and returned to the project manager for further modification of the request. If it meets the requirements, it will be displayed as passed approval and subsequent work will be carried out.

[0100] The test manager or tester designs test cases according to the required functional points of the test requirements, adds test cases in the case management module, and completes the design of test cases by selecting the corresponding test rounds, required functional points, test types and steps.

[0101] The test manager or tester uses the test execution module to create a new test plan execution, determine the time period for the test plan execution, the test cases that need to be executed, and assign testers.

[0102] S4. The tester records the execution status of the test case, submits a test problem sheet, and assigns it to the R&D party.

[0103] Testers execute tests according to the test plan and record the execution status of the test cases, which include pass, fail or block.

[0104] After a test case fails to execute, the tester can directly add a new problem ticket or choose to associate an existing problem ticket number. After a test case is blocked, the tester records the reason for the blockage and provides it to the R&D party. After the R&D party fixes the problem, it will be sent to the tester for regression verification.

[0105] After the test party designs the test cases in the test case management module and the test execution module and executes the test cases, the test execution status can be viewed in the test execution module to view the situations where failed and blocked test case problems occur.

[0106] S5. The R&D party fixes, rejects or postpones the test problem based on the test problem list and provides feedback to the test party;

[0107] In the defect management module, the R&D party can view the test problem tickets assigned by the test party and determine whether to modify, postpone or refuse to handle the problems.

[0108] For issues that refuse to be modified, the reasons are noted on the issue ticket, and the problem is closed after confirmation by the testing party. For issues that need to be modified, the impact domain analysis, cause of the problem and solution measures are noted on the issue ticket, and the regression testing party verifies whether it is closed.

[0109] S6. The testing party completes the software testing based on the feedback from the testing issues.

[0110] For fixed issues, if regression verification fails, the issue will be transferred back to the R&D party. For issues that are confirmed to be problems but need to be dealt with later, the issues will be treated as legacy issues, and the testing party will track the deferred issues until the problems are fixed or closed, completing software testing.

[0111] The present invention also provides an electronic device, Figure 4 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention, such as Figure 4 As shown, the electronic device may include: a processor, a communications interface, a memory, and a communications bus, wherein the processor, the communications interface, and the memory communicate with each other via the communications bus. The processor may call the logic instructions in the memory, for example, to execute the following method:

[0112] S1. Project administrators create software testing projects, manage project information, add project members, and assign project member permissions and responsibilities;

[0113] S2. The R&D party creates and publishes test requirement information based on the software test project and adds new test requirements;

[0114] S3. The testing party approves the test request. After approval, the test case is designed according to the test request and the test plan is executed;

[0115] S4. The tester records the execution status of the test case, submits a test problem sheet, and assigns it to the R&D party;

[0116] S5. The R&D party fixes, rejects or postpones the test problem based on the test problem list and provides feedback to the test party;

[0117] S6. The testing party completes the software testing based on the feedback from the testing issues.

[0118] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0119] An embodiment of the present invention further provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the method provided in each of the above embodiments is implemented, for example, including:

[0120] S1. Project administrators create software testing projects, manage project information, add project members, and assign project member permissions and responsibilities;

[0121] S2. The R&D party creates and publishes test requirement information based on the software test project and adds new test requirements;

[0122] S3. The testing party approves the test request. After approval, the test case is designed according to the test request and the test plan is executed;

[0123] S4. The tester records the execution status of the test case, submits a test problem sheet, and assigns it to the R&D party;

[0124] S5. The R&D party fixes, rejects or postpones the test problem based on the test problem list and provides feedback to the test party;

[0125] S6. The testing party completes the software testing based on the feedback from the testing issues.

[0126] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0127] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0128] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A software testing management system, characterized in that: include: Project management module, requirement management module, test management module, use case management module, test execution module and defect management module, including: The project management module is configured to manage project information and project members; The demand management module is configured to manage demand information and demand function points; The test submission management module is configured to manage the test submission requirements and the test submission approval process; The test case management module is configured to maintain and manage the test cases; The test execution module is configured to manage the test plan execution information and the test case execution results; The defect management module is configured to manage defect problem information and defect logs.

2. A software testing management system according to claim 1, characterized in that: The project information management includes determining the project name and project identification; The project member management includes adding or deleting project members, assigning project roles to project members, and setting project member permissions and responsibilities.

3. A software testing management system according to claim 1, characterized in that: The requirement information includes the name of the tested software version, release time and version description; The requirement function point includes the requirement name, automatically generated requirement identifier, requirement type, requirement status and the person responsible for the development of the requirement; The requirement management module provides the creation of requirement function points in the form of a tree structure and supports previewing the content of the requirement function points in the form of a mind map.

4. A software testing management system according to claim 1, characterized in that: The test requirements include the version information of the tested software, the access address or installation package address of the tested software, the test environment, the test tasks, the associated required functional points, and the functional points that need to be tested; The test approval process management refers to the R&D project manager creating and submitting a test request, and the test manager of the testing party determining whether the content of the test request meets the test requirements and approving it.

5. A software testing management system according to claim 1, characterized in that: The test case maintenance management includes adding and managing test cases, and the test cases include: Use case name, automatically generated use case identifier, associated test requirement function points, test type, test version, and use case steps.

6. A software testing management system according to claim 1, characterized in that: The test plan execution information includes the plan name, the version of the software being tested, the version submitted for testing, the start and end time of the execution plan, the execution plan description information, and the execution case selected for this execution plan, the personnel who will perform the test, and the assignment of the test tasks; The use case execution results include four execution results: not executed, passed, failed and blocked, among which the failed execution result is associated with the problem ticket information.

7. A software testing management system according to claim 1, characterized in that: The defect problem information includes the reporter, assignee, problem type, severity, problem status, priority, frequency of occurrence, problem description, problem details, and the corresponding version of the tested device, version submitted for testing, test plan execution, test case set, test execution case and test environment information; The defect log information management includes the change record after the user modifies the defect problem information and the defect note information newly created by the user.

8. A software testing method applied to the management system according to any one of claims 1 to 7, characterized in that: The method comprises the steps of: S1. Project administrators create software testing projects, manage project information, add project members, and assign project member permissions and responsibilities; S2. The R&D party creates and publishes test requirement information based on the software test project and adds new test requirements; S3. The testing party approves the test request. After approval, the test case is designed according to the test request and the test plan is executed; S4. The tester records the execution status of the test case, submits a test problem sheet, and assigns it to the R&D party; S5. The R&D party fixes, rejects or postpones the test problem based on the test problem list and provides feedback to the test party; S6. The testing party completes the software testing based on the feedback from the testing issues.

9. The software testing method according to claim 8, characterized in that: Said After the R&D party fixes the test problem, it will be sent to the test party for regression verification. If the regression verification fails, the problem will be transferred back to the R&D party until it is fixed or closed; After the R&D party refuses to handle the test issue, the test party closes the test issue; After the R&D party defers the testing issue, the testing party will track the deferred issue until it is fixed or closed.

10. The software testing method according to claim 8, characterized in that: In S4, the tester records the execution status of the test case, including pass, fail or block, where: After a test case fails, the tester can directly create a new issue ticket or choose to associate an existing issue ticket number; After the test case execution is blocked, the test party records the cause of the blockage and provides it to the R&D party. After the R&D party fixes the problem, it sends it to the test party for regression verification.

Images