WO2019100577A1 - Automated test management method and apparatus, terminal device, and storage medium - Google Patents

Abstract

Disclosed are an automated test management method and apparatus, a terminal device, and a storage medium. The automated test management method comprises: acquiring a target test script in a case editing management platform, and sending the target test script to a case test management platform; acquiring, in the case test management platform, a test result by means of testing based on the target test script, wherein the test result comprises a passed identification or a non-passed identification; the case test management platform uploading the test result carrying the non-passed identification to a case defect management platform; and the case defect management platform analyzing the test result, so as to acquire an analysis result, wherein the case editing management platform, the case test management platform and the case defect management platform are connected via a B/S architecture. The automated test management method has the advantages of a strong real-time synchronism, making it difficult to make mistakes, and improving the work efficiency.

Description

Automated test management method, device, terminal device and storage medium

This patent application is based on the Chinese invention patent application filed on November 27, 2017, with the application number of 201711204948.9, entitled "Automated Test Management Method, Apparatus, Terminal Equipment and Storage Medium", and requires its priority.

Technical field

The present application relates to the field of automated test management, and in particular, to an automated test management method, apparatus, terminal device, and storage medium.

Background technique

The C/S (Client/Server, Client/Server) architecture is a typical two-tier architecture. The client contains one or more programs running on the user's computer. There are two types of servers, one is the database. The server, the client accesses the server's data through a database connection; the other is a Socket server, and the server's program communicates with the client's program through the Socket. At present, most automated test management platforms are based on the C/S architecture, which users need to install before they can be used, with low sharing and high maintenance costs.

In the traditional automated test management platform, after testing the test script through the automated test management platform, only the test results are displayed, and the defect analysis mechanism for analyzing the test results is lacking, and the defects existing in the test results cannot be analyzed and improved. Moreover, when testing with the current test script, the tester independently modifies the test script with defects, and the test script with the same defect may be assigned to different testers for processing separately, which may easily lead to repeated work by different testers. The workload of large testers reduces work efficiency.

Summary of the invention

The present application provides an automated test management method, apparatus, terminal device and storage medium to solve the problem that the current automated test management platform cannot analyze and improve the test scripts with test defects in the test results, and different testers have test scripts with the same defects. Repeated modifications result in inefficient work.

In a first aspect, the application provides an automated test management method, including:

Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.

In a second aspect, the application provides an automated test management apparatus, including:

a target test script obtaining module, configured to obtain a target test script in the use case editing management platform, and send the target test script to the use case test management platform;

a test result obtaining module, configured to perform a test based on the target test script in the use case test management platform, and obtain a test result, where the test result includes an identifier or a failure identifier;

a test result uploading module, configured to upload, by the use case test management platform, the test result carrying the unsigned identifier to the use case defect management platform;

The analysis result obtaining module is configured to analyze the test result on the use case defect management platform to obtain an analysis result.

In a third aspect, the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions The following steps are implemented:

Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.

In a fourth aspect, the present application provides a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the following steps:

Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.

In the automatic test management method, device, terminal device and storage medium provided by the application, the target test script is first obtained in the use case editing management platform, and the target test script is sent to the use case test management platform based on the B/S architecture, and then in the use case The test management platform tests based on the target test script, obtains the test result, and uploads the test result of the failed test by the use case test management platform to the use case defect management platform based on the B/S architecture, and finally, tests the defect in the use case defect management platform. The results were analyzed and the analysis results were obtained to correlate the automated test management platform with the use case defect management platform and to analyze and improve the test results with defects. The real-time synchronization between the platforms in the workflow is not easy to leak. And the use case editing management platform and the use case test management platform are connected through the B/S architecture, so that the user can use without downloading the application software, and the sharing is high and the maintenance cost is low.

DRAWINGS

In order to more clearly illustrate the technical solutions of the present application, the drawings to be used in the description of the present application will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. For ordinary technicians, other drawings can be obtained based on these drawings without paying for creative labor.

Figure 1 is a flow chart of the automated test management method provided in Embodiment 1.

FIG. 2 is a specific schematic diagram of step S10 of FIG. 1.

FIG. 3 is a specific schematic diagram of step S12 of FIG. 2.

FIG. 4 is another specific schematic diagram of step S12 of FIG. 2.

FIG. 5 is a specific schematic diagram of step S13 of FIG. 2.

FIG. 6 is a specific schematic diagram of step S14 of FIG. 2.

FIG. 7 is a specific schematic diagram of step S40 of FIG. 1.

8 is a schematic block diagram of an automated test management apparatus provided in Embodiment 2.

9 is a schematic diagram of a terminal device provided in Embodiment 4.

Detailed ways

The technical solutions in the present application will be clearly and completely described in the following with reference to the drawings in the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

FIG. 1 shows a flow chart of an automated test management method in this embodiment. The automated test management method can be applied to financial institutions such as banks, securities, insurance, or other institutions that need to automatically test the system, so as to improve test quality and improve work efficiency by using the automated test management method. As shown in FIG. 1, the automated test management method includes the following steps:

S10: Obtain a target test script in the use case editing management platform, and send the target test script to the use case test management platform.

Among them, the use case editing management platform refers to the platform used by testers to obtain target test scripts. The target test script is a test script obtained by scripting a test case edited by a tester. Specifically, the use case editing management platform sends the obtained target test script to the use case test management platform, and sends the reminder information to the test management mailbox to enhance the real-time synchronization of the work management process.

As shown in FIG. 2, in step S10, the target test script is obtained in the use case editing management platform, which specifically includes the following steps:

S11: Display at least two use case execution numbers sequentially on the configuration interface of the use case editing management platform.

Among them, the use case editing management platform refers to the management platform used by testers to create test cases. The configuration interface of the use case editing management platform is the interface displayed by the tester when editing the test case. Specifically, when the test case editing instruction input by the tester when clicking the use case editing button, the use case editing management platform jumps based on the use case editing command. Interface. The use case execution number is the number of the execution order of each test execution step in the original test case edited by the tester.

