CN111651358B - Method for generating test cases, software testing method, device and server - Google Patents

Abstract

The present invention provides a method for generating test cases, a software testing method, a device and a server. If a test case for a target software needs to be generated, the parameter values of the test case are determined according to the relevant operation data of the user of the target software; a configuration file of the test case is generated according to these parameter values, and then the test case is generated. The method automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, the generation efficiency of test cases is also improved.

Description

Method for generating test cases, software testing method, device and server

Technical Field

The present invention relates to the technical field of software testing, and in particular to a method for generating test cases, a software testing method, a device and a server.

Background technique

Automated testing is an integral part of the software life cycle. At each stage of software development, software can be automatically tested through test cases. Most of the test cases used in automated testing are written manually; then, from the written test cases, a part of the test cases are automatically selected based on the coverage test indicators of the software to be tested, or a part of the test cases are selected manually with the help of experience to test the software to be tested. Since the test cases are written manually, it is time-consuming and labor-intensive on the one hand, and it is difficult to match the actual application scenarios of the software on the other hand, so the accuracy and reliability of the test are low.

Summary of the invention

In view of this, an object of the present invention is to provide a method for generating test cases, a software testing method, an apparatus and a server to improve the efficiency of generating test cases while improving the accuracy and reliability of software testing.

In a first aspect, an embodiment of the present invention provides a method for generating a test case, the method comprising: if a test case for a target software needs to be generated, determining a parameter value of the test case based on user data of the target software; wherein the user data comprises: operation data of a user of the target software operating the target software; generating a configuration file for the test case based on the parameter value; and generating the test case based on the configuration file.

Furthermore, the test case includes at least one use case parameter; the step of determining the parameter value of the test case based on the user data of the target software includes: if it is necessary to determine the parameter value of the use case parameter based on the user data, obtaining user data related to the use case parameter; determining the parameter value of the use case parameter based on the user data related to the use case parameter.

Furthermore, the use case parameter is provided with an identifier; the identifier is used to indicate that: the parameter value of the use case parameter is determined according to the user data, or the parameter value of the use case parameter is a specified value; if the parameter value of the use case parameter needs to be determined according to the user data, the step of obtaining the user data related to the use case parameter comprises: querying the identifier of the use case parameter, and if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to the user data, obtaining the user data related to the use case parameter.

Furthermore, the user data is pre-stored in a preset relational database; at least a portion of the user data is synchronized in a preset cache database; the step of obtaining user data related to the use case parameters includes: obtaining user data related to the use case parameters from the cache database; if the user data related to the use case parameters cannot be obtained from the cache database, obtaining user data related to the use case parameters from the relational database through the cache database.

Furthermore, the step of determining the parameter value of the use case parameter based on user data related to the use case parameter includes: obtaining alternative parameter values of the use case parameter from the user data; if the alternative parameter values include multiple values, determining the parameter value of the use case parameter from the multiple alternative parameter values based on the sizes of the alternative parameter values.

Furthermore, the step of generating a configuration file of the test case according to the parameter value includes: filling the parameter value into the use case parameter corresponding to the parameter value; generating the configuration file of the test case according to the use case parameter and the parameter value corresponding to the use case parameter.

Furthermore, after the step of generating the test case according to the configuration file, the method further includes: obtaining updated user data of the target software at preset time intervals; and updating the test case according to the updated user data.

In a second aspect, an embodiment of the present invention provides a software testing method, the method comprising: if it is necessary to test the target software, obtaining a test case of the target software; testing the target software through the test case to obtain a test result; wherein the test case of the target software is generated in the following manner: determining a parameter value of the test case based on user data of the target software; wherein the user data comprises: operation data of the user of the target software operating the target software; generating a configuration file of the test case based on the parameter value; and generating the test case based on the configuration file.

Furthermore, after the step of testing the target software through the test case, the method further includes: sending the test result to a designated test result receiving address.

In a third aspect, an embodiment of the present invention provides a device for generating test cases, the device comprising: a first determination module, for determining parameter values of the test cases according to user data of the target software if a test case for target software needs to be generated; wherein the user data comprises: operation data of the user of the target software operating the target software; a first generation module, for generating a configuration file of the test case according to the parameter value; and a second generation module, for generating the test case according to the configuration file.

In a fourth aspect, an embodiment of the present invention provides a software testing device, comprising: an acquisition module, used to acquire a test case of the target software if it is necessary to test the target software; a second determination module, used to test the target software through the test case to obtain a test result; wherein the test case of the target software is generated in the following manner: determining a parameter value of the test case based on user data of the target software; wherein the user data includes: operation data of the user of the target software operating the target software; generating a configuration file of the test case based on the parameter value; and generating the test case based on the configuration file.

