CN109271309B

CN109271309B - Method and device for automatically testing software, server, equipment and storage medium

Info

Publication number: CN109271309B
Application number: CN201710584465.XA
Authority: CN
Inventors: 高斯婷
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2017-07-18
Filing date: 2017-07-18
Publication date: 2022-04-08
Anticipated expiration: 2037-07-18
Also published as: CN109271309A

Abstract

The embodiment of the disclosure provides a method and a device for automatically testing software, computer equipment and a computer readable storage medium, which are applied to the technical field of software testing, wherein the method comprises the following steps: acquiring the project name of each software project contained in the software project to be tested to form a project name set; traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name; judging whether an association relation exists between the software projects to obtain a judgment result; and executing an automatic test according to the judgment result and the engineering configuration information. The embodiment of the disclosure can effectively realize automation of test environment deployment and automation of test case operation, save labor cost, improve test efficiency and accuracy, and shorten software test period.

Description

Method and device for automatically testing software, server, equipment and storage medium

Technical Field

The disclosed embodiments relate to the technical field of software testing, and in particular, to a method for automatically testing software, an apparatus for automatically testing software, a server, a computer device, and a computer-readable storage medium.

Background

At present, the following problems mainly exist in the existing software project testing process: (1) manual deployment of the test environment is time-consuming and incorrect due to human factors; (2) running a test case (case) manually is time consuming and results in test omissions due to human factors. The reasons for the above problems are mainly that it takes a long time to deploy the test environment and manually run the test case, each project in the software project has its own environment deployment script and automatic test case, and the software projects to be tested in the department are numerous, one project may correspond to multiple projects, and the deployment and automatic testing of multiple projects need human intervention, obviously resulting in time and labor consumption; meanwhile, whether the test environment deployment is successful and whether the result of the automatic test is accurate still need to be judged manually.

Therefore, how to implement automation of test environment deployment and automation of test case operation, save labor cost, shorten software test period, and become a technical problem to be solved urgently.

Disclosure of Invention

The embodiment of the disclosure provides a new technical scheme based on the above problems, and can effectively implement automation of test environment deployment and automation of test case operation, save labor cost, improve test efficiency and accuracy, and shorten software test period.

In view of this, according to a first aspect of the embodiments of the present disclosure, a method for automatically testing software is provided, including: acquiring the project name of each software project contained in the software project to be tested to form a project name set; traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name; judging whether an association relation exists between the software projects to obtain a judgment result; and executing an automatic test according to the judgment result and the engineering configuration information.

In the technical scheme, the project names of all software projects included in all projects to be tested form a set, so that all the software projects can be scheduled through a unified interface, unified management of automatic test software is facilitated, manual intervention is reduced, specifically, the project name set is traversed, the project configuration information of the software projects corresponding to each traversed project name is obtained, automatic testing of the software is further performed by combining the obtained corresponding project configuration information according to whether an incidence relation exists between the software projects corresponding to the project name set, labor cost is saved, testing efficiency and accuracy are improved, and a software testing period is shortened.

Further, the engineering configuration information of each software project includes association relationship configuration information, and specifically, whether an association relationship exists between the software projects may be determined according to the association relationship configuration information, where the association relationship configuration information is used to indicate whether different software projects belong to one software project and/or to indicate whether different software projects are in a serial operation relationship or a parallel operation relationship.

In the above technical solution, preferably, the engineering configuration information further includes environment deployment information and use case test information, and the step of executing an automated test according to the judgment result and the engineering configuration information includes: when the judgment result shows that the incidence relation exists among the software projects, automatically deploying a first test environment according to first environment deployment information corresponding to the traversed first software project name, and starting to operate the corresponding first software project, wherein the first software project name is any name in the project name set; obtaining a first deployment result of the first test environment; when the first deployment result is successful deployment, operating a first test case according to first case test information corresponding to the first software engineering name, generating a first case operation result, and determining whether to finish the automatic test according to the first case operation result; and when the first deployment result is a deployment failure, outputting all the case operation results generated by the software project to be tested, and finishing the automatic test.

In the technical scheme, the engineering configuration information for performing the automated testing on each software engineering at least comprises environment deployment information and case test information, wherein the environment deployment information is used for realizing the automated deployment of the testing environment and comprises a code script directory, a corresponding latest code script and the like, and the case test information is used for realizing the automated testing of the case and comprises a test case operation directory, a corresponding latest test case and the like.

