WO2019100576A1

WO2019100576A1 - Automated test management method and apparatus, terminal device, and storage medium

Info

Publication number: WO2019100576A1
Application number: PCT/CN2018/073376
Authority: WO
Inventors: 伍振亮; 伍朗
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-11-27
Filing date: 2018-01-19
Publication date: 2019-05-31
Also published as: CN107908566A

Abstract

Disclosed are an automated test management method and apparatus, a terminal device, and a storage medium. The automated test management method comprises: creating an original test case in a case editing management platform, and sending the original test case to a case audit platform; acquiring, in the case audit platform, a target test case based on the original test case, and sending the target test case to the case editing management platform; acquiring, in the case editing management platform, a target test script based on the target test case, and sending the target test script to a case test management platform; and acquiring, in the case test management platform, a test result by means of testing based on the target test script, wherein the case editing management platform, the case audit platform and the case test management platform are connected via a B/S architecture. The automated testing 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 201711204956.3, 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 testing, 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, the lack of correspondence between test cases and automated test scripts makes the test management platform lack of standardization. As the requirements change, the testers need to update the test cases and test scripts. However, in the existing automated test management methods, the test case modules and test script modules are separated from each other. Therefore, testers need to test cases and tests. The scripts are updated separately, which greatly increases the workload of the testers and takes time.

Summary of the invention

The present application provides an automated test management method, apparatus, terminal device and storage medium to solve the problem of lack of correspondence between test cases and automated test scripts, and low sharing and high maintenance cost of the automated test management platform.

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

Create an original test case in the use case editing management platform and send the original test case 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 editing management platform;

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

Testing in the use case test management platform based on the target test script to obtain test results;

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

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

The original test case obtaining module is configured to create an original test case in the use case editing management platform, and send the original test case to the use case review platform;

a target test case obtaining module, configured to acquire a target test case based on the original test case in the use case review platform, and send the target test case to a use case editing management platform;

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

a test result obtaining module, configured to perform testing based on the target test script in the use case test management platform, and obtain test results;

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:

Create an original test case in the use case editing management platform, and send the original test case to the use case review platform;

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:

In the automatic test management method, device, terminal device and storage medium provided by the present application, the original test case is first created in the use case editing management platform, and the original test case is sent to the use case review platform based on the B/S mechanism, so as to be used in the use case. The audit platform obtains the target test case based on the original test case, and then passes the B/S architecture and sends the target test case to the use case editing management platform. Finally, based on the target test case in the use case editing management platform, the target test script is obtained, and the target test script is sent to the use case test management platform based on the B/S framework to perform test based on the target test script in the use case test management platform, and obtain the test. result. The real-time synchronization between the platforms in the workflow is strong, it is not easy to leak, improve work efficiency, and the use case editing management platform, the use case review platform and the use case test management platform are connected through the B/S architecture, so that the user does not need to download the application. The software is ready to use, with high sharing and low maintenance costs.

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.

1 is a flow chart of an 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. 1.

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

FIG. 5 is a flowchart of an automated test management method provided in Embodiment 1.

FIG. 6 is a specific schematic diagram of step S50 of FIG. 5.

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

FIG. 8 is a specific schematic diagram of step S30 of FIG. 1.

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

FIG. 10 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 utilize the automated test management method to improve test efficiency and reduce test and maintenance costs. As shown in FIG. 1, the automated test management method includes the following steps:

S10: Create the original test case in the use case editing management platform, and send the original test case to the use case review platform.

Among them, the use case editing management platform refers to the management platform used by testers to create test cases. 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. A use case audit platform is a platform that enables auditing of the original test cases sent by testers.

As shown in FIG. 2, in step S10, the original test case is created in the use case editing management platform, and the original test case is sent to the use case review 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.