In a fifth aspect, an embodiment of the present invention provides a server, comprising a processor and a memory, wherein the memory stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the method for generating test cases described in any one of the first aspect above, or the software testing method described in any one of the second aspect above.

In the sixth aspect, an embodiment of the present invention provides a machine-readable storage medium, which stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the method for generating test cases described in any one of the first aspects above, or the software testing method described in any one of the second aspects above.

The method for generating test cases, the software testing method, the device and the server provided by the present invention, if it is necessary to generate test cases for target software, determine the parameter values of the test cases according to the relevant operation data of the users of the target software; generate the configuration files of the test cases according to these parameter values, and then generate the test cases. The method automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, it also improves the efficiency of test case generation.

Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description, claims and drawings.

In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a flow chart of a method for generating a test case provided by an embodiment of the present invention;

FIG2 is a flow chart of another method for generating test cases provided by an embodiment of the present invention;

FIG3 is a flowchart of another method for generating test cases provided by an embodiment of the present invention;

FIG4 is a flowchart of another method for generating test cases provided by an embodiment of the present invention;

FIG5 is a flow chart of a software testing method provided by an embodiment of the present invention;

FIG6 is a flow chart of another software testing method provided by an embodiment of the present invention;

FIG7 is a schematic diagram of the structure of a device for generating test cases provided by an embodiment of the present invention;

FIG8 is a schematic diagram of the structure of a software testing device provided by an embodiment of the present invention;

FIG. 9 is a schematic diagram of the structure of a server provided in an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

In the current software testing industry, automated testing is an integral part of the software life cycle and plays an irreplaceable role in regression testing and continuous integration testing. Test cases can be used to perform automated testing on software at all stages of software development. Therefore, it is very important to select reasonable test cases in the right way. Most of the test cases currently used in automated testing are written manually. Currently, the following two methods are mainly used to select test cases from written test cases:

Method 1 is to manually select some test cases based on experience. However, this method cannot guarantee coverage and cannot ensure that all scenarios are covered. In addition, a large amount of redundancy will be generated over time. For example, for products, product functions are constantly updated. For example, if model A is newly added to the computer room, test cases matching model A need to be configured based on model A. As time goes by, if model A needs to be replaced with new model B, test cases matching model B need to be configured based on model B. At this time, although model A is no longer needed, test cases matching model A are still retained, resulting in redundancy.

Method 2: automatically select a part of test cases through the coverage test index of the software to be tested, and verify a small number of test cases based on some strategies, where the coverage test index can be understood as the coverage of the development code; the above strategies can be based on the modified part, the risk level or the operation profile, etc.; although the coverage of the test cases selected by this method is more comprehensive, the execution coverage of this method is large, the execution efficiency is low, and it cannot cover abnormal scenarios.

Since the test cases are written manually, on the one hand, it is necessary to manually obtain parameters from the config (configuration file) and put the parameters into the automated script, which is cumbersome and less intelligent; on the other hand, it is difficult to match the actual application scenarios of the software, and the accuracy and reliability of the test are low.

Based on this, the embodiments of the present invention provide a method for generating test cases, a software testing method, a device and a server. The technology can be applied to applications that need to generate test cases, or applications that need to test software to be tested through test cases. To facilitate understanding of this embodiment, a method for generating test cases disclosed in an embodiment of the present invention is first introduced in detail. As shown in Figure 1, the method includes the following steps:

Step S102, if a test case of the target software needs to be generated, the parameter value of the test case is determined according to the user data of the target software; wherein the user data includes: operation data of the user of the target software operating the target software.

The above-mentioned target software can be understood as a software product that needs to be functionally tested; the above-mentioned test case can be understood as a description of a test task for a specific software product, which usually includes a test plan, method, technology or strategy, etc.; when performing automated testing on the target software, the test case can be a tool for assisting manual testing generated by using languages such as java (an object-oriented programming language) or python (a cross-platform computer programming language) with the help of frameworks such as testng (an open source automated testing framework); the above-mentioned parameter values can be understood as specific values related to the test case, such as the number of concurrent startups, the number of security groups added to mongodb (a database based on distributed file storage), etc.; the above-mentioned operation data may include the number of mongodb purchased by the user, the number of times the user has reconfigured the instance, etc.; in actual implementation, if it is necessary to generate a test case for the target software, the parameter value related to the test case can be determined based on the relevant operation data of the user who uses the target software.

Step S104: Generate a configuration file for the test case according to the parameter values.

The above configuration file can be understood as a file that can configure the relevant parameters of the test case; after the parameter value of the test case is determined according to the user data of the target software, a configuration file matching the test case can be generated according to the parameter value.

Step S106, generating a test case according to the above configuration file.

In actual implementation, the configuration file can be read through an automated script, and test cases can be generated based on relevant data in the read configuration file.

A method for generating a test case provided by an embodiment of the present invention, if a test case for a target software needs to be generated, the parameter values of the test case are determined according to the relevant operation data of the user of the target software; a configuration file of the test case is generated according to these parameter values, and then the test case is generated. The method automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, the generation efficiency of test cases is also improved.

An embodiment of the present invention also provides another method for generating a test case, which is implemented on the basis of the method of the above embodiment; the method focuses on describing the specific process of determining the parameter value of the test case according to the user data of the target software, which specifically corresponds to the following steps S202 to S204.

In the method, the test case includes at least one test case parameter; the test case parameter can be understood as a parameter item that needs to be designed for the test case, such as: the number of concurrent startups or the number of security groups added to mongodb; the test case parameter is usually provided with an identifier; the identifier is used to indicate: the parameter value of the test case parameter is determined according to user data, or the parameter value of the test case parameter can be a specified value; in actual implementation, the parameter values of some test case parameters need to be determined according to user data, and then the test case is automatically generated; while the parameter values of some test case parameters are determined in a more flexible manner and do not need to be determined according to user data, such as manually setting the corresponding specified value, etc.; a boolean type value can be used as an identifier to identify the test case parameter, and the boolean type value is used to control whether the parameter value of the test case parameter needs to be determined according to user data; the boolean type value can be 0 or 1, and usually the test engineer will pre-set the method for determining the parameter value of the corresponding use case parameter when the boolean type value is 0 and 1 respectively, for example, when the boolean type value is 1, it means that the parameter value of the use case parameter can be determined according to user data, and when the boolean type value is 0, it means that the parameter value of the use case parameter can be a manually set specified value, etc.

User data is pre-stored in a preset relational database; at least a portion of the user data is synchronized in a preset cache database; the relational database may be MySQL (SQL is the full name of Structured Query Language), and the cache database may be redis (Remote Dictionary Server). Of course, other relational databases or other cache databases may be selected as required. In actual implementation, online user data may be obtained in advance through a tool, and the obtained user data may be stored in a specified relational database, such as a MySQL database.

As shown in FIG2 , the method comprises the following steps:

Step S202: if it is necessary to determine the parameter value of the use case parameter according to the user data, obtain the user data related to the use case parameter.

The step S202 may specifically include: querying the identifier of the use case parameter, and if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to user data, acquiring user data related to the use case parameter.

In actual implementation, when it is necessary to generate a test case for the target software, considering that the test case usually includes at least one use case parameter, it is generally necessary to first query the identifier corresponding to the use case parameter to confirm the method for determining the parameter value of the use case parameter; for example, if a boolean type value is used as the identifier, and it is pre-set that when the boolean type value is 1, it means that the parameter value of the use case parameter can be determined based on user data; at this time, if the boolean type value queried is 1, the user data related to the use case parameter can be obtained.

Considering the differences in user data storage locations, the steps for obtaining user data related to use case parameters can be specifically implemented through the following steps 1 and 2:

Step 1: Get user data related to the use case parameters from the cache database.

In actual implementation, after the user data is stored in the preset relational database, the relational database usually synchronizes part of the data to the cache database. For example, the MySQL database usually synchronizes part of the data to the redis database. For some routine operations, if the redis database contains the user data required for the routine operations, the user data related to the use case parameters corresponding to the routine operations can be directly obtained from the redis database through automated scripts.

Step 2: If the user data related to the use case parameters cannot be obtained from the cache database, the user data related to the use case parameters is obtained from the relational database through the cache database.

Since only a part of the user data is synchronized in the cache database, the automated code may not be able to obtain the required user data related to some use case parameters from the cache database, while the relational database contains complete user data. In this case, the automated code can be used to first obtain the user data related to the use case parameters from the relational database, update it to the cache database, and then obtain the user data related to the use case parameters from the updated cache database; for example, if the required user data cannot be obtained from the redis database, the user data can be obtained from the MySQL database first, then updated to the redis database, and then the required user data can be obtained from the updated redis database.