In this embodiment, when the terminal device jumps to the configuration interface of the use case editing management platform, because the interface resource is limited, the configuration interface performs the execution number according to the preset number of use cases, such as displaying 1-10 in the order of Arabic numerals. Wait for 10 use cases to execute the number. When the tester wants to add test cases, you can choose batch add mode or add one by one to reduce the interface resource share and increase the load rate. Specifically, when the tester wants to add the test execution step of the test case, the "add number" button in the configuration interface of the use case editing management platform may be clicked to input an execution number addition instruction to the use case editing management platform, and the execution number is added. The number of use case execution numbers to be added to the input can be customized. If the batch addition mode is selected, the number of execution number of the use case is defined as an integer greater than 1. If the item-by-add method is selected, the number of execution numbers of the use case is defined. It is 1 for the purpose of adding convenience.

S12: On the use case editing management platform, each use case execution number is associated with a basic action to form an original test case, and the original test case is sent to the use case review platform.

The original test case refers to a set of test scenarios including test execution steps obtained by the tester according to the requirements of the system to be tested. The basic action is some basic test action pre-stored by the server, such as the action of "login". The use case test management platform is a management platform based on test case editing test scripts. A use case audit platform is a platform that enables auditing of the original test cases sent by testers. Specifically, each use case execution number is associated with a required basic action selected by the tester in the pre-stored basic action (hereinafter referred to as a target action) to form a group comprising at least two basic actions, and at least two The test scenario in which the execution order between the base actions corresponds to the use case execution number, that is, the original test case.

Since at least two use case execution numbers are sequentially displayed and sequentially executed, the original test cases formed based on the basic actions associated with the use case execution number can be executed strictly in accordance with the use case execution number display and execution order in subsequent tests. Ensure that the test to be tested can be performed in the order of the basic actions in the original test case designed by the user to enhance the accuracy of the test. In this embodiment, the use case editing management platform sends the obtained original test case to the use case test management platform, and sends the reminder information to the test management mailbox, thereby enhancing the real-time synchronization of the test script editing process.

As shown in FIG. 3, in step S12, each use case execution number is associated with a basic action, and specifically includes the following steps:

S1211: Acquire an action selection instruction input by the user in an input box corresponding to each use case execution number, and the action selection instruction includes an action ID and/or an action name.

The action selection instruction is an instruction for selecting a desired action of the user. The action ID is an identifier for uniquely identifying a base action pre-stored in the server. The action name refers to the name of the test action input by the tester or the name of the base action pre-stored in the server. Specifically, each use case execution number corresponds to an input box to enable the tester to input the target action, and the tester can input only the action ID, or only input the action name, or can input the action ID and the action name at the same time, and complete the input. After clicking the OK button, the corresponding action selection instruction can be input to obtain the required basic action based on the action selection instruction.

S1212: Associate the basic operation with the use case execution number based on the action ID and/or the action name.

Specifically, the manner in which the tester obtains the target action may be as follows: First, when the tester knows the action ID and/or the action name of the target action stored in the server in advance, the action ID and/or action of the target action may be directly input. Name to get the target action. Second, when the tester does not know the action ID and/or the action name of the target action stored in the server, the target action name to be achieved by the target action may be input, and the use case editing management platform will test according to the target action name input by the tester. The person provides a similar basic action corresponding to the target action for the tester to select the target action from the similar basic actions provided, that is, the user can input an action selection instruction to the use case editing management platform, so as to select an instruction based on the action Similar basic actions determine the target action. It can be understood that if the similar basic action recommended by the use case editing management platform does not have a target action to be used by the user, the use case editing management platform generates a reminder information for reminding the developer to load the target action, and sends the reminder information to the use case editing management platform. The developer's client is used to remind the developer to perform basic action development based on the reminder information, which makes the use case editing management platform more practical and meets the needs of testers.

Further, when the use case editing management platform recommends a similar basic action to the tester, the keyword matching algorithm may be used to obtain a similar basic action corresponding to the target action. Among them, the keyword matching algorithm includes but is not limited to the Knuth-Morris-Pratt (KMP) algorithm. Specifically, the KMP algorithm is an improved string matching algorithm. The key of the KMP algorithm is to use the information after the matching failure to minimize the number of matching between the pattern string and the main string to achieve fast matching. In this embodiment, the KMP algorithm is used to perform keyword matching on the target action input by the tester and the action name stored in the database, to obtain similar basic actions, save time, and improve efficiency.

Specifically, the server stores a keyword information table in which the action name of the basic action is stored, and each action name corresponds to one or more keywords, and the target action and the keyword information table are matched by the KMP algorithm. Key words to determine similar underlying actions. For example, the keyword "open browser" can be a browser. When the tester inputs "click browser", the server will be a tester in the pre-stored keyword information table by matching the keyword "browser". It is recommended to "open the browser" to facilitate the use of testers to enhance the user experience.

In another embodiment, as shown in FIG. 4, in step S12, each use case execution number is associated with a basic action, and specifically includes the following steps:

S1221: Display a basic action list on the configuration interface of the use case editing management platform, where the basic action list includes at least one basic action.

The basic action list refers to an action list that is pre-stored in the use case editing management platform and includes at least one basic action. In this embodiment, the basic action list is displayed in a hierarchical list on the configuration interface of the use case editing management platform. Specifically, the tester can also select the target action according to the basic action list, so that the tester can quickly view all the basic actions stored by the server and improve the user experience.

S1222: Drag and drop a basic action into an input box corresponding to a use case execution number by using a drag and drop method, so that the use case execution number is associated with the basic action.

Specifically, the tester can select the target action in the basic action list by dragging and dropping, and drag it to the input box corresponding to the use case execution number, so that the target action selected by the tester is associated with the use case execution number. . In this embodiment, the target action selected by the tester is input into the input box corresponding to the use case execution number by using a drag and drop method, and the operation process is simple, and the work efficiency is improved.