Further, when judging that the association relationship exists between the software projects, automatically deploying the test environment for each project name in the traversed project set according to the environment deployment information, then, the service of the software engineering is started, the deployment result of the test environment is automatically monitored, the human intervention is avoided, the test efficiency and the test accuracy are improved, the subsequent automatic software test flow can be further determined according to the deployment result of the test environment, and specifically, if the test environment is successfully deployed through monitoring, the test case can be automatically operated to test whether the service of the software project is normal, meanwhile, the traversal of the project name set can be determined to be finished, namely, the automatic test of other residual software projects can be finished through monitoring the operation result of the test case, meanwhile, the manual intervention is avoided, and the test efficiency and the test accuracy are improved; and if the test environment deployment is monitored to fail, outputting the case operation result of the test case corresponding to one or more project names in the traversed project name set, and ending the automated test on the correlated software projects to save resources.

In any one of the above technical solutions, preferably, the step of determining whether to end the automated test according to the first example operation result includes: when the first case operation result is normal operation, continuously traversing other project names in the project name set until all project names in the project name set are successfully traversed, and correspondingly outputting all case operation results; and when the first case operation result is abnormal operation, outputting all case operation results generated by the software project to be tested, and finishing the automatic test.

In the technical scheme, when the software projects corresponding to the project name set are mutually associated, if the use case operation result of the test case of any software project is normal operation, other project names in the project name set can be continuously traversed until all the project names in the project name set are successfully traversed, namely, the test environment is successfully deployed automatically, the use case operation results of the test cases for starting to operate the corresponding software projects are normally operated, all the generated use case operation results can be uniformly output, and automation and association management are facilitated; if the case operation result of the test case of any software project is abnormal operation, the case operation result of the test case corresponding to one or more project names in the traversed project name set can be output, and the automatic test of each software project related to each other is ended, so that resources are saved.

In any of the above technical solutions, preferably, the step of performing an automated test according to the judgment result and the engineering configuration information further includes: when the judgment result shows that no incidence relation exists among the software projects, automatically deploying a second test environment according to second environment deployment information corresponding to the traversed second software project name, and starting to run the corresponding second software project, wherein the second software project name is any name in the project name set; acquiring a second deployment result of the second test environment; when the second deployment result is successful deployment, operating a second test case according to second case test information corresponding to the second software engineering name, generating and outputting a second case operation result, and continuously traversing other engineering names in the engineering name set until all the engineering names in the engineering name set are traversed; and when the second deployment result is a deployment failure, outputting the second deployment result, and continuously traversing other project names in the project name set until all project names in the project name set are traversed.

In the technical scheme, when judging that no association relation exists between software projects, automatically deploying a test environment for each project name in a traversed project set according to environment deployment information, then, the service of the software engineering is started, the deployment result of the test environment is automatically monitored, the human intervention is avoided, the test efficiency and the test accuracy are improved, the subsequent automatic software test flow can be further determined according to the deployment result of the test environment, and specifically, if the test environment is successfully deployed through monitoring, automatically running the test cases to test whether the service of the software project is normal, outputting the generated case running results of the test cases one by one, and then continuously traversing other project names in the project name set until all the project names in the project name set are traversed; if the test environment deployment is failed, the corresponding test environment deployment result can be output firstly, and other project names in the project name set are traversed continuously until all the project names in the project name set are traversed, so that the automatic deployment of the test environment, the automatic operation of the test case and the monitoring of the corresponding result are realized.

In any of the above technical solutions, preferably, the method for automatically testing software further includes: and generating a log file in the automatic test software process to record the passing of the automatic test software process for subsequent positioning and checking, such as positioning to the name or the number of lines of a function method, and checking the reasons of the test environment deployment failure and/or the abnormal case operation.

In any of the above technical solutions, preferably, the step of obtaining the project name of each software project included in the to-be-tested software project to form the project name set includes: and acquiring the project name of each software project through an HTTP service interface to form the project name set.

In the technical scheme, the engineering names of the software projects can be called as a uniform interface through an HTTP (Hyper Text Transfer Protocol) service interface to form a set; furthermore, all processes of the automatic test software can be scheduled through the HTTP service interface, so that excessive manual intervention is avoided, and the test efficiency and accuracy are improved.

