CN112069073A - Test case management method, terminal and storage medium - Google Patents

Abstract

The application discloses a management method, a terminal and a storage medium of a test case, wherein the method comprises the following steps: acquiring an updating instruction of a test case; determining a test case to be updated and content to be updated corresponding to the test case to be updated according to the updating instruction, and executing an updating operation on the test case to be updated based on the content to be updated; and acquiring the updated test case obtained by the updating operation, executing the auditing operation of the updated test case, and storing the updated test case passing the auditing operation into a database. The problems that the existing test cases are not managed completely, so that the test cases are not covered completely, a plurality of different test case versions exist simultaneously, and information is disordered are solved, and the updated and audited test cases are stored in the database in time, so that the management efficiency of the test cases is improved, and the time and cost of testers are saved.

Description

Test case management method, terminal and storage medium

technical field

The present application relates to the technical field of testing, and in particular, to a test case management method, terminal and storage medium.

Background technique

With the advancement of science and technology, various fields have also developed rapidly. Regardless of any industry, there are more and more new functions. For testers, not only the increase of function items, but also the increase of test cases, even as many as thousands. Example. However, at present, the management of test cases still remains in manual operation of excel tables, manual backup, etc. When test cases are added, deleted, modified, etc., the updated information cannot be synchronized to all relevant personnel in time, resulting in test cases. Incomplete coverage, multiple different test case versions coexist, and information confusion.

SUMMARY OF THE INVENTION

By providing a test case management method, a terminal, and a storage medium, the embodiments of the present application aim to solve the problem of imperfect management of existing test cases, resulting in incomplete test case coverage, simultaneous existence of multiple different test case versions, and information confusion The problem.

In order to achieve the above object, on the one hand, the present application provides a test case management method, the test case management method includes the following steps:

Get the update instruction of the test case;

Determine the test case to be updated and the content to be updated corresponding to the test case to be updated according to the update instruction, and perform an update operation on the test case to be updated based on the content to be updated;

The updated test case obtained by the update operation is acquired, the audit operation of the updated test case is performed, and the updated test case that has passed the audit operation is stored in a database.

Optionally, the step of obtaining the updated test case obtained by the update operation, and performing the review operation of the updated test case includes:

When the updated test case is obtained, start the review process of the updated test case;

An audit instruction is sent to an auditor based on the audit process, so that the auditor can audit the updated test case according to the audit instruction.

Optionally, after the step of sending an audit instruction to an auditor based on the audit process, so that the auditor can audit the updated test case according to the audit instruction, it includes:

Obtain the updated test cases that have not passed the review and the result information of the review;

Send the updated test case that fails the review and the result information of the review to the corresponding tester, so that the tester can check the test case that fails the review according to the result information of the review. The updated test case is modified.

Optionally, obtaining the updated test case obtained by the update operation, performing an audit operation of the updated test case, and storing the updated test case that has passed the audit operation in a database after the steps, including:

Obtain the item information to be tested, and obtain the target test case matching the item information to be tested in the database, and the target test case is an updated and approved test case stored in the database in advance;

Execute the test operation of the item to be tested based on the target test case to generate a test report.

Optionally, in the described acquisition of the item information to be tested, the step of acquiring the target test case matching the item information to be tested in the database includes:

Obtain the project requirements in the project information to be tested, and generate corresponding test requirements according to the project requirements;

A target test case matching the information of the item to be tested is acquired from the database based on the test requirement.

Optionally, after the step of obtaining the target test case matching the information of the item to be tested in the database based on the test requirement, the step includes:

If a target test case matching the information of the item to be tested is not obtained in the database based on the test requirement, sending a request for obtaining the target test case;

The target test case is acquired based on the acquisition request, and stored in the database.

Optionally, the step of performing a test operation of the item to be tested based on the target test case to generate a test report includes:

Generate a to-be-tested list based on the target test case, and obtain test data for each item in the to-be-tested list;

A test operation of the item to be tested is performed based on the test data of each item to generate a test report.

Optionally, after the step of performing the test operation of the item to be tested based on the target test case to generate a test report, the step includes:

Obtain the test results in the test report, and determine whether the test results are consistent with the preset results;