Step S204, determining the parameter value of the use case parameter according to the user data related to the use case parameter. Specifically, step S204 can be implemented by the following steps 3 to 4:

Step three: Obtain candidate parameter values for the use case parameters from user data.

The above-mentioned alternative parameter values can be understood as parameter values related to the use case parameters. User data usually contains one or more alternative parameter values for the use case parameters. The alternative parameter values of the use case parameters can be obtained from a cache database, such as a redis database, by writing automated code. For example, taking the use case parameter as the number of concurrent startups as an example, the number of concurrent startups of users within a certain period of time is obtained, the obtained number value is inserted into the relational database, and synchronized to the cache database. At this time, multiple number values of the number of concurrent startups corresponding to multiple different time points within the time period can usually be obtained from the cache database. The multiple number values are the above-mentioned alternative parameter values. In actual implementation, the multiple number values can be the same data value or different data values.

Step 4: If the above candidate parameter values include multiple ones, determine the parameter value of the use case parameter from the multiple candidate parameter values according to the size of the candidate parameter values.

The alternative parameter values of the use case parameters obtained above can be screened through automated code. If the alternative parameter values include multiple data values of different sizes, the multiple alternative parameter values can be compared to obtain comparison results, and the alternative parameter values that meet the requirements are selected from the comparison results as the parameter values of the use case parameters according to the requirements; for example, still taking the use case parameter as the number of concurrent startups as an example, if the multiple numbers of concurrent startups obtained include multiple different data values, the largest data value corresponding to the number of concurrent startups can be selected as the parameter value of the use case parameter; for another example, there are 10 users, each of whom uses the same target software. If 9 of the users only operate their own instances once, and the 10th user operates his own instance 100 times, then 100 instances are obtained. It can also be understood that the same type of data can be screened according to the size of the data value, and the data value that meets the requirements is selected, and the maximum value is generally selected.

Step S206: Generate a configuration file for the test case according to the parameter values.

Step S208: Generate test cases according to the configuration file.

In the above method for generating test cases, the test case includes at least one test case parameter; if the parameter value of the test case parameter needs to be determined according to user data, firstly, the user data related to the test case parameter is obtained; then, the parameter value of the test case parameter is determined according to the obtained user data. Finally, a configuration file of the test case is generated according to these parameter values, and then the test case is generated. The method automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, it also improves the efficiency of test case generation.

The embodiment of the present invention also provides another method for generating a test case, which is implemented on the basis of the method of the above embodiment; the method focuses on describing the specific process of generating a configuration file of a test case according to parameter values, which specifically corresponds to the following steps S304 to S306. As shown in FIG3 , the method includes the following steps:

Step S302, if a test case of the target software needs to be generated, the parameter value of the test case is determined according to the user data of the target software; wherein the user data includes: operation data of the user of the target software operating the target software.

Step S304, fill the parameter value into the use case parameter corresponding to the parameter value.

In actual implementation, the parameter values of the above test cases can be obtained from the cache database through an automated script. Considering that a test case usually includes at least one use case parameter, the obtained parameter value can be filled in the corresponding use case parameter. For example, taking the use case parameter as the number of concurrent startups as an example, if the maximum number value corresponding to the number of concurrent startups is used as the parameter value of the use case parameter, the maximum number value can be read from the cache database through an automated script and filled in the use case parameter corresponding to the number of concurrent startups.

Step S306: Generate a configuration file for the test case based on the use case parameters and parameter values corresponding to the use case parameters.

The above configuration file may be a conf file. In actual implementation, the configuration file of the test case may be automatically generated through automation code according to the test case parameters with filled parameter values.

Step S308: Generate test cases according to the configuration file.

In actual implementation, the configuration file can be read through an automated script, such as reading a conf file, and the read data can be used to automatically generate test cases to test the target software. For example, it can be used for daily inspections or regression testing tasks. Regression testing can be understood as a controlled experiment that can detect regression bugs, or it can be understood as retesting after modifying the old code to confirm that the modification has not introduced new errors or caused errors in other codes; the test case can be in the form of automated code, which usually includes checkpoints, etc.

The following test case design is based on the number of mongodb security groups added by the user selected as the use case parameter. First, the number of security groups added by users to mongodb within a certain period of time is obtained. Usually, multiple quantity values can be obtained. The multiple quantity values obtained are compared, and the largest quantity value is selected to obtain the maximum number of security groups. The maximum quantity value can be read from the cache database through an automated script and filled into the use case parameter corresponding to mongodb adding security groups. The test case configuration file, such as the conf file, is automatically generated through the automated code. The automated script reads the conf file and automatically generates a complete automated test case.

In the above method for generating test cases, if it is necessary to generate test cases for the target software, the parameter values of the test cases are determined according to the relevant operation data of the users of the target software; the parameter values are filled into the use case parameters corresponding to the parameter values, and the configuration files of the test cases are generated according to the use case parameters and the parameter values corresponding to the use case parameters, thereby generating the test cases. This method automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, it also improves the efficiency of test case generation.

The embodiment of the present invention also provides another method for generating test cases, which is implemented on the basis of the method of the above embodiment; the method focuses on describing the specific process of updating the test cases according to the updated user data of the target software, which specifically corresponds to the following steps S408 to S410, as shown in FIG4, and the method includes the following steps:

Step S402, if a test case of the target software needs to be generated, the parameter value of the test case is determined according to the user data of the target software; wherein the user data includes: operation data of the user of the target software operating the target software.

Step S404: Generate a configuration file for the test case according to the parameter values.

Step S406: Generate test cases according to the configuration file.

Step S408: acquiring updated user data of the target software at a preset time interval.

The above-mentioned preset time interval can be set according to actual needs. For example, the time interval can be daily, hourly, etc., or it can be real-time acquisition of updated user data of the target software. The updated user data can be understood as new operation data generated when the user of the target software operates the target software. In actual implementation, considering that the operation data of the user of the target software when operating the target software is constantly updated, it is necessary to obtain the updated user data of the target software according to the preset time interval. For example, online user data can be obtained daily to obtain the latest user behavior to ensure the reliability of the generated test case scenario.

Step S410: Update the test case according to the above updated user data.

After the updated user data of the target software is obtained, the updated parameter values of the test case can be determined according to the updated user data, and then an updated configuration file of the test case is generated according to the updated parameter values, and then the test case is updated according to the updated configuration file.

The above method for generating test cases, if it is necessary to generate test cases for the target software, determines the parameter values of the test cases according to the relevant operation data of the users of the target software; generates a configuration file for the test cases according to these parameter values, and then generates the test cases; updates the test cases according to the updated user data of the target software obtained. This method saves and processes online user data, obtains the latest user dynamics in real time, and automatically generates test cases after obtaining user data. It does not require manual writing of test cases and automation scripts, which not only ensures the high reliability of the test case scenarios, but also saves the time of generating test cases, improves the testing efficiency, and ensures that the user data used in the automated testing is the user operation with high accuracy; for continuous integration testing, regression testing after adding new functions, and subsequent real-time playback of online scenarios, etc., it can be directly executed automatically without manual selection of test cases, which greatly improves the intelligence of test cases.

The embodiment of the invention provides a software testing method, which is implemented on the basis of the method in the above embodiment; as shown in FIG5 , the method includes the following steps:

Step S502, if the target software needs to be tested, obtain the test case of the target software; wherein the test case of the target software is generated in the following manner: determine the parameter value of the test case according to the user data of the target software; wherein the user data includes: the operation data of the user of the target software operating the target software; generate a configuration file of the test case according to the parameter value; generate the test case according to the configuration file.

Step S504: test the target software using the test case to obtain the test result.

The above test results can be understood as the actual test results of the target software obtained after testing the target software according to the test method in the test case. Based on the actual test results, it can be confirmed whether the software function corresponding to the test case in the target software meets the software requirements, etc.

A software testing method provided by an embodiment of the present invention can test the target software by acquiring the test case of the target software to obtain the test result; wherein the test case of the target software can be generated in the following manner: determining the parameter value of the test case according to the relevant operation data of the user of the target software; generating a configuration file of the test case according to these parameter values, and then generating the test case. The method automatically generates the test case according to the real user operation data of the target software. Compared with the method of manually writing the test case, the real user operation data makes the generated test case match the actual application scenario of the target software, thereby improving the accuracy and reliability of the software test; at the same time, it also improves the efficiency of generating the test case.

The embodiment of the present invention further provides another software testing method, which is implemented on the basis of the method in the above embodiment; as shown in FIG6 , the method comprises the following steps:

Step S602, if the target software needs to be tested, obtain the test case of the target software; wherein the test case of the target software is generated in the following manner: determine the parameter value of the test case according to the user data of the target software; wherein the user data includes: the operation data of the user of the target software operating the target software; generate a configuration file of the test case according to the parameter value; generate the test case according to the configuration file.

Step S604: test the target software using the test case to obtain the test result.

Step S606: Send the test result to a designated test result receiving address.

The test result receiving address may include a work group or an email address, etc. The test result receiving address may be specified according to actual needs so that the personnel corresponding to the test result receiving address can obtain the test result, and then the test result can be analyzed to improve the software function corresponding to the test case in the target software; in actual implementation, the automation code can be combined with the jenkins server, and the automated test case generated according to the big data is executed on the jenkins server. The jenkins server calls the automation script of the test case, verifies the target software through the automation script of the test case, and sends the test result in the form of a report to the work group and email address configured by the jenkins server, etc.; the jenkins server has some built-in functions, such as the timed build function, through which the timed rules can be set. After the setting is completed, the build task will be executed regularly according to the set time, which can save manpower; in addition, there are email sending functions, visual report functions, etc. In general, obtaining user data, generating test cases, and executing test cases are usually run on one device, for example, in the jenkins server.

The above software testing method, if it is necessary to test the target software, can test the target software by obtaining the test case of the target software to obtain the test result; and send the test result to the specified test result receiving address. This method automatically generates test cases based on the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, it also improves the efficiency of test case generation.

An embodiment of the present invention provides a structural schematic diagram of a device for generating test cases, as shown in Figure 7, the device includes: a first determination module 70, which is used to determine the parameter value of the test case according to the user data of the target software if a test case for the target software needs to be generated; wherein the user data includes: the operation data of the user of the target software operating the target software; a first generation module 71, which is used to generate a configuration file of the test case according to the parameter value; and a second generation module 72, which is used to generate a test case according to the configuration file.

The embodiment of the present invention provides a device for generating test cases. If it is necessary to generate test cases for target software, the parameter values of the test cases are determined according to the relevant operation data of the user of the target software; a configuration file of the test cases is generated according to these parameter values, and then the test cases are generated. The device automatically generates test cases according to the real user operation data of the target software. Compared with the method of manually writing test cases, the real user operation data makes the generated test cases match the actual application scenarios of the target software, thereby improving the accuracy and reliability of software testing; at the same time, the efficiency of test case generation is also improved.

Furthermore, the test case includes at least one use case parameter; the first determination module 70 is also used to: if it is necessary to determine the parameter value of the use case parameter based on user data, obtain user data related to the use case parameter; and determine the parameter value of the use case parameter based on the user data related to the use case parameter.

Furthermore, the use case parameter is provided with an identifier; the identifier is used to indicate that: the parameter value of the use case parameter is determined according to user data, or the parameter value of the use case parameter is a specified value; the first determination module 70 is also used to: query the identifier of the use case parameter, if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to user data, obtain user data related to the use case parameter.

Furthermore, user data is pre-stored in a preset relational database; at least a portion of the user data is synchronized in a preset cache database; the first determination module 70 is also used to: obtain user data related to the use case parameters from the cache database; if the user data related to the use case parameters cannot be obtained from the cache database, obtain the user data related to the use case parameters from the relational database through the cache database.

Furthermore, the first determination module 70 is also used to: obtain candidate parameter values of the use case parameter from the user data; if the candidate parameter values include multiple types, determine the parameter value of the use case parameter from the multiple candidate parameter values according to the size of the candidate parameter values.

Furthermore, the first generating module 71 is also used to: fill the parameter value into the use case parameter corresponding to the parameter value; and generate a configuration file of the test case according to the use case parameter and the parameter value corresponding to the use case parameter.

Furthermore, the device is also used to: obtain updated user data of the target software at preset time intervals; and update test cases according to the updated user data.

The device for generating test cases provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned method embodiment for generating test cases. For the sake of brief description, for matters not mentioned in the embodiment of the device for generating test cases, reference may be made to the corresponding contents in the aforementioned method embodiment for generating test cases.

An embodiment of the present invention provides a structural schematic diagram of a software testing device, as shown in Figure 8, the device includes: an acquisition module 80, which is used to acquire the test case of the target software if the target software needs to be tested; a second determination module 81, which is used to test the target software through the test case to obtain the test result; wherein the test case of the target software is generated in the following manner: determining the parameter value of the test case according to the user data of the target software; wherein the user data includes: operation data of the user of the target software operating the target software; generating a configuration file of the test case according to the parameter value; generating the test case according to the configuration file.