According to a second aspect of the embodiments of the present disclosure, an apparatus for automatically testing software is provided, including: the acquisition module is used for acquiring the project names of the software projects to be tested so as to form a project name set; the traversal module is used for traversing the project name set and acquiring corresponding software project configuration information according to each traversed project name; the judging module is used for judging whether the association relationship exists between the software projects to obtain a judging result; and the test module is used for executing an automatic test according to the judgment result and the engineering configuration information.

In the above technical solution, preferably, the engineering configuration information further includes environment deployment information and use case test information, and the test module includes: the first deployment submodule is used for automatically deploying a first test environment according to first environment deployment information corresponding to the traversed first software project name and starting to run the corresponding first software project when the judgment result shows that the incidence relation exists among the software projects, wherein the first software project name is any name in the project name set; the first obtaining submodule is used for obtaining a first deployment result of the first testing environment; the operation sub-module is used for operating a first test case according to first case test information corresponding to the first software engineering name when the first deployment result is successful in deployment, generating a first case operation result and determining whether to finish the automatic test according to the first case operation result; and the output submodule is used for outputting all the case running results generated by the software project to be tested when the first deployment result is the deployment failure, and finishing the automatic test.

In any one of the above technical solutions, preferably, the test module further includes a scheduling submodule, and the scheduling submodule is configured to: when the first case operation result is normal operation, scheduling the traversal module to continuously traverse other project names in the project name set until all project names in the project name set are successfully traversed, and scheduling the output submodule to correspondingly output all case operation results; and when the first case operation result is abnormal operation, scheduling the output submodule to output all case operation results generated by the software project to be tested, and finishing the automatic test.

In any one of the above technical solutions, preferably, the test module further includes: the second deployment submodule is used for automatically deploying a second test environment according to second environment deployment information corresponding to the traversed second software project name and starting to run the corresponding second software project when the judgment result shows that no association exists among the software projects, wherein the second software project name is any name in the project name set; the second obtaining submodule is used for obtaining a second deployment result of the second testing environment; the first processing submodule is used for running a second test case according to second case test information corresponding to the second software engineering name when the second deployment result is that the deployment is successful, generating and outputting a second case running result, and continuously traversing other engineering names in the engineering name set until all the engineering names in the engineering name set are traversed; and the second processing submodule is used for outputting the second deployment result when the second deployment result is the deployment failure, and continuously traversing other project names in the project name set until all the project names in the project name set are traversed.

In any one of the above technical solutions, preferably, the device for automatically testing software further includes: and the log generation module is used for generating a log file in the automatic test software process so as to record the passing of the automatic test software process for subsequent positioning and checking, such as positioning to the name or the number of lines of a function method, and checking the reasons of the test environment deployment failure and/or the abnormal case operation.

In any one of the above technical solutions, preferably, the obtaining module is specifically configured to: and acquiring the project name of each software project through an HTTP service interface to form the project name set.

In the technical scheme, the engineering names of the software projects can be called as a uniform interface through an HTTP service interface to form a set; furthermore, all processes of the automatic test software can be scheduled through the HTTP service interface, so that excessive manual intervention is avoided, and the test efficiency and accuracy are improved.

According to a third aspect of the embodiments of the present disclosure, a server is provided, which includes the apparatus for automated testing software according to any one of the above-mentioned technical solutions of the second aspect, so that the server has all beneficial technical effects of the apparatus for automated testing software, and details are not repeated herein.

According to a fourth aspect of the embodiments of the present disclosure, a computer device is proposed, which includes a memory, a processor and a computer program stored on the memory and executable on the processor, and the processor implements the following steps when executing the computer program: acquiring the project name of each software project contained in the software project to be tested to form a project name set; traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name; judging whether an association relation exists between the software projects to obtain a judgment result; and executing an automatic test according to the judgment result and the engineering configuration information.

According to a fifth aspect of embodiments of the present disclosure, a computer-readable storage medium is presented, on which a computer program is stored, which when executed by a processor, performs the steps of: acquiring the project name of each software project contained in the software project to be tested to form a project name set; traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name; judging whether an association relation exists between the software projects to obtain a judgment result; and executing an automatic test according to the judgment result and the engineering configuration information.

According to the technical scheme of the embodiment of the disclosure, the automation of test environment deployment and the automation of test case operation can be effectively realized, the labor cost is saved, the test efficiency and accuracy are improved, and the software test period is shortened.

Drawings

FIG. 1 shows a flow diagram of a method of automated testing of software according to a first embodiment of the disclosure;