If the test result is consistent with the preset result, the data corresponding to the test result is stored in the test case table in the database;

If the test result is inconsistent with the preset result, record data inconsistent with the preset result.

In addition, in order to achieve the above object, another aspect of the present application further provides a terminal, the terminal includes a memory, a processor, and a test case management program stored in the memory and running on the processor, and the processor executes all the test cases. When describing the test case management program, the steps to implement the above test case management method are described.

In addition, in order to achieve the above purpose, another aspect of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the above test case is implemented steps of the management method.

In this embodiment, the update instruction of the test case is obtained, the update operation is performed on the test case to be updated according to the update instruction, the updated test case is further reviewed, and the updated and reviewed test case is stored in the database. By timely storing the updated and approved test cases in the database, the test cases obtained by users in the database are the latest version. Therefore, it solves the problems of incomplete test case management, incomplete test case coverage, simultaneous existence of multiple different test case versions, and confusion of information, which improves the management efficiency of test cases and saves the time and cost of testers. cost.

Description of drawings

FIG. 1 is a schematic structural diagram of a terminal of a hardware operating environment involved in a solution according to an embodiment of the present application;

FIG. 2 is a schematic flowchart of the first embodiment of the management method of the test case of the application;

FIG. 3 is a schematic flowchart of the second embodiment of the management method of the test case of the application;

FIG. 4 is a schematic flowchart of the third embodiment of the management method of the test case of the present application;

FIG. 5 is a schematic flowchart of a fourth embodiment of a management method for a test case of the present application;

FIG. 6 is a schematic flowchart of the fifth embodiment of the management method of the test case of the present application;

FIG. 7 is a schematic flowchart of obtaining the updated test case obtained by the update operation in the test case management method of the application, and performing the review operation of the updated test case;

8 is a schematic flow chart of obtaining the information of the item to be tested in the management method of the test case of the application, and obtaining the target test case matching the information of the item to be tested in the database;

FIG. 9 is a schematic flowchart of performing a test operation of an item to be tested based on the target test case to generate a test report in the test case management method of the present application.

The realization, functional characteristics and advantages of the purpose of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

The main solutions of the embodiments of the present application are: obtaining an update instruction of the test case; determining the test case to be updated and the content to be updated corresponding to the test case to be updated according to the update instruction, and based on the content to be updated Perform an update operation on the test case to be updated; obtain the updated test case obtained by the update operation, perform an audit operation on the updated test case, and review the updated test case that has passed the audit operation. Test cases are stored in the database.

At present, the management of test cases is still in manual operation of excel sheets, manual backup, etc. When test cases are added, deleted, modified, etc., the updated information cannot be synchronized to all relevant personnel in time, resulting in insufficient test case coverage. Complete, multiple different test case versions exist at the same time, and the information is confusing. The present application obtains the update instruction of the test case, performs the update operation on the test case to be updated according to the update instruction, further conducts the review operation on the updated test case, and stores the updated and approved test case in the database. By storing the updated and approved test cases in the database in time, the test cases obtained by the user in the database are the latest version. Therefore, it solves the problems of incomplete test case management, incomplete test case coverage, simultaneous existence of multiple different test case versions, and confusion of information, which improves the management efficiency of test cases and saves the time and cost of testers. cost.

As shown in FIG. 1 , FIG. 1 is a schematic structural diagram of a terminal of a hardware operating environment involved in the solution of an embodiment of the present application.

As shown in FIG. 1 , the terminal may include: a processor 1001 , such as a CPU, a network interface 1004 , a user interface 1003 , a memory 1005 , and a communication bus 1002 . Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (eg, a WI-FI interface). The memory 1005 may be high-speed RAM memory, or may be non-volatile memory, such as disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Optionally, the terminal may further include a camera, an RF (Radio Frequency, radio frequency) circuit, a sensor, a remote control, an audio circuit, a WiFi module, a detector, and the like. Of course, the terminal may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a temperature sensor, etc., which will not be repeated here.

Those skilled in the art can understand that the terminal structure shown in FIG. 1 does not constitute a limitation on the terminal device, and may include more or less components than the one shown, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a test case management program.