The configuration interface of the use case editing management platform refers to the interface that the test case editing management platform jumps based on the use case editing instruction when the test case editing instruction input by the tester is clicked on the use case editing button. The use case execution number refers to the execution order of each step in the original test case edited by the tester. In this embodiment, when jumping to the configuration interface of the use case editing management platform, due to limited interface resources, the configuration interface performs execution number according to the preset number of use cases, such as displaying 1-10, etc. in the order of Arabic numerals. The use case execution number; when the tester wants to add a test case, you can choose to add the batch or add one by one to reduce the interface resource occupancy and increase the load rate. Specifically, when the tester wants to add a test case, the use case creation management instruction may be input to the use case editing management platform, where the use case can add a number of use case instruction numbers to be added by the custom input; if the batch addition mode is selected, Customize the batch parameters. When the batch parameter is defined as 1, the option of adding one by one is selected to achieve the convenience of adding.

S12: Associate each use case execution number with a base action to form an original test case.

The basic action is some basic test actions pre-stored by the server, such as the action of "login". In this embodiment, 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 set of test plans including at least one basic action. 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.

As shown in FIG. 3, in step S12, each use case execution number is associated with a basic action to form an original test case, which 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 action name of the test action input by the tester or the action 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 to be achieved by the target action can be input, and the use case editing management platform provides the tester according to the target action input by the tester. A similar basic action corresponding to the target action for the tester to select the target action from the similar basic actions provided, ie the user can select and determine the target action based on the similar base action by inputting a selection instruction to the use case editing management platform. It can be understood that if the similar basic action recommended by the use case editing management platform does not have the 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 development information to the use case editing management platform. The client's client reminds 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 pre-stores a keyword information table including the action name of the basic action as a keyword, and matches the target action and the keyword in the keyword information table by the KMP algorithm to determine a similar basic action. For example, the keyword "open browser" can be a browser. When the tester enters "click browser", the server will be the 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 configuration interface of the use case editing management platform is the interface displayed by the tester when editing the test case. The basic action list refers to a list of actions that are pre-stored in the use case editing management platform and contain at least two basic actions. 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 required basic action (ie, 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, and associate the use case execution number with the base action.