FIG. 2 is a schematic flow chart illustrating a first method of performing an automated test based on a determination and engineering configuration information according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart illustrating a first method of performing an automated test based on a determination and engineering configuration information according to an embodiment of the present disclosure;

FIG. 4 shows a schematic block diagram of an apparatus for automated testing software of an embodiment of the present disclosure;

FIG. 5 shows a schematic block diagram of the test module shown in FIG. 4;

figure 6 illustrates a scheduling architecture and system diagram for test environment integration and admission according to an embodiment of the present disclosure;

FIG. 7 shows a method flow diagram of automated test software according to a second embodiment of the present disclosure;

FIG. 8 shows a schematic block diagram of a computer device of an embodiment of the present disclosure.

Detailed Description

In order that the above objects, features and advantages of the embodiments of the present disclosure may be more clearly understood, embodiments of the present disclosure are described in further detail below with reference to the accompanying drawings and detailed description. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure, however, the embodiments of the disclosure may be practiced in other ways than those described herein, and therefore the scope of the embodiments of the disclosure is not limited by the specific embodiments disclosed below.

The method for automatically testing software according to the embodiment of the present disclosure is described in detail below with reference to fig. 1 to 3.

As shown in fig. 1, the method for automatically testing software according to the first embodiment of the present disclosure specifically includes the following steps:

step 102, acquiring the project name of each software project included in the to-be-tested software project to form a project name set.

Specifically, in this step, the project name of each software project is acquired through an HTTP service interface to form the project name set.

In the embodiment, the engineering names of the software projects can be called as a uniform interface through the HTTP service interface to form a set; furthermore, all processes of the automatic test software can be scheduled through the HTTP service interface, so that excessive manual intervention is avoided, and the test efficiency and accuracy are improved.

And 104, traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name.

And 106, judging whether the software projects have an association relation or not to obtain a judgment result.

And 108, executing an automatic test according to the judgment result and the engineering configuration information.

In the embodiment, the project names of all the software projects included in all the projects to be tested form a set, so that all the software projects can be scheduled through a unified interface, unified management of automatic test software is facilitated, manual intervention is reduced, specifically, the project name set is traversed, the project configuration information of the software project corresponding to each traversed project name is obtained, and the automatic test of the software is further executed by combining the obtained corresponding project configuration information according to whether the incidence relation exists between the software projects corresponding to the project name set, so that the labor cost is saved, the test efficiency and accuracy are improved, and the software test period is shortened.

Further, in the above embodiment, the engineering configuration information further includes environment deployment information and use case test information, that is, the engineering configuration information for performing the automated test on each software engineering at least includes the environment deployment information and the use case test information, where the environment deployment information is used to implement the automated deployment of the test environment, and includes a code script directory and a corresponding latest code script, and the use case test information is used to implement the automated test of the use case, and includes a test use case operation directory and a corresponding latest test use case.

Further, step 108 in the above embodiment can be specifically executed as the following two embodiments.

In the first embodiment, the determination result indicates that an association relationship exists between the software projects. Specifically, as shown in fig. 2, the step 108 may be specifically executed as:

step S20, automatically deploying a first test environment according to the first environment deployment information corresponding to the traversed first software project name, and starting to run the corresponding first software project, wherein the first software project name is any name in the project name set.

Step S22, obtain a first deployment result of the first test environment.

Step S24, when the first deployment result is that deployment is successful, running a first test case according to the first case test information corresponding to the first software project name, and generating a first case running result, so as to determine whether to end the automated test according to the first case running result.

And step S26, when the first deployment result is a deployment failure, outputting all the case operation results generated by the software project to be tested, and ending the automated test.

In the embodiment, when the incidence relation exists between the software projects, the test environment is automatically deployed according to the environment deployment information of each project name in the traversed project set, then, the service of the software engineering is started, the deployment result of the test environment is automatically monitored, the human intervention is avoided, the test efficiency and the test accuracy are improved, the subsequent automatic software test flow can be further determined according to the deployment result of the test environment, and specifically, if the test environment is successfully deployed through monitoring, the test case can be automatically operated to test whether the service of the software project is normal, meanwhile, the traversal of the project name set can be determined to be finished, namely, the automatic test of other residual software projects can be finished through monitoring the operation result of the test case, meanwhile, the manual intervention is avoided, and the test efficiency and the test accuracy are improved; and if the test environment deployment is monitored to fail, outputting the case operation result of the test case corresponding to one or more project names in the traversed project name set, and ending the automated test on the correlated software projects to save resources.