In the terminal shown in FIG. 1 , the network interface 1004 is mainly used to connect to the background server and perform data communication with the background server; the user interface 1003 is mainly used to connect to the client (client) and perform data communication with the client; and the processor 1001 can be used to invoke the test case management program stored in memory 1005 and perform the following operations:

Get the update instruction of the test case;

Determine the test case to be updated and the content to be updated corresponding to the test case to be updated according to the update instruction, and perform an update operation on the test case to be updated based on the content to be updated;

The updated test case obtained by the update operation is acquired, the audit operation of the updated test case is performed, and the updated test case that has passed the audit operation is stored in a database.

Referring to FIG. 2 , FIG. 2 is a schematic flowchart of the first embodiment of the test case management method of the present application.

This embodiment of the present application provides an embodiment of a method for managing test cases. It should be noted that although the logical sequence is shown in the flowchart, in some cases, the shown sequence may be executed in a sequence different from that shown here. or the described steps.

Test case management methods include:

Step S10, obtaining the update instruction of the test case;

During the life cycle of a software product, from the first creation of the product to the final offline, a large number of test cases will be generated in the test case database during this period. To update the test case in , before executing the update operation, you need to obtain the update instruction of the test case. For example, based on the change of the test project requirements, the test cases in the database also need to be modified, deleted, added or re-imported into new test cases, that is, the modification instructions, deletion instructions, addition instructions and import of the test cases need to be obtained correspondingly. instructions etc. Further, since the test cases in the database correspond to different test items, and each test item includes multiple test cases, for example, taking an APP test as an example, in the development process of the APP, regression test cases and UI test cases need to be used , interface test cases, critical path test cases and other test cases. However, these test cases used by the APP may also need to be used in other test projects, such as the development and test projects of the payment platform, etc. Since there are many test cases in the database and different types, it is necessary to obtain the classification management instructions of the test cases. The classification management instruction classifies and manages the test cases in the database. Among them, the test case is a very important type of document in the testing process, it is the core of the test work, a set of input and output standards during testing, and a specific comparison of software requirements. By running the test case, the program can be found errors in .

Step S20: Determine the test case to be updated and the content to be updated corresponding to the test case to be updated according to the update instruction, and perform an update operation on the test case to be updated based on the content to be updated;

Due to the large number and types of test cases in the database, when the update instruction of the test case is obtained, the update instruction needs to be parsed to determine the test case to be updated and the content to be updated corresponding to the test case to be updated. The updated content performs the update operation on the test case to be updated. For example, if the currently obtained modification instruction is for the UI test case in the payment platform page, it is necessary to determine which payment platform UI test case is to be modified based on the modification instruction, and what content is to be modified. If it is obtained based on the modification instruction that the balance display field is added to the display interface of the WeChat payment platform, you need to find the UI test case corresponding to the WeChat payment platform test project in the database, and add the code of the balance display field in the UI test case to complete the process. Modification of UI test cases.

In step S30, the updated test case obtained by the update operation is acquired, the review operation of the updated test case is performed, and the updated test case that has passed the review operation is stored in a database.

The test case management system obtains the updated test case obtained by the update operation, performs the audit operation of the updated test case, and stores the updated test case that has passed the audit operation in the database; wherein, the updated test case Refers to the test cases obtained after completing routine update operations such as adding new use cases, modifying test cases, deleting test cases, importing test cases, and exporting test cases. In order to ensure the accuracy and validity of the updated test case, an audit operation needs to be performed on the updated test case, and the audit operation refers to the actual test inspection performed by the auditor on the updated test case. Specifically, the updated test case is used to test at least one object to be tested multiple times, and the test accuracy rate of the updated test case is counted according to the test results of the multiple tests. If the test accuracy rate reaches the set threshold, the current The updated test case is recorded as a valid test case. For example: if the updated test case is used to test the problem of the mobile terminal splash screen, the updated test case can be used to test the splash screen use case event of the mobile terminal multiple times. If the screen flickering phenomenon occurs, the test result is recorded as passing the review or correct; if the mobile terminal has the screen flickering phenomenon, the test result is recorded as failing the review or error. Further acquisition of the test results is to pass the review or to be the correct updated test case, and store the updated test case in the database. It should be noted that if the test accuracy rate of the updated test case is 98% after multiple tests, the set threshold is 95%, and the test accuracy rate is higher than the set threshold, it means that the updated test case is a valid test. Example.

Further, referring to FIG. 7 , the step of obtaining the updated test case obtained by the update operation, and performing the review operation of the updated test case includes:

Step S31, when the updated test case is obtained, start the review process of the updated test case;

Step S32, sending an audit instruction to an auditor based on the audit process, so that the auditor can audit the updated test case according to the audit instruction.

When the test case management system obtains the updated test case, it initiates the review process of the updated test case, and further sends the review instruction to each reviewer according to the review process, so that the reviewer can perform the updated test according to the received review instruction. Use cases are reviewed. Among them, the reviewers include test team leaders, product managers, development designers and other related reviewers, and can also conduct peer review, group review, department review, and third-party review. Specifically, when the test management system detects an updated test case, it initiates the review process of the test case, and automatically sends the review instruction to each reviewer, wherein the review instruction may be sent by email or by short message Send, and need to be accompanied by the relevant documentation of the test case. After receiving the audit instruction, the auditor will verify the updated test case, such as judging whether the structural arrangement of the test case design is clear and reasonable, whether it is conducive to efficiently covering the requirements, whether the priority arrangement is reasonable, and whether the test requirements are covered. All function points on the test case and whether the test case has good executable, etc. After the audit is completed, a corresponding audit report is generated, and the audit report is uploaded to the test management system, wherein the audit report includes the audit basis, the audit result, the relevant information of the auditor, the modification information of the test case, and the like.

In this embodiment, the update instruction of the test case is obtained, the update operation is performed on the test case to be updated according to the update instruction, the updated test case is further reviewed, and the updated and reviewed test case is stored in the database. By timely storing the updated and approved test cases in the database, the test cases obtained by users in the database are the latest version. Therefore, it solves the problems of incomplete test case management, incomplete test case coverage, simultaneous existence of multiple different test case versions, and confusion of information, which improves the management efficiency of test cases and saves the time and cost of testers. cost.

Further, referring to FIG. 3 , a second embodiment of the method for managing test cases of the present application is proposed.

The difference between the second embodiment of the test case management method and the first embodiment of the test case management method is that the review instruction is sent to the reviewer based on the review process, so that the reviewer can After the steps of the review instruction to review the updated test case, include:

Step S320, obtaining the updated test case that has not passed the review and the result information of the review;

Step S321, sending the updated test case that has not passed the review and the result information of the review to the corresponding tester, so that the tester can check the failed review according to the result information of the review. The updated test case is modified.

When the test case management system obtains the updated test case that has not passed the review, it further obtains the corresponding review result information, sends the test case modification instruction to the tester, and sends the updated test case that has not passed the review to the review. The result information is sent to the corresponding tester; wherein, the tester is the user who updates the test case in the test management system. After receiving the modification instruction, the tester re-modifies the updated test case that has not passed the review according to the review result information. For example, when it is currently obtained that the communication connection test case fails the review, it will further obtain the updated tester corresponding to the communication connection test case, and send the modification instruction and review result information to the tester; if the tester obtains the result information in the review result If the communication connection test case fails to test whether the communication connection of the mobile phone is successful, the communication connection test case needs to be modified.

This embodiment ensures the validity and accuracy of the test cases by resending the test cases that have not passed the review to the testers for modification.

Further, referring to FIG. 4 , a third embodiment of the method for managing test cases of the present application is proposed.

The difference between the third embodiment of the test case management method and the first embodiment and the second embodiment of the test case management method is that the acquisition of the updated test case obtained by the update operation, the execution of the The review operation of the updated test case, and after the step of storing the updated test case that has passed the review operation in the database, includes:

Step S40, obtain the information of the item to be tested, obtain the target test case matching the information of the item to be tested in the database, and the target test case is the updated and approved test case stored in the database in advance ;