S13: Based on the original test case in the use case review platform, obtain the target test case, and send the target test case to the use case editing management platform.

Among them, the target test case refers to the auditor reviewing the original test case and marking the test case obtained after the audit is passed. If the audit fails, the use case auditing platform will send the original test case to the use case editing management platform for modification. After that, the use case editing management platform will send the modified original test case to the use case review platform for review, until the review is passed. Target test case. Or, if the audit fails, the use case audit platform can obtain the audit modification instruction input by the auditor, and modify the original test case based on the audit modification instruction to obtain the target test case.

In a specific implementation, before step S13, the automated test management method further includes performing audit authority configuration on the original test case. As shown in FIG. 5, the configuration of the audit permission for the original test case specifically includes the following steps:

S1311: Obtain an audit permission configuration request input by the user in the use case editing management platform, and the audit authority configuration request includes an auditor ID.

Specifically, when the tester saves the original test case, if the auditor needs to specify the auditor to review the original test case, the test permission configuration button displayed on the interface may be selected, and the use case editing management platform may obtain The audit authority configuration request entered by the user, the audit authority configuration request includes the auditor ID, so that the original test case is assigned to the auditor corresponding to the auditor ID. Among them, the auditor ID is a unique identifier that identifies the auditor.

S1312: Send the original test case to the use case auditing platform based on the audit permission configuration request, so that the auditing interface corresponding to the auditor ID displays the original test case.

Specifically, when the tester corresponding to the auditor ID specifies the original test case, the tester clicks upload, and the use case editing management platform can send the original test case to the audit interface corresponding to the auditor ID, and give The auditing email corresponding to the auditor ID sends an alert message.

Understandably, if the tester does not need to specify the auditor to review the original test case, he or she can directly select the upload. The use case editing management platform will directly send the original test case to the use case audit platform and be allocated by the use case review platform. Specifically, the work tasks of each auditor in the use case review platform include a work task to be completed and a work task completed. The server periodically counts and records the task to be completed for each auditor in the use case auditing platform, and the audit task information table includes the auditor ID, the audit mailbox corresponding to the auditor ID, and the corresponding work task to be completed. . In this embodiment, the upper limit of each auditor's task to be completed is predefined. When the use case auditing platform receives the original test case without the designated auditor, it searches for the work task to be completed corresponding to the auditor in turn. If the number of the task to be completed does not reach the upper limit, the auditor ID is obtained. The audit platform sends the original test case to the audit interface corresponding to the auditor ID, and sends a reminder message to the audit mailbox corresponding to the auditor ID. This process improves the efficiency by reasonably allocating work tasks to achieve rational use of resources.

Specifically, in step S13, the target test case is obtained based on the original test case in the use case review platform, and specifically includes the following steps:

S1321: Obtain an audit instruction on the audit interface corresponding to the auditor ID, and the audit instruction includes an audit identifier.

In this embodiment, each auditor logs in to the audit interface corresponding to the auditor ID through his login account; in the use case audit platform, the auditor can select any original test case to be audited to input the selection audit command. In order for the review interface to display the original test case corresponding to the audit selection instruction. During the audit, the auditor should click the “Audit Pass” and “Audit Passed” buttons displayed on the audit interface to output the corresponding audit instruction. The audit ID carried by the audit instruction may be the audit pass identifier or the audit. By identification.

S1322: If the audit identifier is an audit pass identifier, the original test case is used as the target test case.

Specifically, the auditor audits the original test case according to his own judgment. If the original test case passes the audit, the auditor will mark the original test case as the approval pass (ie, the audit pass mark) and select the confirmation save. The use case review platform is The target test case with the audit pass identifier may be sent to the use case editing management platform when the audit identifier of the original test case is obtained. If the original test case fails the audit, the auditor will mark the original test case as unapproved (ie, the audit fails the identification) and confirm the save. The use case review platform will obtain the audit modification instruction, which includes the audit modification. The use case management mailbox corresponding to the opinion and use case editing management platform. The use case review platform enhances the automated test management process by sending the original test case with the audit failed identifier and the review modification comments to the use case editing management platform and sending the reminder information to the mailbox corresponding to the developer who created the original test case. Synchronization, not easy to leak, improve work efficiency.

In this embodiment, if the auditor has an error in the mark of the original test case, the change can be made without checking the save state, and the use case review platform will only have the review when receiving the instruction to confirm the save state. The original test case of the identification is sent to the use case editing management platform to improve the fault tolerance of the management process.

S14: Obtain a target test script based on the target test case in the use case editing management platform.

Among them, automated testing needs to be tested according to the test script, so the target test case needs to be scripted. Specifically, the target test script is a test script obtained by scripting the target test case. The use case editing management platform will send the obtained target test script to the use case test management platform, and send reminder information to the test management mailbox to enhance the real-time synchronization of the work management process.

Specifically, as shown in FIG. 6 , in step S14, the target test scenario is obtained based on the target test case in the use case editing management platform, and specifically includes the following steps:

S141: In the use case editing management platform, based on the target test case, sequentially calling the basic actions corresponding to the at least two use case execution numbers to form the original test script.

The use case execution number is associated with the base action, and the database stores the action execution code corresponding to the action ID of each base action. Specifically, after receiving the target test case sent by the use case review platform and carrying the audit pass identifier, the use case editing management platform acquires the use case scripting instruction input by the tester. The use case scripting instructions include an action ID associated with at least two use case execution numbers. The use case editing management platform sequentially calls the action execution code corresponding to each use case execution number in the target test case based on the action ID to form the original test script. This process eliminates the need for the tester to rewrite the test script according to the target test case, and can directly call the stored action execution code, saving time and improving work efficiency.

S142: Acquire a script modification instruction input by the user, where the script modification instruction includes an action ID and an adjustment parameter.