Specifically, the tester can select the required basic action (ie, 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 tester selects the selected The base action (ie the target action) is associated with the use case execution number. In this embodiment, the basic action selected by the tester (ie, the target action) 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.

As shown in FIG. 5, in an embodiment, the automated test management method, before step S10, further includes step S50: pre-configuring the basic action list. As shown in FIG. 6 , the configuration basic action list specifically includes the following steps:

S51: Acquire at least two action editing requests in the use case editing management platform, where the action editing request includes an action name corresponding to the basic action.

Specifically, the developer may input at least two action editing requests on the use case editing management platform to form a basic action list, and the use case editing management platform may call the pre-stored basic action editing template after receiving the basic action editing request. The basic action editing template includes an action name of the base action and a corresponding action execution code. The developer only needs to edit the action name of the basic action and the corresponding action execution code to complete the editing of the basic action, so as to simplify the operation process, save time and improve efficiency.

S52: clustering the at least two action names by using a clustering algorithm, and classifying and managing the basic actions by using the example editing management platform to form a basic action list.

Specifically, the basic action list obtained by clustering the at least two action names by using the K-means clustering algorithm includes at least two cluster class clusters, each cluster class cluster corresponding to a behavior type, and each clustering The class cluster includes a centroid. The cosine similarity algorithm is used to calculate the distance from each action name to the centroid, and the cluster cluster to which the centroid with the smallest calculated distance belongs is used as the category of the action name. 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. The K-MEANS algorithm is an algorithm that inputs the number of clusters k and a database containing n data objects, and outputs an algorithm that satisfies the minimum standard k clusters of variance. The algorithm has low complexity and can process massive data in a short time. ,Improve efficiency.

Further, the step of clustering at least two action names by using the K-maens clustering algorithm is as follows: First, K are randomly selected from at least two action names as a centroid, where k represents the number of cluster clusters. Then, using the word segmentation technique, each action name (including the centroid) is segmented, and the TF-IDF is used to calculate the weight of each word in the corresponding action name to form a feature vector. For example, the word "open browser" is segmented, and the "open" "browser" is used to form a feature vector (the vector dimension of the feature vector is 2); if the dimensions of the feature vectors of the two action names are different, the feature of the largest dimension is taken. The dimension corresponding to the vector is used as the final dimension, and the other feature vector dimensions are insufficient to be filled with 0. Finally, the cosine similarity algorithm is used to calculate the distance between the feature vector corresponding to each action name and the centroid, and the cluster cluster to which the centroid with the smallest distance is calculated is used as the category of the action name. Among them, the number of centroids is determined by the number K of clustering clusters, and the specific K value is customized by the developer. 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.

S20: 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.

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 audit platform sends the original test case to the use case editing management platform for modification. After that, the use case editing management platform sends the modified original test case to the use case review platform for review until the audit passes the target test. Example. 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 embodiment, as shown in FIG. 7, before step S20, the automated test management method further includes performing audit authority configuration on the original test case. The audit permission configuration of the original test case includes the following steps:

S211: 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.

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.

S212: Send the original test case to the use case review platform based on the audit permission configuration request, so that the audit 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, the upload can be directly selected. 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 task information table includes the auditor ID, the auditing mailbox corresponding to the auditor ID, and the corresponding 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.

In a specific implementation, in step S20, the target test case is obtained based on the original test case in the use case review platform, and specifically includes the following steps:

S221: 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.

S222: If the audit identifier is an audit pass identifier, the original test case is used as a 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.

S30: Obtain a target test script based on the target test case in the use case editing management platform, and send the target test script to the use case test 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.

As shown in FIG. 8 , in step S30, 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:

S31: In the use case editing management platform, based on the target test case, sequentially execute the action execution code corresponding to the at least two use case execution numbers to form the original test script.

The use case execution number is also associated with an 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 instruction includes an action ID. 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.

S32: Acquire a script modification instruction input by the user, and 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.

S33: Modify an action execution code corresponding to the action ID in the original test script to form a target test script based on the adjustment parameter.

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.

S40: Perform test based on the target test script in the use case test management platform to obtain test results.

Among them, the test results include pass and fail. 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 of the system to be tested in the use case test management platform to increase work efficiency.

Specifically, the use case test management platform can send the failed test results to the use case defect management platform for analysis. The use case defect management platform displays a defect list including at least one defect type, each defect type including a test defect description and a test defect resolution method. In this embodiment, when the use case defect management platform analyzes the defect of the untested test result (ie, the target defect), the analyst may select a defect type similar to the target test defect from the defect list, and the defect is managed by the use case defect management platform. The test defect description and test defect resolution method corresponding to the type, generate a defect report in the html (Hypertext Markup Language) format, and send the defect report 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 resolution and increase productivity.

In this embodiment, the use case defect management platform includes a defect report template, and the defect report template includes a defect type module, a defect description module, and a defect resolution method module. When testing, the analyst only needs to select a defect similar to the target test defect from the defect list. Type, you can generate defect reports, save time and improve work efficiency.

In this embodiment, the use case editing management platform, the use case review platform, the use case test management platform, and the use case defect 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.

In this embodiment, the original test case is created in the use case editing management platform, and the original test case is sent to the use case review platform based on the B/S mechanism, so as to obtain the target test case based on the original test case in the use case review platform. The target test case is then sent to the use case editing management platform through the B/S architecture. Finally, based on the target test case in the use case editing management platform, the target test script is obtained, and the target test script is sent to the use case test management platform based on the B/S framework to perform test based on the target test script in the use case test management platform, and obtain the test. result. The real-time synchronization between the platforms in the workflow is strong, it is not easy to leak, improve work efficiency, and the use case editing management platform, the use case review platform and the use case test management platform are connected through the B/S architecture, so that the user does not need to download the application. The software can be used, the sharing is high and the maintenance cost is low, and the automated test method pre-creates a basic action list for the user to view, the operation flow is simple, saves time, and improves work efficiency.

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. 9 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. 9, the automated test management apparatus includes an original test case acquisition module 10, a target test case acquisition module 20, a target test script acquisition module 30, a test result acquisition module 40, and an action list configuration module 50. The steps of the original test case acquisition module 10, the target test case acquisition 20 module, the target test script acquisition module 30, the test result acquisition module 40, and the action list configuration module 50 and the automatic test management method in the embodiment are one by one. Correspondingly, in order to avoid redundancy, the present embodiment will not be described in detail.

The original test case acquisition module 10 is configured to create an original test case in the use case editing management platform and send the original test case to the use case review platform.

The target test case obtaining module 20 is configured to obtain a 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 module 30 is configured to obtain a target test script based on the target test case in the use case editing management platform, and send the target test platform to the use case test management platform.

The test result obtaining module 40 is configured to perform testing based on the target test script in the use case test management platform, and obtain test results.

The action list configuration module 50 is configured to pre-configure the basic action list.

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

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 base action to form an original test case.

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 obtaining unit 12 further includes a base action list display sub-unit 1221 and a base action selection 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 basic action selection 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 automated test management device further includes an action editing unit 51 and a base action list obtaining unit 52.

The action editing unit 51 is configured to acquire at least two action editing requests in the use case editing management platform, where the action editing request includes an action name corresponding to the basic action.

The basic action list obtaining unit 52 is configured to perform clustering processing on the at least two action names by using a clustering algorithm, and classify and manage the basic actions by using the example editing management platform to form a basic action list.

Preferably, the automated test management apparatus further includes an audit authority configuration acquisition unit 211 and an original test case transmission unit 212.

The audit authority configuration obtaining unit 211 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 unit 212 is configured to send the original test case to the use case review platform based on the audit authority configuration request, so that the audit interface corresponding to the auditor ID displays the original test case.

Preferably, the target test case acquisition module 20 includes an audit instruction acquisition unit 221 and a target test case acquisition unit 222.

The audit instruction obtaining unit 221 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 obtaining unit 222 is configured to use the original test case as the target test case if the audit mark is the audit pass identifier.

Preferably, the target test script acquisition module 30 includes an original test script acquisition unit 31, a script modification instruction acquisition unit 32, and a target test script acquisition unit 33.

The original test script obtaining unit 31 is configured to sequentially execute an action execution code 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 obtaining unit 32 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 obtaining unit 33 is configured to modify an action execution code corresponding to the action ID in the original test script to form a target test script based on the adjustment parameter.

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. 10 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 10, the terminal device 100 of this embodiment includes a processor 101, a memory 102, and computer readable instructions 103 stored in the memory 102 and executable on the processor 101. The processor 101, when executing the computer readable instructions 103, implements the steps in the various automated test management method embodiments described above, such as steps S10 through S40 shown in FIG. Alternatively, the processor 101 implements the functions of the modules/units in the various apparatus embodiments described above when the computer readable instructions 103 are executed, such as the functions of the modules 10 through 50 shown in FIG.

Illustratively, computer readable instructions 103 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 102 and executed by processor 101 to complete the application. The one or more modules/units may be a series of instructions of computer readable instructions capable of performing a particular function, which is used to describe the execution of computer readable instructions 103 in the terminal device 100. For example, the computer readable instructions 103 can be segmented into an original test case acquisition module 10, a target test case acquisition 20 module, a target test script acquisition module 30, a test result acquisition module 40, and an audit authority configuration module 50. The specific functions of each module are as described in Embodiment 2, and are not described herein.

The terminal device 100 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, the processor 101 and the memory 102. It will be understood by those skilled in the art that FIG. 10 is merely an example of the terminal device 100, and does not constitute a limitation of the terminal device 100, and may include more or less components than those illustrated, or combine some 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 101 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), 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 102 may be an internal storage unit of the terminal device 100, such as a hard disk or a memory of the terminal device 100. The memory 102 may also be an external storage device of the terminal device 100, such as a plug-in hard disk equipped on the terminal device 100, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 102 may also include both an internal storage unit of the terminal device 100 and an external storage device. The memory 102 is used to store computer readable instructions 103 and other programs and data required by the terminal device 100. The memory 102 can also be used to temporarily store data that has been or will 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