The software product in the test project needs to be tested and the performance of the software product is verified before the software product can be put into use. According to different test requirements, it is necessary to select test cases that meet the test requirements. Therefore, when acquiring the information of the item to be tested, it is necessary to obtain the target test case matching the information of the item to be tested in the database; wherein, the information of the item to be tested includes the item name, the item identifier, the software version, the storage path, etc.; The target test case mentioned above is the updated and approved test case stored in the database in advance. Specifically, the test management system is provided with a test project information filling template, and the user fills in the relevant information of the project to be tested in the filling template, such as project name, project logo, project requirements, project attributes, project labels, etc.; Obtain the item information to be tested in the template, and match the item information to be tested with the test case information stored in the database, where the test case information includes: use case identification, use case name, test purpose, test level, reference information, test environment , Preconditions, Test Steps, Expected Results, Designers, etc. For example, the item name and item identifier in the item information to be tested can be matched with the case name and case tag in the test case information respectively, so as to obtain the test case matching the item information to be tested, that is, the target test case. Optionally, if multiple similar test cases are matched based on the matching operation, the selection information of the test case is sent to the user, or the test case with the highest test level or the test case with the latest update time is selected from the multiple test cases.

Further, with reference to Figure 8, the described acquisition of the item information to be tested, the step of acquiring the target test case matching the item to be tested information in the database includes:

Step S41, obtaining the project requirements in the project information to be tested, and generating corresponding test requirements according to the project requirements;

In step S42, a target test case matching the information of the item to be tested is acquired from the database based on the test requirement.

The project requirements in the project information are acquired, and corresponding test requirements are generated according to the project requirements; wherein, the project requirements include software test requirement information submitted by users, software function requirement documents, and expected output result information. Specifically, the user needs to provide the above necessary information according to the system prompts in the filling template in the test case management system, and other detailed requirement information is included in the software testing requirement information document. Among them, each document includes multiple test tasks, for example: the test item to be tested is the test of the mobile phone APP, and the test task is: when there is no network, you can browse the local data; when the client has a new version, there is an update prompt; useful When it comes to location services and camera services, it is necessary to perform a front-end and back-end switching test to check whether the application is normal; check whether the push message is sent according to the specified business rules, etc. Further, corresponding test requirements are generated according to the project requirements of the project to be tested, and the test requirements and the project requirements are in one-to-one correspondence, so as to facilitate identification by the test case management system. Based on the test requirements, the target test cases matching the information of the project to be tested are obtained in the database, for example, the matching test cases in the database are obtained according to the project name.

Step S50: Execute a test operation of the item to be tested based on the target test case to generate a test report.

Obtain the target test case, perform the test operation on the item to be tested based on the target test case, and generate a test report based on the test operation; specifically, if there are currently 10 matching test cases corresponding to the item to be tested, you need to convert these 10 test cases Each is run once, so the project to be tested needs to run 10 test operations. For example, the 10 test cases include 3 connection tests, 2 interface tests, and 5 firewall tests. When executing the tests, the test operations of each test case are executed in sequence according to the built-in test sequence. Further, obtain the test report obtained after each test operation is performed, and store the test report generated by the same test content in the same location, such as establishing different folders for different test contents in advance, and the folder is used to store the test operation. The obtained test report; wherein, the test report records the test content in a table or other forms of documents. Optionally, the test report can be in the form of a hyperlink, and when clicking on the hyperlink, you can enter and document the test content in a table or other forms, wherein the test content recorded in the test report includes each step of the test and The time-consuming and total time-consuming of each test step, the execution of a single step, the test method, the name of the tester, the number of tests, etc.

Further, with reference to FIG. 9 , the step of executing the test operation of the item to be tested based on the target test case to generate a test report includes:

Step S51, generating a list to be tested based on the target test case, and acquiring the test data of each item in the list to be tested;

Step S52: Execute a test operation of the item to be tested based on the test data of each item to generate a test report.

When determining the target test case corresponding to the item to be tested, the test case management system generates a list to be tested according to the target test case, further obtains the test data of each item in the list to be tested, and executes the test data of the item to be tested based on the test data of each item. Test operations and generate corresponding test reports. Wherein, since the items to be tested include many contents to be tested, the corresponding matching target test cases may include multiple ones. Specifically, taking the test of a mobile APP as an example, when testing a mobile APP, the content to be tested includes: installation and uninstallation test, functional use case test, user experience test, update and upgrade test, and database design test, etc., and each test content includes Different test requirements need to be recorded in the form of a table to generate a to-be-tested list; in the to-be-tested list, all the test requirements in the project to be tested can be read, and each test requirement has been matched with a corresponding test Example. For example, the database design test includes general addition, deletion, modification, and query tests; when the business needs to retrieve data from the server and save it to the client, whether the client can save the data locally; when the business modifies the data , After deletion, will the client and server have corresponding update and other test requirements. When performing the test operation, traverse the list to be tested from beginning to end, obtain the test data of each item, and further perform the test operation of the item to be tested according to the test data of each item, such as obtaining the test steps in the test data, according to the test steps Execute the test operation of each step, wherein the test data of each item can be tested multiple times. Record the test results corresponding to each test data, and generate the corresponding test report.

In this embodiment, the project requirements in the project to be tested are acquired, corresponding test requirements are generated according to the project requirements, and target test cases matching the test requirements are acquired, and a test operation is further performed according to the to-be-tested list generated by the target test cases to generate a test report. Configure different test cases for different projects based on project requirements, without the need for testers to blindly rummage through files, automatically match project test cases, and manage test conclusions synchronously, improving work efficiency and saving labor costs.

Further, referring to FIG. 5 , a fourth embodiment of the method for managing test cases of the present application is proposed.

The difference between the fourth embodiment of the test case management method and the first embodiment, the second embodiment and the third embodiment of the test case management method is that the acquisition based on the test requirement in the database After the steps of the target test case matching the information of the item to be tested, include:

Step S420, if a target test case matching the information of the item to be tested is not obtained in the database based on the test requirement, send an acquisition request for the target test case;

Step S421: Obtain the target test case based on the obtaining request, and store it in the database.

If the test case management system does not obtain a target test case matching the information of the item to be tested in the database based on the test requirements, it sends an acquisition request of the target test case to the tester, wherein the acquisition request includes the test requirements of the item to be tested and desired effects. When the tester receives the acquisition request of the target test case, he writes the test case according to the request information in the acquisition request, and uploads the completed test case to the test management system. When the test case is approved and the expected test result is achieved, Then store the test case to the database. Optionally, testers can retrieve test cases that are similar to the target test cases in the test management system, and modify the similar test cases to form the required target test cases, which avoids the tester from rewriting test cases and saves testing. staff time.

In this embodiment, when a completely matching target test case is not obtained, an acquisition instruction for sending the target test case to the tester is acquired, so that the tester can timely feedback the corresponding target test case based on the acquisition instruction, so as to ensure the test of the item to be tested. need.

Further, referring to FIG. 6 , a fifth embodiment of the method for managing test cases of the present application is proposed.

The difference between the fifth embodiment of the test case management method and other embodiments of the test case management method is that after the step of performing the test operation of the item to be tested based on the target test case to generate a test report, include:

Step S53, obtaining the test result in the test report, and judging whether the test result is consistent with the preset result;

Step S54, if the test result is consistent with the preset result, then store the data corresponding to the test result in the test case table in the database;

Step S55, if the test result is inconsistent with the preset result, record the data inconsistent with the preset result.

When the test management system completes the test operation, it will automatically acquire the test results in the test report, and determine whether the test results are consistent with the preset results. Wherein, each test case generates a corresponding test result, that is, it is determined whether the obtained test result of each test case is consistent with the corresponding preset result. For example, if the expected result corresponding to test case A in the project to be tested is "abc" and the actual obtained test result is "abc", it means that the current test result is consistent with the preset result; at this time, the test management system will The successful data of the automatic test is saved to the test case table in the database. If the currently obtained test result is "abcd", it means that the current test result is inconsistent with the preset result. When the test case fails, the test management system will issue a test failure notification, mark the failed test case, and record the test. The data in the failed use case that is inconsistent with the preset result is convenient for testers to modify.

This embodiment judges whether the test result is consistent with the preset result, and if so, stores the data corresponding to the successful test case in the test case table; if not, records the data inconsistent with the preset result. By judging whether the test results are consistent with the preset results, the failed test cases can be found in time, and the management efficiency can be improved.