It can be understood that the action execution code corresponding to each basic action includes a method function and corresponding original parameters. The adjustment parameter refers to the parameter input by the tester when the original test script is modified according to the system requirements. Specifically, the action execution code includes a method function for implementing the base action and corresponding original parameters; at this time, the user may input a script modification instruction to the use case editing management platform to modify the original parameter to the adjustment parameter in the script modification instruction. For example, when the basic action selected by the tester is “open browser”, the corresponding action execution script includes a method function for implementing the function of the print browser and corresponding original parameters, and the URL of the browser can be changed, and the input is performed. The required adjustment parameters (ie the required URL) are needed to make the original test case more suitable for the system to be tested.

S143: Modify the original test script to form a target test script based on the adjustment parameters.

Specifically, the action execution code corresponding to the action ID in the original test script is modified by the adjustment parameter corresponding to each action execution code acquired in step S32 to form a target test script, and the target test script is sent to the use case test management platform. In this embodiment, before sending the target test script to the use case test management platform, the tester ID and the corresponding mailbox for receiving the test result may be configured, so that the system to be tested corresponds to a tester to enhance the work management process.

S20: Perform test based on the target test script in the use case test management platform, and obtain test results, and the test results include identification or failure identification.

Among them, the test results include identification and failure identification. Specifically, after the test is completed, the use case test management platform sends the test result to the mailbox corresponding to the tester ID. In this embodiment, the tester can also perform batch test on the system to be tested in the use case test management platform to improve work efficiency.

In this embodiment, the use case editing management platform and the use case test management platform are connected through the B/S architecture. Among them, the B/S architecture is the browser and server structure. Under this structure, the user work interface is implemented by the WEB browser. Very few transaction logic is implemented in the browser, but the main transaction logic is on the server ( Server) implementation. The B/S architecture is a network structure mode after the rise of WEB. The WEB browser is the most important application software for the client. Users do not need to download, just install the browser to use, greatly reducing maintenance costs.

S30: The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform.

Among them, the use case defect management platform refers to the platform for analysts to analyze the test results and obtain defect reports. Specifically, after the use case test management platform receives the test result carrying the failed identifier, the test result is uploaded to the use case defect management platform, and the reminder information is sent to the defect management mailbox. In this embodiment, when the tester performs batch test on the test system, multiple test results carrying the failed identifier may be obtained, and the tester pops up a window of “whether to select batch upload” when clicking “upload”. The tester only needs to click “Yes” to input the batch uploading instruction. Based on the batch uploading instruction, the selected plurality of test results carrying the unidentified identification can be batch uploaded to the use case defect management platform to meet the user requirements.

S40: The use case defect management platform obtains the analysis result formed based on the analysis of the test result.

Specifically, the analyst can analyze the test results in the use case defect management platform, and obtain the analysis results in the following two ways:

First, the use case defect management platform has the function of automatically recommending test defects. Specifically, the test result received by the use case defect management platform includes a test case execution number and a basic action corresponding to the test case execution number. Since the server stores the keyword information table in advance, the action information name of the base action is stored in the keyword information table. Each action name corresponds to one or more keywords. Therefore, the use case defect management platform extracts the keyword corresponding to the basic action based on the keyword information table and matches the test defect name in the pre-stored test defect list in the server, and automatically recommends the matching test defect name to the user. The analysis results are formed and are convenient for users to use.

Second, the analyst believes that the test defect name automatically recommended by the platform is not ideal. The analyst can also manually add the test defect name and defect processing method of the test defect obtained by the analysis to form the analysis result, and the platform will manually add the test defect by the analyst. The name is updated to the database in real time, so that when the test defect occurs again, the tester does not need to repeatedly change the test script corresponding to the test defect, thereby reducing the workload of the tester and improving work efficiency.

Further, the use case defect management platform further sends the obtained analysis result to the use case editing management platform and/or the use case test management platform, and the use case editing management platform and/or the use case test management platform send the reminder information to the target test script. The corresponding mailbox (such as the tester) and the test management mailbox are processed by the processing personnel, so that the relevant processing personnel can follow up the test processing state in real time, and process in time to improve work efficiency. In this embodiment, the use case editing management platform, the use case test management platform, and the use case defect management platform are connected through the B/S architecture.

Specifically, before uploading the test result to the use case defect management platform, the tester can specify the analyst in the use case defect management platform for analysis; click the analyst configuration button displayed on the interface, at this time, the use case test management platform will obtain the user. The input analyst configuration request includes an analyst ID to assign the original test case to the analyst corresponding to the analyst ID, and send the reminder information to the analysis mailbox corresponding to the analyst ID. Among them, the analyst ID is a unique identifier that can identify the analyst.

It can be understood that when the test result uploaded by the use case test management platform is received by the use case defect management platform, if the tester does not specify an analyst to perform the analysis, the server will perform statistics on each of the analyst's work tasks to be completed. Specifically, the use case defect management platform performs timing statistics on each of the analysts' work tasks to be completed in the use case defect management platform, and stores an analysis task information table, where the analysis task information table includes an analyst ID and an analysis mailbox corresponding to the analyst ID. And the corresponding work task to be completed. In this embodiment, the upper limit of each analyst's work task to be completed is predefined. When the use case defect management platform receives the test result of carrying the unidentified identifier of the unspecified analyst, the task to be completed corresponding to the analyst is searched in turn, and if the number of the task to be completed does not reach the upper limit, the The analyst ID, the use case defect management platform will send the carrying failure test result to the analysis interface corresponding to the analyst ID, and send the reminder information to the analysis mailbox corresponding to the analyst ID. This process improves the efficiency by reasonably allocating work tasks to achieve rational use of resources.

In a specific embodiment, prior to step S40, the automated test management method further includes pre-creating a test defect list in the use case defect management platform. The test defect list includes at least one test defect information, and each test defect information includes a test defect name and a defect processing method. The test defect name is a brief description of the test defect that failed the test. The defect processing method is a method of solving the above-mentioned test defects that have not passed the test. As shown in FIG. 7, the test defect list is pre-created in the use case defect management platform, and specifically includes the following steps:

S411: Acquire at least two defect editing requests in the use case defect management platform, where the defect editing request includes a test defect name and a defect processing method.

Specifically, when the analysis result of the test result of the unsuccessful identifier uploaded by the use case test management platform is displayed on the use case defect management platform, the analyst may determine the corresponding test defect name based on the test result and upload the corresponding test defect to the user defect management platform. The test defect name and defect processing method, after clicking the confirmation button, the defect editing request can be input to the use case defect management platform. When each defect editing request obtained by the use case defect management platform is stored, the test defect name and the corresponding defect processing method are stored in the database corresponding to the use case defect management platform, for example, the name of the test defect is "the text in the button control is truncated. ", the corresponding defect processing method is to set the background color of the button to replace the background color of the system, so that the text is completely displayed. The processing efficiency is improved by pre-storing the test defect name and the corresponding defect processing method in the database, so as to facilitate subsequent processing by calling the corresponding defect processing method.

S412: Clustering the at least two test defect names by using a clustering algorithm, and classifying and managing the test defect names by using the defect management platform to form a hierarchically displayed test defect list.

The test defect list is a pre-stored defect list including at least two test defects. Specifically, the K-means clustering algorithm is used to cluster at least two test defect names, and the defect management platform is used to classify the test defect names to form a hierarchically displayed test defect list, which is convenient for management and can make the user It can more intuitively view all test defects stored in the server and improve the user experience.

In this embodiment, the steps of clustering at least two action names by using the K-maens clustering algorithm are as follows: First, K are randomly selected from at least two test defect names as a centroid, where k represents a cluster class. The number of clusters. Then, each test defect name (including the centroid) is segmented by word segmentation technology, and the TF-IDF is used to calculate the weight of each word in the corresponding test defect name to form a feature vector. In this embodiment, the word segmentation technique can use the staging word segmentation tool to perform word segmentation, and the stutter word segmentation tool is a common Chinese word segmentation tool, which has the advantages of high accuracy and high efficiency. For example, the word "missing text" is segmented, and the "missing" "text" is formed to form two vector dimension feature vectors; if the dimension of the feature vector of the two action names is different, the dimension corresponding to the feature vector of the largest dimension is taken as the final dimension. If other feature vector dimensions are insufficient, they can be filled with 0. Finally, the cosine similarity algorithm is used to calculate the distance between the feature vector and the centroid of each action name, and the cluster cluster to which the centroid with the smallest distance is calculated is used as the category of the action name to achieve the hierarchical display test defect list. the goal of. Among them, the cosine similarity algorithm, also known as the cosine similarity algorithm, is an algorithm for evaluating their similarity by calculating the angle cosine of two vectors. In this embodiment, the number of centroids is determined by the number K of clustering clusters, and the specific K value is customized by the developer.

As shown in FIG. 7, in step S40, the use case defect management platform obtains an analysis result formed based on the analysis of the test result, and specifically includes the following steps:

S421: The use case defect management platform acquires a current defect name formed based on the analysis of the test result.

The current defect name is a name obtained by analyzing the test result, and the current defect name may be obtained by extracting the keyword of the test result, or may be analyzed by the analyst and added to the user defect management platform. A list of pre-stored test defects. As can be appreciated, the current defect name contains keywords corresponding to the base action.

S422: Calculating the similarity between the current defect name and each test defect name by using the cosine similarity degree, selecting the test defect name corresponding to the maximum similarity, and selecting the defect processing method based on the selected test defect name to form an analysis result.

The analysis result refers to the use case defect management platform generated according to the test defect name and the defect processing method, and the analysis result may be a test defect report. The cosine similarity algorithm, also known as the cosine similarity algorithm, is an algorithm that evaluates the similarity of two vectors by evaluating their cosine values. It can be understood that the closer the angle cosine of the two vectors is to 1, the greater the similarity of the two vectors. Specifically, let A = (A ₁ , A ₂ ... A _n ), B = (B ₁ , B ₂ ... B _n ), then the formula for calculating the cosine similarity is

A represents the vector corresponding to the current defect name, B represents the vector corresponding to each test defect name, and the test defect name and defect processing method corresponding to the minimum angle (ie, the cosine value closest to 1) is selected to form the analysis result. .

In this embodiment, when the use case defect management platform analyzes the test defect (ie, the current defect) of the untested test result, the analyst can also independently select the test defect name similar to the current defect name from the test defect list, and the use case defect management platform. The test defect name and defect processing method corresponding to the defect type can be generated to generate a test defect report in the html (hypertext markup language) format, and the defect report is sent to the mailbox corresponding to the tester ID. This process saves time by eliminating the need for analysts to edit defect handling methods, and testers can handle defects based on recommended defect handling methods to increase productivity.

In this embodiment, the target test script is first acquired in the use case editing management platform, and the target test script is sent to the use case test management platform based on the B/S architecture (Browser/Server, browser/server mode), and then used in the use case test management. The platform tests based on the target test script to obtain test results, and the use case test management platform uploads the test result carrying the unsigned identifier to the use case defect management platform based on the B/S architecture, and finally, the test result is performed on the use case defect management platform. Analyze and obtain the analysis results, so that the automated test management platform is associated with the use case defect management platform, and analyze and improve the test results of the defects. Finally, the analysis results are sent to the test management mailbox, so that the user does not need to manually send the analysis results. ,Improve work efficiency. The real-time synchronization between the platforms in the workflow is not easy to leak. And the use case editing management platform and the use case test management platform are connected through the B/S architecture, so that the user can use without downloading the application software, and the sharing is high and the maintenance cost is low.

It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the present application.

Example 2

Fig. 8 is a block diagram showing the principle of an automated test management apparatus corresponding to the automated test management method in the first embodiment. As shown in FIG. 8, the automated test management apparatus includes a target test script acquisition module 10, a test result acquisition module 20, a test result uploading module 30, and an analysis result obtaining module 40. The implementation functions of the target test script acquisition module 10, the test result acquisition module 20, the test result uploading module 30, and the analysis result obtaining module 40 correspond to the steps corresponding to the automated test management method in the embodiment. To avoid redundancy, the implementation The examples are not detailed one by one.

The target test script obtaining module 10 is configured to obtain a target test script in the use case editing management platform, and send the target test script to the use case test management platform.

The test result obtaining module 20 is configured to perform a test based on the target test script in the use case test management platform, and obtain the test result, where the test result includes the identifier or the fail-through identifier.

The test result uploading module 30 is used by the use case test management platform to upload the test result carrying the failed identifier to the use case defect management platform.

The analysis result obtaining module 40 is configured to analyze the test result on the use case defect management platform, and obtain the analysis result.

Preferably, the target test script acquisition module 10 includes a use case execution number display unit 11, an original test case acquisition unit 12, a target test case acquisition unit 13, and a target test script acquisition unit 14.

The use case execution number display unit 11 is configured to sequentially display at least two use case execution numbers on the configuration interface of the use case editing management platform.

The original test case obtaining unit 12 is configured to associate each use case execution number with a basic action on the use case editing management platform to form an original test case, and send the original test case to the use case review platform.

The target test case obtaining unit 13 is configured to obtain the target test case based on the original test case in the use case review platform, and send the target test case to the use case editing management platform.

The target test script obtaining unit 14 is configured to acquire the target test script based on the target test case in the use case editing management platform.

Preferably, the original test case acquisition unit 12 includes an action selection instruction acquisition sub-unit 1211 and a use case execution number association sub-unit 1212.

The action selection instruction acquisition sub-unit 1211 is configured to acquire an action selection instruction input by the user in an input box corresponding to each use case execution number, and the action selection instruction includes an action ID and/or an action name.

The use case execution number association sub-unit 1212 is configured to associate the use number with the base action based on the action ID and/or the action name.

Preferably, the original test case acquisition unit 12 includes a base action list display sub-unit 1221 and a use case execution number association sub-unit 1222.

The basic action list display sub-unit 1221 is configured to display a basic action list on the configuration interface of the use case editing management platform, where the basic action list includes at least one basic action.

The use case execution number association sub-unit 1222 is configured to drag and drop a basic action into an input box corresponding to a use case execution number by using a drag and drop method, and associate the use case execution number with the base action.

Preferably, the target test case acquisition unit 13 includes an audit authority configuration subunit 1311, an original test case transmission subunit 1312, an audit instruction acquisition subunit 1321, and a target test case acquisition subunit 1322.

The audit authority configuration sub-unit 1311 is configured to obtain an audit authority configuration request input by the user in the use case editing management platform, and the audit authority configuration request includes an auditor ID.

The original test case sending sub-unit 1312 is configured to send the original test case to the use case auditing platform based on the auditing authority configuration request, so that the auditing interface corresponding to the auditor ID displays the original test case.

The audit instruction acquisition sub-unit 1321 is configured to obtain an audit instruction on the audit interface corresponding to the auditor ID, and the audit instruction includes an audit identifier.

The target test case acquisition sub-unit 1322 is configured to use the original test case as the target test case for the audit identification to be the audit pass identifier.

Preferably, the target test script acquisition unit 14 includes an original test script acquisition sub-unit 141, a script modification instruction acquisition sub-unit 142, and a target test script acquisition sub-unit 143.

The original test script acquisition sub-unit 141 is configured to sequentially call the basic action corresponding to the at least two use case execution numbers based on the target test case in the use case editing management platform to form an original test script.

The script modification instruction acquisition sub-unit 142 is configured to acquire a script modification instruction input by the user, and the script modification instruction includes an action ID and an adjustment parameter.

The target test script acquisition sub-unit 143 is configured to modify the original test script based on the adjustment parameters to form a target test script.

Preferably, the analysis result acquisition module 40 includes a defect editing request acquisition unit 411, a test defect list acquisition unit 412, a current defect name acquisition unit 421, and an analysis result acquisition unit 422.

The defect editing request obtaining unit 411 is configured to acquire at least two defect editing requests in the use case defect management platform, where the defect editing request includes a test defect name and a defect processing method.

The test defect list obtaining unit 412 is configured to perform clustering processing on the at least two test defect names by using a clustering algorithm, and classify and manage the test defect names by using the example defect management platform to form a hierarchically displayed test defect list.

The current defect name obtaining unit 421 is configured to acquire, by the use case defect management platform, a current defect name formed based on the analysis of the test result.

The analysis result obtaining unit 422 is configured to calculate the similarity between the current defect name and each test defect name by cosine similarity, select a test defect name corresponding to the maximum similarity, and select a defect processing method based on the selected test defect name to form an analysis. result.

Example 3

The embodiment provides a computer readable storage medium on which computer readable instructions are stored, and when the computer readable instructions are executed by the processor, the automatic test management method in Embodiment 1 is implemented. No longer. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the automatic test management apparatus in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.

Example 4

FIG. 9 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 9, the terminal device 90 of this embodiment includes a processor 91, a memory 92, and computer readable instructions 93 stored in the memory 92 and operable on the processor 91. The processor 91 implements the steps in the various embodiments of the method described above when the computer readable instructions 93 are executed, such as steps S10 through S40 shown in FIG. Alternatively, the processor 91 implements the functions of the modules/units in the various apparatus embodiments described above when the computer readable instructions 93 are executed, such as the functions of the modules 10 to 40 shown in FIG.

Illustratively, computer readable instructions 93 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 92 and executed by processor 91 to complete the application. The one or more modules/units may be an instruction segment of a series of computer readable instructions 93 capable of performing a particular function, which is used to describe the execution of computer readable instructions 93 in the terminal device 90. For example, the computer readable instructions 93 may be divided into a target test script acquisition module 10, a test result acquisition module 20, a test result uploading module 30, and an analysis result obtaining module 40. The specific functions of each module are as described in Embodiment 2. One by one.