Further, the determining whether to end the automation test according to the first example operation result in the step S24 may specifically be performed as:

when the first case operation result is normal operation, continuously traversing other project names in the project name set until all project names in the project name set are successfully traversed, and correspondingly outputting all case operation results; and when the first case operation result is abnormal operation, outputting all case operation results generated by the software project to be tested, and finishing the automatic test.

In this embodiment, when the software projects corresponding to the project name set are associated with each other, if the case operation result of the test case of any software project is normal operation, the other project names in the project name set can be continuously traversed until all the project names in the project name set are successfully traversed, that is, the test environment is successfully deployed automatically, the case operation results of the test cases for starting to operate the corresponding software projects are all normally operated, all the generated case operation results can be uniformly output, and automation and association management are facilitated; if the case operation result of the test case of any software project is abnormal operation, the case operation result of the test case corresponding to one or more project names in the traversed project name set can be output, and the automatic test of each software project related to each other is ended, so that resources are saved.

In a second embodiment, the determination result indicates that no association exists between the software projects. Specifically, as shown in fig. 3, the step 108 may be specifically executed as:

and step S30, automatically deploying a second test environment according to the traversed second environment deployment information corresponding to the second software project name, and starting to run a corresponding second software project, wherein the second software project name is any name in the project name set.

And step S32, acquiring a second deployment result of the second test environment.

Step S34, when the second deployment result is that deployment is successful, running a second test case according to the second case test information corresponding to the second software project name, generating and outputting a second case running result, and continuing to traverse other project names in the project name set until all project names in the project name set are traversed.

Step S36, when the second deployment result is a deployment failure, outputting the second deployment result, and continuing to traverse other project names in the project name set until all project names in the project name set are traversed.

In the embodiment, when judging that no association relation exists between the software projects, automatically deploying the test environment for each project name in the traversed project set according to the environment deployment information, then, the service of the software engineering is started, the deployment result of the test environment is automatically monitored, the human intervention is avoided, the test efficiency and the test accuracy are improved, the subsequent automatic software test flow can be further determined according to the deployment result of the test environment, and specifically, if the test environment is successfully deployed through monitoring, automatically running the test cases to test whether the service of the software project is normal, outputting the generated case running results of the test cases one by one, and then continuously traversing other project names in the project name set until all the project names in the project name set are traversed; if the test environment deployment is failed, the corresponding test environment deployment result can be output firstly, and other project names in the project name set are traversed continuously until all the project names in the project name set are traversed, so that the automatic deployment of the test environment, the automatic operation of the test case and the monitoring of the corresponding result are realized.

Further, in any of the above embodiments, the method for automatically testing software further includes: and generating a log file in the automatic test software process to record the passing of the automatic test software process for subsequent positioning and checking, such as positioning to the name or the number of lines of a function method, and checking the reasons of the test environment deployment failure and/or the abnormal case operation.

The apparatus of the automated test software according to the embodiment of the present disclosure is described in detail below with reference to fig. 4 and 5.

As shown in fig. 4, an apparatus 40 for automated testing software according to an embodiment of the present disclosure includes: an acquisition module 402, a traversal module 404, a determination module 406, and a testing module 408.

The obtaining module 402 is configured to obtain an engineering name of each software project included in a software project to be tested, so as to form an engineering name set; the traversal module 404 is configured to traverse the set of project names, and obtain corresponding software project configuration information according to each traversed project name; the judging module 406 is configured to judge whether an association relationship exists between the software projects, so as to obtain a judgment result; the test module 408 is configured to execute an automated test according to the determination result and the engineering configuration information.

Further, in any of the above embodiments, as shown in fig. 5, the test module 408 includes: a first deployment sub-module 4080, a first acquisition sub-module 4081, a run sub-module 4082, and an output sub-module 4083.

The first deployment submodule 4080 is configured to, when the determination result indicates that an association relationship exists between the software projects, automatically deploy a first test environment according to first environment deployment information corresponding to the traversed first software project name, and start to run the corresponding first software project, where the first software project name is any name in the project name set; the first obtaining sub-module 4081 is configured to obtain a first deployment result of the first testing environment; the running sub-module 4082 is configured to, when the first deployment result is that deployment is successful, run a first test case according to first case test information corresponding to the first software project name, and generate a first case running result, so as to determine whether to end the automated test according to the first case running result; the output sub-module 4083 is configured to output all the case operation results generated by the software project to be tested when the first deployment result is a deployment failure, and end the automated test.