In addition, the present application also provides a terminal. The terminal includes a memory, a processor, and a management program for test cases stored in the memory and running on the processor. By operating on the terminal, new test cases are added, test cases are modified, and test cases are modified. Batch import of test cases, test case review, test case storage backup, test case classification and matching management, etc., make it unnecessary for testers to write test cases through excel sheets, and realize real-time synchronization and update of test cases to all relevant personnel, ensuring that all personnel get All test cases are the latest and the same version; further, the terminal configures different test cases for different projects according to the project requirements, without the need for testers to blindly look for files, when testers test a specific project, just select the project name , project identification and other information can automatically match project test cases, and can manage test conclusions synchronously, improve work efficiency and save labor costs.

In addition, the present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned test case management method are implemented.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

It should be noted that, in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not preclude the presence of a plurality of such elements. The present application may be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names.

While alternative embodiments of the present application have been described, additional changes and modifications to these embodiments may occur to those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include alternative embodiments and all changes and modifications that fall within the scope of the present application.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (10)

1. A management method for test cases is characterized in that the method comprises the following steps:

acquiring an updating instruction of a test case;

determining a test case to be updated and content to be updated corresponding to the test case to be updated according to the updating instruction, and executing an updating operation on the test case to be updated based on the content to be updated;

and acquiring the updated test case obtained by the updating operation, executing the auditing operation of the updated test case, and storing the updated test case passing the auditing operation into a database.

2. The method according to claim 1, wherein the step of obtaining the updated test case obtained by the update operation and executing the audit operation of the updated test case includes:

when the updated test case is obtained, starting an auditing process of the updated test case;

and sending an auditing instruction to an auditor based on the auditing process so that the auditor can audit the updated test case according to the auditing instruction.

3. The method for managing the test cases according to claim 2, wherein the step of sending an audit instruction to an auditor based on the audit flow so that the auditor performs the audit on the updated test cases according to the audit instruction includes:

acquiring the updated test cases which do not pass the examination and the examination result information;

and sending the updated test case which does not pass the audit and the result information of the audit to corresponding testers so that the testers can modify the updated test case which does not pass the audit according to the result information of the audit.

4. The method according to claim 1, wherein after the steps of obtaining the updated test case obtained by the update operation, performing an audit operation on the updated test case, and storing the updated test case that passes the audit operation in a database, the method comprises:

acquiring information of items to be tested, and acquiring a target test case matched with the information of the items to be tested in the database, wherein the target test case is an updated and approved test case which is stored in the database in advance;

and executing the test operation of the item to be tested based on the target test case to generate a test report.

5. The method for managing test cases according to claim 4, wherein the step of obtaining the information of the items to be tested and obtaining the target test case matched with the information of the items to be tested in the database comprises:

acquiring a project requirement in the to-be-tested project information, and generating a corresponding test requirement according to the project requirement;

and acquiring a target test case matched with the to-be-tested project information in the database based on the test requirement.

6. The method for managing test cases according to claim 5, wherein the step of obtaining the target test case matching the information of the item to be tested in the database based on the test requirement includes:

if a target test case matched with the to-be-tested item information is not obtained in the database based on the test requirement, sending an obtaining request of the target test case;

and acquiring the target test case based on the acquisition request, and storing the target test case in the database.

7. The method for managing test cases according to claim 3, wherein the step of executing a test operation of a to-be-tested item based on the target test case to generate a test report includes:

generating a to-be-tested list based on the target test case, and acquiring test data of each item in the to-be-tested list;

and executing the test operation of the item to be tested based on the test data of each item to generate a test report.

8. The method for managing test cases according to claim 3, wherein after the step of executing the test operation of the item to be tested based on the target test case to generate the test report, the method comprises:

obtaining a test result in the test report, and judging whether the test result is consistent with a preset result;

if the test result is consistent with the preset result, storing the data corresponding to the test result into a test case table in the database;

and if the test result is inconsistent with the preset result, recording data inconsistent with the preset result.

9. A terminal comprising a memory, a processor and a hypervisor of test cases stored on the memory and running on the processor, the processor implementing the steps of the method of any of claims 1 to 8 when executing the hypervisor of test cases.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 8.

Images