The terminal device 90 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device may include, but is not limited to, a processor 91, a memory 92. It will be understood by those skilled in the art that FIG. 9 is merely an example of the terminal device 90, does not constitute a limitation of the terminal device 90, may include more or less components than those illustrated, or may combine certain components, or different components. For example, the terminal device may further include an input/output device, a network access device, a bus, and the like.

The processor 91 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (ASIC). Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 92 may be an internal storage unit of the terminal device 90, such as a hard disk or a memory of the terminal device 90. The memory 92 may also be an external storage device of the terminal device 90, such as a plug-in hard disk equipped with the terminal device 90, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 92 may also include both an internal storage unit of the terminal device 90 and an external storage device. The memory 92 is used to store computer readable instructions 93 and other programs and data required by the terminal device. The memory 92 can also be used to temporarily store data that has been output or is about to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium. The computer readable instructions, when executed by a processor, may implement the steps of the various method embodiments described above. Wherein, the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like. The computer readable medium can include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read-Only) Memory), random access memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media It does not include electrical carrier signals and telecommunication signals.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims (20)

1. An automated test management method, comprising:

   Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

   Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

   The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

   The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

   The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.
2. The automated test management method according to claim 1, wherein the obtaining the target test script in the use case editing management platform comprises:

   Displaying at least two use case execution numbers sequentially on the configuration interface of the use case editing management platform;

   On the use case editing management platform, each of the use case execution numbers is associated with a basic action to form an original test case, and the original test case is sent to the use case review platform;

   Obtaining a target test case based on the original test case in the use case review platform, and sending the target test case to the use case edit management platform;

   The target test script is obtained based on the target test case in the use case editing management platform.
3. The automated test management method according to claim 2, wherein the associating each of the use case execution numbers with a basic action comprises:

   Obtaining, in an input box corresponding to each of the use case execution numbers, an action selection instruction input by a user, where the action selection instruction includes an action ID and/or an action name;

   Based on the action ID and/or the action name, the use case execution number is associated with the base action.
4. The automated test management method according to claim 2, wherein the associating each of the use case execution numbers with a basic action comprises:

   Displaying a basic action list on the configuration interface of the use case editing management platform, where the basic action list includes at least one basic action;

   Dragging a base action to an input box corresponding to a use case execution number in a drag and drop manner to associate the use case execution number with the base action.
5. The automated test management method according to claim 2, wherein said target test case comprises at least two said use case execution numbers and corresponding basic actions;

   And obtaining the target test script based on the target test case in the use case editing management platform, including:

   And in the use case editing management platform, based on the target test case, sequentially calling the basic actions corresponding to the at least two use case execution numbers to form an original test script;

   Obtaining a script modification instruction input by a user, where the script modification instruction includes an action ID and an adjustment parameter;

   The original test script is modified based on the adjustment parameters to form the target test script.
6. The automated test management method according to claim 2, wherein said automated test management method further comprises: said original test before said step of reviewing said original test case to obtain a target test case Use case for audit permission configuration;

   Performing audit authority configuration on the original test case, including:

   Obtaining an audit authority configuration request input by the user in the use case editing management platform, where the audit authority configuration request includes an auditor ID;

   Sending, according to the auditing authority configuration request, the original test case to the use case auditing platform, so that the auditing interface corresponding to the auditor ID displays the original test case;

   The acquiring the target test case based on the original test case in the use case review platform, including:

   Obtaining an audit instruction on the audit interface corresponding to the auditor ID, and the audit instruction includes an audit identifier;

   If the audit identifier is an audit pass identifier, the original test case is used as the target test case.
7. The automated test management method according to claim 1, wherein before the step of the use case defect management platform obtaining the analysis result formed based on the analysis of the test result, the automated test management method further comprises: The use defect management platform pre-creates a test defect list, the test defect list including at least one test defect information, each of the test defect information including a test defect name and a defect processing method;

   The analyzing the test result by the use case defect management platform, and obtaining the analysis result, including:

   The test result is analyzed by the use case defect management platform to obtain a current defect name;

   Calculating a similarity between the current defect name and each of the test defect names by using a cosine similarity, selecting a test defect name corresponding to the maximum similarity, and selecting a defect processing method based on the selected test defect name to form the analysis result;

   The pre-creating a defect list of the defect in the use case defect management platform includes:

   Obtaining at least two defect editing requests in the use case defect management platform, the defect editing request including a test defect name and a defect processing method;

   The clustering algorithm is used to perform clustering processing on the at least two test defect names, so that the use case defect management platform classifies and manages the test defect names to form a hierarchically displayed test defect list.
8. An automated test management device, comprising:

   a target test script obtaining module, configured to obtain a target test script in the use case editing management platform, and send the target test script to the use case test management platform;

   a test result obtaining module, configured to perform a test based on the target test script in the use case test management platform, and obtain a test result, where the test result includes an identifier or a failure identifier;

   a test result uploading module, configured to upload, by the use case test management platform, the test result carrying the unsigned identifier to the use case defect management platform;

   The analysis result obtaining module is configured to analyze the test result on the use case defect management platform to obtain an analysis result.
9. A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:

   Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

   Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

   The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

   The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

   The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.
10. The terminal device according to claim 9, wherein the obtaining the target test script in the use case editing management platform comprises:

    Displaying at least two use case execution numbers sequentially on the configuration interface of the use case editing management platform;

    On the use case editing management platform, each of the use case execution numbers is associated with a basic action to form an original test case, and the original test case is sent to the use case review platform;

    Obtaining a target test case based on the original test case in the use case review platform, and sending the target test case to the use case edit management platform;

    The target test script is obtained based on the target test case in the use case editing management platform.
11. The terminal device according to claim 10, wherein the associating each of the use case execution numbers with a basic action comprises:

    Displaying a basic action list on the configuration interface of the use case editing management platform, where the basic action list includes at least one basic action;

    Dragging a base action to an input box corresponding to a use case execution number in a drag and drop manner to associate the use case execution number with the base action.
12. The terminal device according to claim 10, wherein said target test case comprises at least two said use case execution numbers and corresponding basic actions;

    And obtaining the target test script based on the target test case in the use case editing management platform, including:

    And in the use case editing management platform, based on the target test case, sequentially calling the basic actions corresponding to the at least two use case execution numbers to form an original test script;

    Obtaining a script modification instruction input by a user, where the script modification instruction includes an action ID and an adjustment parameter;

    The original test script is modified based on the adjustment parameters to form the target test script.
13. The terminal device according to claim 10, wherein said processor further implements the following steps when said processor executes said computer readable instructions before said step of reviewing said original test case to obtain a target test case : Performing audit authority configuration on the original test case;

    Performing audit authority configuration on the original test case, including:

    Obtaining an audit authority configuration request input by the user in the use case editing management platform, where the audit authority configuration request includes an auditor ID;

    Sending, according to the auditing authority configuration request, the original test case to the use case auditing platform, so that the auditing interface corresponding to the auditor ID displays the original test case;

    The acquiring the target test case based on the original test case in the use case review platform, including:

    Obtaining an audit instruction on the audit interface corresponding to the auditor ID, and the audit instruction includes an audit identifier;

    If the audit identifier is an audit pass identifier, the original test case is used as the target test case.
14. The terminal device according to claim 9, wherein said processor executes said computer readable instructions when said use case defect management platform acquires an analysis result formed based on said test result analysis The following steps: pre-creating a test defect list in the use case defect management platform, the test defect list including at least one test defect information, each of the test defect information including a test defect name and a defect processing method;

    The analyzing the test result by the use case defect management platform, and obtaining the analysis result, including:

    The test result is analyzed by the use case defect management platform to obtain a current defect name;

    Calculating a similarity between the current defect name and each of the test defect names by using a cosine similarity, selecting a test defect name corresponding to the maximum similarity, and selecting a defect processing method based on the selected test defect name to form the analysis result.

    Pre-creating a list of test defects in the use case defect management platform, including:

    Obtaining at least two defect editing requests in the use case defect management platform, the defect editing request including a test defect name and a defect processing method;

    The clustering algorithm is used to perform clustering processing on the at least two test defect names, so that the use case defect management platform classifies and manages the test defect names to form a hierarchically displayed test defect list.
15. A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

    Obtaining a target test script in the use case editing management platform, and sending the target test script to the use case test management platform;

    Performing a test based on the target test script in the use case test management platform, and obtaining a test result, where the test result includes an identifier or a failed identifier;

    The use case test management platform uploads the test result carrying the failed identifier to the use case defect management platform;

    The use case defect management platform obtains an analysis result formed based on the analysis of the test result;

    The use case editing management platform, the use case test management platform, and the use case defect management platform are connected by a B/S architecture.
16. The computer readable storage medium of claim 15, wherein the obtaining the target test script in the use case editing management platform comprises:

    Displaying at least two use case execution numbers sequentially on the configuration interface of the use case editing management platform;

    On the use case editing management platform, each of the use case execution numbers is associated with a basic action to form an original test case, and the original test case is sent to the use case review platform;

    Obtaining a target test case based on the original test case in the use case review platform, and sending the target test case to the use case edit management platform;

    The target test script is obtained based on the target test case in the use case editing management platform.
17. The computer readable storage medium of claim 16, wherein the associating each of the use case execution numbers with a base action comprises:

    Displaying a basic action list on the configuration interface of the use case editing management platform, where the basic action list includes at least one basic action;

    Dragging a base action to an input box corresponding to a use case execution number in a drag and drop manner to associate the use case execution number with the base action.
18. The computer readable storage medium of claim 16 wherein said target test case comprises at least two of said use case execution numbers and corresponding base actions;

    And obtaining the target test script based on the target test case in the use case editing management platform, including:

    And in the use case editing management platform, based on the target test case, sequentially calling the basic actions corresponding to the at least two use case execution numbers to form an original test script;

    Obtaining a script modification instruction input by a user, where the script modification instruction includes an action ID and an adjustment parameter;

    The original test script is modified based on the adjustment parameters to form the target test script.
19. A computer readable storage medium as recited in claim 16, wherein said computer readable instructions are further implemented by said processor prior to said step of reviewing said original test case for obtaining a target test case The following steps: configuring the audit permission for the original test case;

    Performing audit authority configuration on the original test case, including:

    Obtaining an audit authority configuration request input by the user in the use case editing management platform, where the audit authority configuration request includes an auditor ID;

    Sending, according to the auditing authority configuration request, the original test case to the use case auditing platform, so that the auditing interface corresponding to the auditor ID displays the original test case;

    The acquiring the target test case based on the original test case in the use case review platform, including:

    Obtaining an audit instruction on the audit interface corresponding to the auditor ID, and the audit instruction includes an audit identifier;

    If the audit identifier is an audit pass identifier, the original test case is used as the target test case.
20. A computer readable storage medium according to claim 15 wherein said computer readable instructions are executed by said processor prior to said step of obtaining, by said use case defect management platform, analysis results formed based on said test result analysis And implementing the following steps: pre-creating a test defect list in the use case defect management platform, the test defect list including at least one test defect information, each of the test defect information including a test defect name and a defect processing method;

    The analyzing the test result by the use case defect management platform, and obtaining the analysis result, including:

    The test result is analyzed by the use case defect management platform to obtain a current defect name;

    Calculating a similarity between the current defect name and each of the test defect names by using a cosine similarity, selecting a test defect name corresponding to the maximum similarity, and selecting a defect processing method based on the selected test defect name to form the analysis result;

    The pre-creating a defect list of the defect in the use case defect management platform includes:

    Obtaining at least two defect editing requests in the use case defect management platform, the defect editing request including a test defect name and a defect processing method;

    The clustering algorithm is used to perform clustering processing on the at least two test defect names, so that the use case defect management platform classifies and manages the test defect names to form a hierarchically displayed test defect list.

Images