A software testing device provided by an embodiment of the present invention can test the target software by acquiring the test case of the target software to obtain the test result if the target software needs to be tested; wherein the test case of the target software can be generated in the following manner: determining the parameter value of the test case according to the relevant operation data of the user of the target software; generating a configuration file of the test case according to these parameter values, and then generating the test case. The device automatically generates the test case according to the real user operation data of the target software. Compared with the method of manually writing the test case, the real user operation data makes the generated test case match the actual application scenario of the target software, thereby improving the accuracy and reliability of the software test; at the same time, it also improves the efficiency of generating the test case.

Furthermore, the device is also used to: send the test result to a designated test result receiving address.

The software testing device provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned software testing method embodiment. For the sake of brief description, for matters not mentioned in the software testing device embodiment, reference may be made to the corresponding contents in the aforementioned software testing method embodiment.

An embodiment of the present invention also provides a server, as shown in Figure 9, the server includes a processor 130 and a memory 131, the memory 131 stores machine executable instructions that can be executed by the processor 130, and the processor 130 executes the machine executable instructions to implement the above-mentioned method of generating test cases or the above-mentioned software testing method.

Furthermore, the server shown in FIG. 9 further includes a bus 132 and a communication interface 133 , and the processor 130 , the communication interface 133 and the memory 131 are connected via the bus 132 .

The memory 131 may include a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 133 (which may be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. may be used. The bus 132 may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bidirectional arrow is used in FIG9, but it does not mean that there is only one bus or one type of bus.

The processor 130 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 130. The above processor 130 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present invention can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module may be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 131, and the processor 130 reads the information in the memory 131 and completes the steps of the method of the above embodiment in combination with its hardware.

An embodiment of the present invention also provides a machine-readable storage medium, which stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the above-mentioned method for generating test cases, or software testing method. The specific implementation can be found in the method embodiment, which will not be repeated here.

The computer program products of the method for generating test cases, software testing method, device and server provided in the embodiments of the present invention include a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the methods described in the previous method embodiments. The specific implementation can be found in the method embodiments, which will not be repeated here.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Finally, it should be noted that the above embodiments are only specific implementations of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The protection scope of the present invention is not limited thereto. Although the present invention is described in detail with reference to the above embodiments, those skilled in the art should understand that any person skilled in the art can still modify the technical solutions recorded in the above embodiments within the technical scope disclosed by the present invention, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims (10)

1. A method for generating a test case, characterized in that the method comprises: If a test case of the target software needs to be generated, the parameter value of the test case is determined according to the user data of the target software; wherein the user data includes: the operation data of the user of the target software operating the target software; the operation data includes the number of mongodb purchased by the user and the number of times the user has configured the corresponding instance of the target software; Generate a configuration file for the test case according to the parameter value; Generate the test case according to the configuration file; The step of generating a configuration file for the test case according to the parameter value comprises: Fill the parameter value into the test case parameter corresponding to the parameter value; the parameter value is specific data related to the test case; Generate a configuration file for the test case according to the test case parameters and parameter values corresponding to the test case parameters; The test case includes at least one test case parameter; The step of determining the parameter value of the test case according to the user data of the target software comprises: If it is necessary to determine the parameter value of the use case parameter according to the user data, obtaining the user data related to the use case parameter; Determining a parameter value of the use case parameter based on user data related to the use case parameter; The use case parameter is provided with an identifier; the identifier is used to indicate that: the parameter value of the use case parameter is determined according to the user data, or the parameter value of the use case parameter is a specified value; If it is necessary to determine the parameter value of the use case parameter according to the user data, the step of obtaining the user data related to the use case parameter includes: The identifier of the use case parameter is queried, and if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to the user data, the user data related to the use case parameter is acquired. 2. The method according to claim 1, characterized in that the user data is pre-stored in a preset relational database; at least a portion of the user data is synchronized in a preset cache database; The step of obtaining user data related to the use case parameters includes: Acquire user data related to the use case parameters from the cache database; If the user data related to the use case parameters cannot be obtained from the cache database, the user data related to the use case parameters are obtained from the relational database through the cache database. 3. The method according to claim 1, wherein the step of determining the parameter value of the use case parameter according to the user data related to the use case parameter comprises: Acquire candidate parameter values of the use case parameters from the user data; If the candidate parameter values include multiple types, the parameter value of the use case parameter is determined from the multiple candidate parameter values according to the size of the candidate parameter values. 4. The method according to claim 1, characterized in that after the step of generating the test case according to the configuration file, the method further comprises: Obtaining updated user data of the target software at preset time intervals; The test case is updated according to the updated user data. 5. A software testing method, characterized in that the method comprises: If the target software needs to be tested, obtain the test case of the target software; Testing the target software through the test case to obtain a test result; Wherein, the test case of the target software is generated in the following manner: determining the parameter value of the test case according to the user data of the target software; wherein, the user data includes: the operation data of the user of the target software operating the target software; the operation data includes the number of mongodb purchased by the user and the number of times the user has reconfigured the corresponding instance of the target software; generating the configuration file of the test case according to the parameter value; generating the test case according to the configuration file; the step of generating the configuration file of the test case according to the parameter value includes: filling the parameter value into the use case parameter corresponding to the parameter value; the parameter value is specific data related to the test case; generating the configuration file of the test case according to the use case parameter and the parameter value corresponding to the use case parameter; the test case includes at least one a use case parameter; the step of determining the parameter value of the test case according to the user data of the target software comprises: if the parameter value of the use case parameter needs to be determined according to the user data, obtaining the user data related to the use case parameter; determining the parameter value of the use case parameter according to the user data related to the use case parameter; the use case parameter is provided with an identifier; the identifier is used to indicate: the parameter value of the use case parameter is determined according to the user data, or the parameter value of the use case parameter is a specified value; the step of obtaining the user data related to the use case parameter if the parameter value of the use case parameter needs to be determined according to the user data comprises: querying the identifier of the use case parameter, and if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to the user data, obtaining the user data related to the use case parameter. 6. The method according to claim 5 is characterized in that after the step of testing the target software through the test case, the method further comprises: sending the test result to a designated test result receiving address. 7. A device for generating a test case, characterized in that the device comprises: The first determination module is used to determine the parameter value of the test case according to the user data of the target software if a test case of the target software needs to be generated; wherein the user data includes: the operation data of the user of the target software operating the target software; the operation data includes the number of MongoDB purchased by the user and the number of times the user has configured the corresponding instance of the target software; A first generating module, used to generate a configuration file of the test case according to the parameter value; A second generating module, used to generate the test case according to the configuration file; The first generating module is also used for: Fill the parameter value into the test case parameter corresponding to the parameter value; the parameter value is specific data related to the test case; Generate a configuration file for the test case according to the test case parameters and parameter values corresponding to the test case parameters; The test case includes at least one test case parameter; The first determination module is further used for: if it is necessary to determine the parameter value of the use case parameter according to the user data, obtaining the user data related to the use case parameter; determining the parameter value of the use case parameter according to the user data related to the use case parameter; The use case parameter is set with an identifier; the identifier is used to indicate: the parameter value of the use case parameter is determined according to the user data, or the parameter value of the use case parameter is a specified value; the first determination module is also used to: query the identifier of the use case parameter, if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to the user data, obtain the user data related to the use case parameter. 8. A software testing device, characterized in that the device comprises: An acquisition module is used to acquire test cases of the target software if the target software needs to be tested; A second determination module is used to test the target software through the test case to obtain a test result; Wherein, the test case of the target software is generated in the following manner: determining the parameter value of the test case according to the user data of the target software; wherein, the user data includes: the operation data of the user of the target software operating the target software; the operation data includes the number of mongodb purchased by the user and the number of times the user has reconfigured the corresponding instance of the target software; generating the configuration file of the test case according to the parameter value; generating the test case according to the configuration file; the step of generating the configuration file of the test case according to the parameter value includes: filling the parameter value into the use case parameter corresponding to the parameter value; the parameter value is specific data related to the test case; generating the configuration file of the test case according to the use case parameter and the parameter value corresponding to the use case parameter; the test case includes at least one a use case parameter; the step of determining the parameter value of the test case according to the user data of the target software comprises: if the parameter value of the use case parameter needs to be determined according to the user data, obtaining the user data related to the use case parameter; determining the parameter value of the use case parameter according to the user data related to the use case parameter; the use case parameter is provided with an identifier; the identifier is used to indicate: the parameter value of the use case parameter is determined according to the user data, or the parameter value of the use case parameter is a specified value; the step of obtaining the user data related to the use case parameter if the parameter value of the use case parameter needs to be determined according to the user data comprises: querying the identifier of the use case parameter, and if the identifier of the use case parameter indicates that the parameter value of the use case parameter is determined according to the user data, obtaining the user data related to the use case parameter. 9. A server, characterized in that it includes a processor and a memory, the memory storing machine executable instructions that can be executed by the processor, and the processor executing the machine executable instructions to implement the method for generating test cases described in any one of claims 1-4, or the software testing method described in any one of claims 5-6. 10. A machine-readable storage medium, characterized in that the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the method for generating test cases described in any one of claims 1-4, or the software testing method described in any one of claims 5-6.