Further, in the above embodiment, as shown in fig. 5, the testing module 408 further includes a scheduling sub-module 4084, where the scheduling sub-module 4084 is configured to:

when the first case operation result is normal operation, the traversing module 404 is scheduled to continue traversing other project names in the project name set until all project names in the project name set are successfully traversed, and then the output sub-module 4083 is scheduled to correspondingly output all case operation results; when the first case operation result is abnormal operation, the scheduling sub-module 4083 outputs all the case operation results generated by the software project to be tested, and the automated test is ended.

Further, in any of the above embodiments, as shown in fig. 5, the test module 408 further includes: a second deployment sub-module 4085, a second acquisition sub-module 4086, a first processing sub-module 4087, and a second processing sub-module 4088.

The second deployment submodule 4085 is configured to, when the determination result indicates that there is no association between the software projects, automatically deploy a second test environment according to second environment deployment information corresponding to the traversed second software project name, and start to run the corresponding second software project, where the second software project name is any name in the project name set; the second obtaining sub-module 4086 is configured to obtain a second deployment result of the second test environment; the first processing sub-module 4087 is configured to, when the second deployment result is that deployment is successful, run a second test case according to second case test information corresponding to the second software engineering name, generate and output a second case run result, and continue traversing other engineering names in the engineering name set until all engineering names in the engineering name set are traversed; the second processing sub-module 4088 is configured to, when the second deployment result is a deployment failure, output the second deployment result, and continue to traverse other project names in the project name set until all project names in the project name set are traversed.

Further, in any of the above embodiments, the apparatus 40 for automated testing software further includes: and a log generation module (not shown in the figure) for generating a log file in the automatic test software process to record the passing of the automatic test software process for subsequent positioning and checking, for example, positioning to the name or the number of rows of the function method, and checking the reason of the test environment deployment failure and/or the case operation abnormality.

Further, in any of the above embodiments, the obtaining module 402 is specifically configured to: and acquiring the project name of each software project through an HTTP service interface to form the project name set.

As an embodiment of the present disclosure, a server is provided, which includes the apparatus 40 for automated testing software according to the above embodiment, so that the server has all beneficial technical effects of the apparatus 40 for automated testing software, and details thereof are not described herein.

Fig. 6 shows a scheduling architecture and system diagram for test environment integration and admission according to an embodiment of the present disclosure.

As shown in fig. 6, in the embodiment of the present disclosure, aiming at the problem that manual intervention is required for test environment deployment and test case operation of multiple software projects, an automation architecture capable of scheduling test environment deployment and case operation of all software projects is designed, and system implementation is performed; the dispatching architecture and system integrating and admitting the test environment integrate the functions of test environment deployment monitoring and automatic test monitoring of case operation aiming at the problem that the test environment deployment and case test operation still need to be artificially judged; in addition, the scheduling architecture and system integrated and allowed by the test environment also provide a uniform external HTTP interface for calling the system to perform automated test of one-key test environment deployment and case operation and generate case reports (i.e. case operation results).

Specifically, when the scheduling architecture and system integrated and admitted by the test environment works, the project names of all software projects are acquired through interaction between the event scheduling module and the HTTP access layer, a project name set is formed, the project name set is further traversed, and the flow of the automated test software is further executed according to the association relationship between the software projects corresponding to the project names in the project name set, where the specific method flow is shown in fig. 7, and includes the following flow steps:

step 701, acquiring project names corresponding to all software projects to be tested, and forming a project name set.

Step 702, determining whether the traversal of the project name set is completed, if so, executing step 720, otherwise, executing step 703.

And 703, acquiring all the engineering configuration information of the corresponding software engineering from the configuration analysis module according to the traversed engineering name.

Step 704, determine whether there is a relationship between each software project, if yes, execute step 705, otherwise execute step 713.

Step 705, initializing the deployment script directory of the automated testing environment and pulling the latest deployment script of the automated testing environment.

Step 706, start script deploy test environment, pull up the latest software engineering code and start software engineering service.

Step 707, determining whether the process and the port of the current software project (i.e., the test object) are normal, i.e., determining whether the automated deployment of the test environment is successful, if so, executing step 708, otherwise, executing step 711.

Step 708, initialize the automation case running directory, and pull the latest automation test case.

Step 709, start the automated testing case and generate a case report.