An automated test management method, comprising:

Create an original test case in the use case editing management platform, and send the original test case 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 editing management platform;

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

Testing in the use case test management platform based on the target test script to obtain test results;

The use case editing management platform, the use case review platform, and the use case test management platform are connected by a B/S architecture.
The automated test management method according to claim 1, wherein the creating the original test case 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;

Each of the use case execution numbers is associated with a base action to form the original test case.
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.
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.
The automated test management method according to claim 1, wherein the original test case is created in the use case editing management platform, and the original test case is sent to the use case review platform, and further comprising: the original test case Perform 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.
The automated test management method according to claim 2, wherein the target test case comprises at least two of the 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:

In the use case editing management platform, based on the target test case, sequentially calling an action execution code corresponding to at least two of the 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;

And modifying, according to the adjustment parameter, an action execution code corresponding to the action ID in the original test script to form a target test script.
The automated test management method according to claim 2, wherein the basic action includes an action name;

Before the step of creating the original test case in the use case editing management platform and sending the original test case to the use case review platform, the automated test management method further includes:

Acquiring at least two action editing requests in the use case editing management platform, where the action editing request includes an action name corresponding to the basic action;

The clustering algorithm is used to perform clustering processing on at least two of the action names, so that the use case editing management platform classifies and manages the basic actions to form a basic action list.
An automated test management device, comprising:

The original test case obtaining module is configured to create an original test case in the use case editing management platform, and send the original test case to the use case review platform;

a target test case obtaining module, configured to acquire a target test case based on the original test case in the use case review platform, and send the target test case to a use case editing management platform;

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

a test result obtaining module, configured to perform testing based on the target test script in the use case test management platform, and obtain test results;

The use case editing management platform, the use case review platform, and the use case test management platform are connected by a B/S architecture.
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:

Create an original test case in the use case editing management platform, and send the original test case 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 editing management platform;

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

Testing in the use case test management platform based on the target test script to obtain test results;

The use case editing management platform, the use case review platform, and the use case test management platform are connected by a B/S architecture.
The terminal device according to claim 9, wherein the creating the original test case 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;

Each of the use case execution numbers is associated with a base action to form the original test case.
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.
The terminal device according to claim 9, wherein after the step of creating an original test case in the use case editing management platform and transmitting the original test case to the use case review platform, the processor executes the The computer readable instructions further implement the following steps: 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.
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:

In the use case editing management platform, based on the target test case, sequentially calling an action execution code corresponding to at least two of the 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;

And modifying, according to the adjustment parameter, an action execution code corresponding to the action ID in the original test script to form a target test script.
The terminal device according to claim 10, wherein the basic action includes an action name;

Before the step of creating the original test case in the use case editing management platform and transmitting the original test case to the use case review platform, the processor further implements the following steps when executing the computer readable instruction:

Acquiring at least two action editing requests in the use case editing management platform, where the action editing request includes an action name corresponding to the basic action;

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

Create an original test case in the use case editing management platform, and send the original test case 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 editing management platform;

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

Testing in the use case test management platform based on the target test script to obtain test results;

The use case editing management platform, the use case review platform, and the use case test management platform are connected by a B/S architecture.
The computer readable storage medium of claim 15, wherein the creating the original test case 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;

Each of the use case execution numbers is associated with a base action to form the original test case.
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.
The computer readable storage medium of claim 15, wherein after the step of creating an original test case in the use case editing management platform and transmitting the original test case to the use case review platform, the computer can When the read instruction is executed by the processor, the following steps are further implemented: 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.
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:

In the use case editing management platform, based on the target test case, sequentially calling an action execution code corresponding to at least two of the 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;

And modifying, according to the adjustment parameter, an action execution code corresponding to the action ID in the original test script to form a target test script.
The computer readable storage medium of claim 16 wherein the base action comprises an action name;

Before the original test case is created in the use case editing management platform, and the original test case is sent to the use case review platform, the processor further implements the following steps when executing the computer readable instruction:

Acquiring at least two action editing requests in the use case editing management platform, where the action editing request includes an action name corresponding to the basic action;

The clustering algorithm is used to perform clustering processing on at least two of the action names, so that the use case editing management platform classifies and manages the basic actions to form a basic action list.