Step 710, determining whether the automated test case is running normally, if yes, returning to continue to execute step 702 to traverse the next software project, otherwise, executing step 712.

Step 711 feeds back test environment deployment failure information, and then step 712 is executed.

Step 712, output the generated case report.

Step 713, initializing the deployment script directory of the automated testing environment and pulling the latest deployment script of the automated testing environment.

Step 714, the script deployment test environment is started, the latest software engineering code is pulled, and the software engineering service is started.

Step 715, determine whether the process and port of the current software project (i.e. the test object) are normal, i.e. determine whether the test environment automation deployment is successful, if yes, execute step 717, otherwise execute step 716.

And step 716, feeding back the test environment deployment failure information, and then returning to continue executing step 702 to traverse the next software project.

Step 717, initialize the automation case running directory and pull the latest automation test case.

Step 718, start the automated testing case, and generate a case report.

And step 719, outputting the currently generated case report, and then returning to continue executing step 702 to traverse the next software project.

And step 720, outputting all the generated case reports.

In the above embodiment, engineering configuration information of all software projects included in all software projects to be tested needs to be collected, including a software project name program, a code library deployed in a software project automation environment, a code library deployed in a software project automation case, and a process name and a port number of the software project, so as to be integrated into the system for configuration; developing a configuration analysis class, which can acquire the association relationship configuration information of all software projects and is used for determining whether the software projects have an association relationship, such as determining whether the software projects belong to a software project, determining whether the software projects are in a serial relationship or a parallel relationship, and the like; developing a log class, printing logs with different levels capable of positioning function method names and line numbers, recording an operation process, and facilitating subsequent inquiry and backtracking; an event scheduling class is developed, and the event scheduling class comprises two major functions: one is environment deployment, which comprises a code base actively deployed from an automation environment, an automatic deployment environment for running environment deployment scripts, and detection of processes and ports; one is to pull the code base of the latest automatic case, run the automatic case, return the case result and send the report form in the form of mail; and providing an HTTP service externally, wherein an HTTP service inlet is a set of the project names of one or more software projects to be tested, and the HTTP service inlet can enter a scheduling class to schedule the corresponding software projects.

As shown in fig. 8, a computer device 80 according to an embodiment of the present disclosure includes a memory 80, a processor 82, and a computer program stored on the memory 80 and executable on the processor 82, wherein the memory 80 and the processor 82 may be connected by a bus, and the processor 82 implements the following steps when executing the computer program:

acquiring the project name of each software project contained in the software project to be tested to form a project name set;

traversing the project name set, and acquiring the project configuration information of the corresponding software project according to each traversed project name;

judging whether an association relation exists between the software projects to obtain a judgment result;

and executing an automatic test according to the judgment result and the engineering configuration information.

The steps in the method of the embodiments of the present disclosure may be sequentially adjusted, combined, and deleted according to actual needs.

The device for automatically testing software and the units in the computer equipment in the embodiment of the disclosure can be combined, divided and deleted according to actual needs.

According to an embodiment of the disclosure, a computer-readable storage medium is proposed, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps of:

In summary, it can be understood by those skilled in the art that all or part of the steps in the methods of the above embodiments can be implemented by instructing related hardware with a program, and the program can be stored in a computer-readable storage medium, where the storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an optical Disc (Compact Disc-Read-Only Memory, CD-ROM), or other disk memories, A tape memory, or any other medium readable by a computer that can be used to carry or store data.

Further, the Computer device may be a PC (Personal Computer) terminal.

The technical scheme of the embodiment of the disclosure is described in detail above with reference to the accompanying drawings, so that the automation of test environment deployment and the automation of test case operation can be effectively realized, the labor cost is saved, the test efficiency and accuracy are improved, and the software test period is shortened.

In the embodiments of the present disclosure, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, and specific meanings of the above terms in the embodiments of the present disclosure may be understood according to specific situations by those of ordinary skill in the art.

The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure, and various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the disclosed embodiments should be included in the scope of protection of the disclosed embodiments.

Claims

1. A method for automated testing of software, comprising:

traversing the project name set, and acquiring project configuration information of the corresponding software project according to each traversed project name, wherein the project configuration information comprises environment deployment information and case test information;

executing an automated test according to the judgment result and the engineering configuration information;

wherein the executing of the automated test according to the judgment result and the engineering configuration information comprises:

when the judgment result shows that the incidence relation exists among the software projects, automatically deploying a first test environment according to first environment deployment information corresponding to the traversed first software project name, and starting to operate the corresponding first software project, wherein the first software project name is any name in the project name set;

executing an automated test according to a first deployment result of a first test environment and the case test information;

the executing the automated test according to the judgment result and the engineering configuration information further comprises:

when the judgment result shows that no incidence relation exists among the software projects, automatically deploying a second test environment according to second environment deployment information corresponding to the traversed second software project name, and starting to run the corresponding second software project, wherein the second software project name is any name in the project name set;

and executing the automatic test according to the second deployment result of the second test environment and the case test information.

2. The method for automated testing of software according to claim 1, wherein said performing automated testing based on the first deployment result of the first testing environment and the use case test information comprises:

obtaining a first deployment result of the first test environment;

when the first deployment result is successful deployment, operating a first test case according to first case test information corresponding to the first software engineering name, generating a first case operation result, and determining whether to finish the automatic test according to the first case operation result;

and when the first deployment result is a deployment failure, outputting all the case operation results generated by the software project to be tested, and finishing the automatic test.

3. The method for automatically testing software according to claim 2, wherein the step of determining whether to end the automated test according to the first example operation result comprises:

when the first case operation result is normal operation, continuously traversing other project names in the project name set until all project names in the project name set are successfully traversed, and correspondingly outputting all case operation results;

and when the first case operation result is abnormal operation, outputting all case operation results generated by the software project to be tested, and finishing the automatic test.

4. The method for automated testing of software according to claim 1, wherein said performing automated testing based on the second deployment result of the second testing environment and the use case test information comprises:

acquiring a second deployment result of the second test environment;

when the second deployment result is successful deployment, operating a second test case according to second case test information corresponding to the second software engineering name, generating and outputting a second case operation result, and continuously traversing other engineering names in the engineering name set until all the engineering names in the engineering name set are traversed;

and when the second deployment result is a deployment failure, outputting the second deployment result, and continuously traversing other project names in the project name set until all project names in the project name set are traversed.

5. The method for automatically testing software according to any one of claims 1 to 4, wherein the step of obtaining the project name of each software project included in the software project to be tested to form the project name set comprises:

and acquiring the project name of each software project through an HTTP service interface to form the project name set.

6. An apparatus for automated testing of software, comprising:

the acquisition module is used for acquiring the project names of the software projects to be tested so as to form a project name set;

the traversal module is used for traversing the project name set and acquiring corresponding software project configuration information according to each traversed project name, wherein the project configuration information comprises environment deployment information and case test information;

the judging module is used for judging whether the association relationship exists between the software projects to obtain a judging result;

the test module is used for executing an automatic test according to the judgment result and the engineering configuration information;

7. The apparatus for automated testing software according to claim 6, wherein the testing module comprises:

the first obtaining submodule is used for obtaining a first deployment result of the first testing environment;

the operation sub-module is used for operating a first test case according to first case test information corresponding to the first software engineering name when the first deployment result is successful in deployment, generating a first case operation result and determining whether to finish the automatic test according to the first case operation result;

and the output submodule is used for outputting all the case running results generated by the software project to be tested when the first deployment result is the deployment failure, and finishing the automatic test.

8. The automated test software apparatus of claim 7, wherein the test module further comprises a scheduling submodule configured to:

when the first case operation result is normal operation, scheduling the traversal module to continuously traverse other project names in the project name set until all project names in the project name set are successfully traversed, and scheduling the output submodule to correspondingly output all case operation results;

and when the first case operation result is abnormal operation, scheduling the output submodule to output all case operation results generated by the software project to be tested, and finishing the automatic test.

9. The apparatus for automated testing software according to claim 7, wherein the testing module further comprises:

the second obtaining submodule is used for obtaining a second deployment result of the second testing environment;

the first processing submodule is used for running a second test case according to second case test information corresponding to the second software engineering name when the second deployment result is that the deployment is successful, generating and outputting a second case running result, and continuously traversing other engineering names in the engineering name set until all the engineering names in the engineering name set are traversed;

and the second processing submodule is used for outputting the second deployment result when the second deployment result is the deployment failure, and continuously traversing other project names in the project name set until all the project names in the project name set are traversed.

10. The device for automated testing software according to any one of claims 6 to 9, wherein the obtaining module is specifically configured to:

11. A server, comprising: apparatus for automated testing software according to any of claims 6 to 10.

12. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program implements the steps of:

13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of: