Software testing method and device, electronic equipment and storage medium

Abstract

The invention provides a software testing method and device, electronic equipment and a storage medium, a recommended test type and a recommended test range are determined by receiving necessary test information of to-be-tested software, then an automatic script is generated according to the recommended test type and the recommended test range, and test environment deployment is performed according to a deployment configuration list. And executing the automated script in the deployed test environment to complete the test. Due to the fact that a test engineer only needs to fill in necessary test information of the to-be-tested software in the mode, the test can be completed, and the professional skill requirement for software test is lowered. Moreover, the required deployment environment can be automatically established by deploying the configuration list, so that manual deployment of the test environment is not needed, the time cost and the labor cost required by software testing are reduced, and the software testing efficiency is improved.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of software testing, and in particular to a software testing method, device, electronic device and storage medium. Background Art

[0002] At present, software testing technology, as an important means to verify the reliability and security of software, has been widely used in industries such as the Internet. In related technologies, a test engineer can deploy a set of test environments suitable for the software application to be tested according to experience for testing, or deploy multiple available test environments for parallel testing. However, this method has high requirements for the professional skills of test engineers, and manually deploying test environments requires a large amount of time and labor costs, resulting in low efficiency of software testing. Summary of the Invention

[0003] The purpose of the present invention is to provide a software testing method, device, electronic device and storage medium, which are used to lower the skill threshold of software testing and improve the efficiency of software testing.

[0004] To achieve the above object, in a first aspect, the present invention provides a software testing method, including:

[0005] Receiving necessary test information of the software to be tested, where the necessary test information includes basic information corresponding to the current test version of the software to be tested and a deployment configuration list;

[0006] Determining a recommended test type and a recommended test range according to the necessary test information, and generating an automated script according to the recommended test type and the recommended test range;

[0007] Deploying a test environment according to the deployment configuration list, and executing the automated script in the deployed test environment to complete the test.

[0008] Optionally, determining a recommended test type and a recommended test range according to the necessary test information includes:

[0009] Judging whether the software to be tested is tested for the first time according to the current test version;

[0010] If so, taking a plurality of preset test types as the recommended test types, and determining a recommended test range corresponding to the recommended test type according to the basic information;

[0011] Otherwise, extracting historical information of the software to be tested from a preset database, parsing and comparing the historical information and the basic information, and determining a recommended test type and a recommended test range according to the comparison result, where the historical information includes basic information corresponding to the historical test version of the software to be tested.

[0012] Optionally, when the basic information includes a business requirements document, determine the recommended test types and the recommended test scope according to the comparison result, including:

[0013] Determine the changed business points in the business requirements document according to the comparison result;

[0014] Select at least one test type that matches the changed business points from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed business points.

[0015] Optionally, when the basic information includes an interface design document, determine the recommended test types and the recommended test scope according to the comparison result, including:

[0016] Determine the changed interfaces in the interface design document according to the comparison result;

[0017] Select at least one test type that matches the changed interfaces from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed interfaces.

[0018] Optionally, when the basic information includes a database design document, determine the recommended test types and the recommended test scope according to the comparison result, including:

[0019] Determine the database change situation in the database design document according to the comparison result, where the database change situation includes the change situations of the table structure, entity relationship diagram, and table data volume of the corresponding database;

[0020] Select at least one test type that matches the database change situation from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the database change situation.

[0021] Optionally, when the basic information includes a code file, determine the recommended test types and the recommended test scope according to the comparison result, including:

[0022] Determine the changed code in the code file according to the comparison result, where the changed code includes the front-end code and back-end code corresponding to the changes of the software to be tested;

[0023] Select at least one test type that matches the changed code from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed code.

[0024] Optionally, when the basic information includes a business architecture diagram, determine the recommended test types and the recommended test scope according to the comparison result, including:

[0025] Determine the changed architecture relationship in the business architecture diagram according to the comparison result, and determine the changed configuration resources corresponding to the changed architecture relationship according to the deployment configuration list;

[0026] Select at least one test type that matches the changed architecture relationship and the changed configuration resources from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed architecture relationship and the changed configuration resources.

[0027] Optionally, perform test environment deployment according to the deployment configuration list, including:

[0028] Obtain environment deployment resources according to the selected deployment method, where the environment deployment resources support deploying a specified number of test environments;

[0029] Use the environment deployment resources to perform deployment of the corresponding number of test environments according to the deployment configuration list.

[0030] In a second aspect, the present application provides a software testing device, including:

[0031] An information receiving module, configured to receive necessary test information of the software to be tested, where the necessary test information includes basic information corresponding to the current test version of the software to be tested and a deployment configuration list;

[0032] A test recommendation module, configured to determine a recommended test type and a recommended test scope according to the necessary test information, and generate an automated script according to the recommended test type and the recommended test scope;

[0033] An environment deployment module, configured to perform test environment deployment according to the deployment configuration list, and execute the automated script in the deployed test environment to complete the test.

[0034] In a third aspect, the present application provides an electronic device, including a memory and a processor; instructions are stored in the memory, and when the instructions are called by the processor, the processor is caused to execute the method according to any one of the first aspects above.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium, including computer program instructions, and when the computer program instructions are called by a computer, the computer is caused to implement the method according to any one of the first aspects above.

[0036] Compared with the prior art, the present invention has the following advantages:

[0037] The present application provides a software testing method, apparatus, electronic device and storage medium. By receiving the necessary test information of the software to be tested, the recommended test type and the recommended test scope are determined. Subsequently, an automated script is generated according to the recommended test type and the recommended test scope, the test environment is deployed according to the deployment configuration list, and the automated script is executed in the deployed test environment to complete the test. Since in this way, the test engineer only needs to fill in the necessary test information of the software to be tested to complete the test, the professional skill requirements for software testing are reduced. Moreover, the required deployment environment can be automatically built through the deployment configuration list, so there is no need to manually deploy the test environment, reducing the time cost and labor cost required for software testing and improving the efficiency of software testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings are provided to provide a further understanding of the present application, and they are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings:

[0039] Figure 1 is a flowchart of a software testing method provided by an exemplary embodiment of the present application;

[0040] Figure 2 is an example diagram of a file preference level provided by an exemplary embodiment of the present application;

[0041] Figure 3 is a logical schematic diagram of a software testing method provided by an exemplary embodiment of the present application;

[0042] Figure 4 is an example diagram of a software testing apparatus provided by an exemplary embodiment of the present application;

[0043] Figure 5 is a schematic diagram of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0044] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some examples or embodiments of the present application. For those of ordinary skill in the art, without creative efforts, the present application can also be applied to other similar scenarios based on these drawings. Unless it is obvious from the language context or otherwise stated, the same reference numerals in the drawings represent the same structure or operation.

[0045] As shown in this application and the claims, unless the context clearly indicates otherwise, words such as "a", "an", "one", and / or "the" are not specifically singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of the clearly identified steps and elements, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0046] In the first aspect of the exemplary embodiment of the present application, a software testing method is provided, which will be described below with reference to Figures 1 to 2 for description. This method can be applied to the field of software testing technology. According to the steps of the software testing method of the exemplary embodiment of the present application, it can be executed on an electronic device. For example, it can be executed on a server. As Figure 1 , this method may include:

[0047] S101, receiving the necessary test information of the software to be tested, where the necessary test information includes the basic information corresponding to the current test version of the software to be tested and the deployment configuration list.

[0048] S102, determining the recommended test type and the recommended test range according to the necessary test information, and generating an automated script according to the recommended test type and the recommended test range.

[0049] S103, deploying the test environment according to the deployment configuration list, and executing the automated script in the deployed test environment to complete the test.

[0050] Specifically, the test engineer can create the current test version of the software to be tested in the server, and then send the necessary test information corresponding to the current test version to the server. In normal operations, the test engineer can choose to increment on the basis of the existing test version of the software to be tested to create the current test version of the software to be tested, or directly create a new test version as the current test version. In this embodiment, the necessary test information of the software to be tested may include the basic information corresponding to the current test version of the software to be tested and the deployment configuration list. The server can determine the recommended test type and the recommended test range according to the received necessary test information.

[0051] Preferably, the server can determine whether the software to be tested is being tested for the first time based on the current test version. In the case of the first test, the server can use multiple preset test types as the recommended test types and determine the recommended test scope corresponding to the recommended test types based on the basic information. For example, the multiple test types can include code testing, document testing, capacity testing, interface function testing, page function testing, compatibility testing, performance testing, stress testing, reliability testing, stability testing, database function testing, and so on. The server can recommend the test types that can be executed in parallel, such as code testing, document testing, capacity testing, interface function testing, page function testing, database function testing, compatibility testing, etc., and the test types that cannot be executed in parallel, such as performance testing, stress testing, and so on. The server can use these test types as the recommended test types and determine the recommended test scope corresponding to these recommended test types based on the basic information. In addition, these recommended test types can be set with priorities, so that the server can perform the tests in descending order of priorities, that is, the test order corresponding to the recommended test types can be determined according to the priorities of the recommended test types.

[0052] In the case of non-first test, the server can extract the historical information of the software to be tested from the preset database. The historical information can include the basic information corresponding to the historical test version of the software to be tested. Subsequently, the server can parse and compare the historical information and the basic information, and determine the recommended test types and the recommended test scope based on the comparison result. Preferably, the basic information can include any one or combination of the business requirement document, interface design document, database design document, code file, and business architecture diagram associated with the current test version of the software to be tested. The following will be elaborated with an example including all the above files.

[0053] In the case where the basic information includes the business requirement document, the server can determine the changed business points in the business requirement document of the current test version based on the comparison result. The changed business points can include the business requirements such as the functional logic, performance, security, compatibility, etc. that need to be satisfied and have changed in the current test version compared with the historical test version. Subsequently, the server can select at least one of the multiple test types that match the changed business points as the recommended test types. For example, assuming that the changed business points involve the functional logic of an interface function point of the software to be tested, then the server can select interface function testing, performance testing, stress testing, etc. from the test types mentioned above as the recommended test types, and determine the recommended test scope corresponding to the recommended test types according to the specific content of the changed business points.

[0054] When the basic information includes an interface design document, the server can determine the changed interfaces in the interface design document of the current test version based on the comparison result. Subsequently, the server can select at least one test type that matches the changed interfaces from multiple test types as the recommended test type. For example, interface function testing, performance testing, stress testing, stability testing, etc. can be selected from the test types mentioned above as the recommended test types, and the recommended test scope corresponding to the recommended test type can be determined according to the specific content of the changed interfaces. Preferably, the server can also automatically generate an interface function test script and an interface performance test script corresponding to the interface function of the changed interfaces according to a preset template. The test engineer can use these scripts for testing to further improve the efficiency of software testing.

[0055] When the basic information includes a database design document, the server can determine the database change situation in the database design document based on the comparison result. The database change situation can include changes in the table structure, entity relationship diagram, table data volume, etc. of the corresponding database. Subsequently, the server can select at least one test type that matches the database change situation from multiple test types as the recommended test type. For example, database function testing, performance testing, stress testing, stability testing, etc. can be selected from the test types mentioned above as the recommended test types, and the recommended test scope corresponding to the recommended test type can be determined according to the specific content of the database change situation.

[0056] When the basic information includes a code file, the server can determine the changed code in the code file based on the comparison result. The changed code can include the front-end code and the back-end code corresponding to the changes in the software to be tested. Changes in the front-end code can be changes in the page display method, front-end interface interaction, etc. Changes in the back-end code can be changes in business processing logic, interface function logic, etc. Subsequently, the server can select at least one test type that matches the changed code from multiple test types as the recommended test type. For example, assuming that the changed code involves the function logic of an interface in the back-end code, then the server can select interface function testing, performance testing, stress testing, stability testing, etc. from the test types mentioned above as the recommended test types, and the recommended test scope corresponding to the recommended test type can be determined according to the specific content of the changed code.

[0057] In the case where the basic information includes a business architecture diagram, the server can determine the changed architecture relationship in the business architecture diagram according to the comparison result, and determine the changed configuration resources corresponding to the changed architecture relationship according to the deployment configuration list. The changed architecture relationship can be, for example, the change of the business architecture. The changed configuration resources can be, for example, the configuration resources corresponding to the changed applications, middleware, data clusters, etc. The server can select at least one test type that matches the changed architecture relationship and the changed configuration resources from multiple test types as the recommended test type. For example, performance testing, stress testing, capacity testing, stability testing, etc. can be selected from the test types mentioned above as the recommended test types, and then the recommended test scope corresponding to the recommended test type can be determined according to the specific content of the changed architecture relationship and the changed configuration resources.

[0058] It should be noted that the above steps can be implemented independently, or they can also be implemented according to a certain file priority to facilitate the selection of the most appropriate recommended test type and recommended test scope. Preferably, as Figure 2 shown, in this embodiment, the server can select the most appropriate recommended test type and recommended test scope according to the file priority of the business requirement document - interface design document - database design document - code document - business architecture diagram. In practical applications, the test engineer can also manually select the test types and test scopes he needs, and there is no restriction on this.

[0059] Preferably, the test engineer can select a suitable deployment method according to the actual situation (such as including the urgency of the version or the cost of resource procurement, etc.). The deployment method can be a resource-saving deployment method or the fastest deployment method. For example, if the current test version is relatively urgent and the resource procurement cost is low, then the test engineer can select the fastest deployment method. In this way, the server can obtain the environment deployment resources that support the deployment of multiple test environments according to the selected fastest deployment method, and then deploy multiple test environments in parallel according to the deployment configuration list and the environment deployment resources. Another example is that if the urgency of the current test version is low and the resource procurement cost is high, then the test engineer can select the resource-saving deployment method. In this way, the server can obtain the environment deployment resources that only support the deployment of one test environment according to the selected resource-saving deployment method, and then deploy one test environment according to the deployment configuration list and the environment deployment resources for testing.

[0060] As Figure 3As shown in the figure, the server receives the necessary test information of the software to be tested. It can determine whether the software to be tested is tested for the first time. If so, the server can use all test types as the recommended test types and determine the recommended test scope based on the basic information. Otherwise, the server can determine the recommended test types and the recommended test scope according to the comparison result with the historical information. Subsequently, the server can generate an automated script according to the recommended test types and the recommended test scope, and then deploy the test environment according to the deployment method and the deployment configuration list selected by the test engineer. Then, the generated automated script is executed in the test environment to complete the test. In addition, the server can also summarize the test results corresponding to the automated script and generate a test report to display to the test engineer.

[0061] This application provides a software testing method, device, electronic device, and storage medium. By receiving the necessary test information of the software to be tested, the recommended test types and the recommended test scope are determined. Subsequently, an automated script is generated according to the recommended test types and the recommended test scope, the test environment is deployed according to the deployment configuration list, and the automated script is executed in the deployed test environment to complete the test. Since in this way, the test engineer only needs to fill in the necessary test information of the software to be tested to complete the test, the professional skill requirements for software testing are reduced. Moreover, the required deployment environment can be automatically built through the deployment configuration list, so there is no need to manually deploy the test environment, reducing the time cost and labor cost required for software testing and improving the efficiency of software testing.

[0062] As Figure 4 , this application also provides a software testing device, including an information receiving module 401, a test recommendation module 402, and an environment deployment module 403, where:

[0063] The information receiving module 401 is used to receive the necessary test information of the software to be tested, where the necessary test information includes the basic information corresponding to the current test version of the software to be tested and the deployment configuration list;

[0064] The test recommendation module 402 is used to determine the recommended test types and the recommended test scope according to the necessary test information, and generate an automated script according to the recommended test types and the recommended test scope;

[0065] The environment deployment module 403 is used to deploy the test environment according to the deployment configuration list and execute the automated script in the deployed test environment to complete the test.

[0066] Optionally, to determine the recommended test types and the recommended test scope according to the necessary test information, the test recommendation module 402 is used to:

[0067] Judge whether the software to be tested is tested for the first time according to the current test version;

[0068] If so, use multiple preset test types as the recommended test types, and determine the recommended test scope corresponding to the recommended test types according to the basic information;

[0069] Otherwise, extract the historical information of the software to be tested from the preset database, parse and compare the historical information with the basic information, and determine the recommended test types and the recommended test scope according to the comparison result, where the historical information includes the basic information corresponding to the historical test version of the software to be tested.

[0070] Optionally, when the basic information includes a business requirements document, determine the recommended test types and the recommended test scope according to the comparison result. The test recommendation module 402 is used for:

[0071] Determine the changed business points in the business requirements document according to the comparison result;

[0072] Select at least one of the multiple test types that matches the changed business points as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed business points.

[0073] Optionally, when the basic information includes an interface design document, determine the recommended test types and the recommended test scope according to the comparison result. The test recommendation module 402 is used for:

[0074] Determine the changed interfaces in the interface design document according to the comparison result;

[0075] Select at least one of the multiple test types that matches the changed interfaces as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed interfaces.

[0076] Optionally, when the basic information includes a database design document, determine the recommended test types and the recommended test scope according to the comparison result. The test recommendation module 402 is used for:

[0077] Determine the database change situation in the database design document according to the comparison result, where the database change situation includes the change situations of the table structure, entity relationship diagram, and table data volume of the corresponding database;

[0078] Select at least one of the multiple test types that matches the database change situation as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the database change situation.

[0079] Optionally, when the basic information includes code files, determine the recommended test types and the recommended test scope according to the comparison result. The test recommendation module 402 is used for:

[0080] Determine the changed code in the code file according to the comparison result, where the changed code includes the front-end code and the back-end code corresponding to the changes of the software to be tested;

[0081] Select at least one test type that matches the changed code from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed code.

[0082] Optionally, when the basic information includes a business architecture diagram, determine the recommended test type and the recommended test scope according to the comparison result. The test recommendation module 402 is used for:

[0083] Determine the changed architecture relationship in the business architecture diagram according to the comparison result, and determine the changed configuration resources corresponding to the changed architecture relationship according to the deployment configuration list;

[0084] Select at least one test type that matches the changed architecture relationship and the changed configuration resources from multiple test types as the recommended test type, and determine the recommended test scope corresponding to the recommended test type according to the changed architecture relationship and the changed configuration resources.

[0085] Optionally, deploy the test environment according to the deployment configuration list. The environment deployment module 403 is used for:

[0086] Obtain environment deployment resources according to the selected deployment method, where the environment deployment resources support deploying a specified number of test environments;

[0087] Use the environment deployment resources to deploy the corresponding number of test environments according to the deployment configuration list.

[0088] Such as Figure 5 An exemplary embodiment of the present application also provides an electronic device. It includes a memory 501 and a processor 502. Computer-readable instructions are stored in the memory 501. When the computer-readable instructions are executed by the processor 502, the processor 502 executes the steps of any one of the above-mentioned software testing methods.

[0089] It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or may also be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0090] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous link dynamic random access memory, and direct memory bus random access memory.

[0091] The present application also provides a computer-readable storage medium, which stores computer program instructions. When the computer program instructions are executed by a processor of the computer, the computer is caused to execute the steps of any of the software testing methods mentioned above.

[0092] The computer-readable medium may include a propagated data signal having computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take many forms, including electromagnetic, optical, and the like, or any suitable combination thereof. The computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, apparatus, or device to effect communication, propagation, or transmission for use. The program code located on the computer-readable medium may be propagated through any appropriate medium, including radio, cable, fiber optic cable, radio frequency signal, or similar media, or any combination of the foregoing media.

[0093] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only an example and does not constitute a limitation to the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to the present application. Such modifications, improvements, and corrections are proposed in the present application, so such modifications, improvements, and corrections still fall within the spirit and scope of the exemplary embodiments of the present application.

[0094] Meanwhile, the present application uses specific terms to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that the "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the present application can be appropriately combined.

[0095] Some aspects of the present application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above-mentioned hardware or software can all be referred to as "data block", "module", "engine", "unit", "component" or "system". The processor can be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, aspects of the present application may be embodied as a computer product located in one or more computer-readable media, which includes computer-readable program code. For example, the computer-readable media may include, but is not limited to, magnetic storage devices (such as hard disks, floppy disks, magnetic tapes...), optical disks (such as compact disks CD, digital versatile disks DVD...), smart cards, and flash memory devices (such as cards, sticks, key drives...).

[0096] The computer-readable media may contain a propagated data signal that contains computer program code, for example, on a baseband or as part of a carrier wave. The propagated signal may have various forms of representation, including electromagnetic form, optical form, etc., or a suitable combination thereof. The computer-readable media can be any computer-readable media other than computer-readable storage media, which can be connected to an instruction execution system, apparatus, or device to implement communication, propagation, or transmission for use of the program. The program code located on the computer-readable media can be propagated through any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar media, or any combination of the above media.

[0097] Similarly, it should be noted that, in order to simplify the description of the present application and thus help the understanding of one or more inventive embodiments, in the previous description of the embodiments of the present application, sometimes multiple features are merged into one embodiment, drawing, or description thereof. However, this disclosure method does not mean that the features required by the subject matter of the present application are more than those mentioned in the claims. In fact, the features of the embodiments are fewer than all the features of the single embodiments disclosed above.

[0098] In some embodiments, numbers are used to describe components and the quantity of attributes. It should be understood that such numbers used in the description of embodiments are, in some examples, modified by the modifiers "about", "approximately" or "substantially". Unless otherwise specified, "about", "approximately" or "substantially" indicate that the stated number allows a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may vary according to the characteristics required by individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used in some embodiments of the present application to confirm the breadth of their scope are approximate values, in specific embodiments, such numerical settings are as precise as possible within the feasible range.

[0099] Although the present application has been described with reference to current specific embodiments, those of ordinary skill in the art should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications of the above embodiments are within the scope of the spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A software testing method, characterized in that, Including: Receiving necessary test information of the software to be tested, where the necessary test information includes basic information corresponding to the current test version of the software to be tested and a deployment configuration list; Determining a recommended test type and a recommended test scope according to the necessary test information, and generating an automated script according to the recommended test type and the recommended test scope; Deploying a test environment according to the deployment configuration list, and executing the automated script in the deployed test environment to complete the test.

2. The method according to claim 1, characterized in that, The determining a recommended test type and a recommended test scope according to the necessary test information includes: Judging whether the software to be tested is tested for the first time according to the current test version; If so, taking a plurality of preset test types as the recommended test type, and determining a recommended test scope corresponding to the recommended test type according to the basic information; Otherwise, extracting historical information of the software to be tested from a preset database, parsing and comparing the historical information and the basic information, and determining a recommended test type and a recommended test scope according to the comparison result, where the historical information includes basic information corresponding to the historical test version of the software to be tested.

3. The method according to claim 2, wherein When the basic information includes a business requirement document, the determining a recommended test type and a recommended test scope according to the comparison result includes: Determining changed business points in the business requirement document according to the comparison result; Selecting at least one of the plurality of test types that matches the changed business points as the recommended test type, and determining a recommended test scope corresponding to the recommended test type according to the changed business points.

4. The method according to claim 2, wherein When the basic information includes an interface design document, the determining a recommended test type and a recommended test scope according to the comparison result includes: Determining changed interfaces in the interface design document according to the comparison result; Selecting at least one of the plurality of test types that matches the changed interfaces as the recommended test type, and determining a recommended test scope corresponding to the recommended test type according to the changed interfaces.

5. The method according to claim 2, wherein When the basic information includes a database design document, the determining a recommended test type and a recommended test scope according to the comparison result includes: Determining database change situations in the database design document according to the comparison result, where the database change situations include change situations of the table structure, entity relationship diagram, and table data volume of the corresponding database; Selecting at least one of the plurality of test types that matches the database change situations as the recommended test type, and determining a recommended test scope corresponding to the recommended test type according to the database change situations.

6. The method according to claim 2, wherein When the basic information includes code files, the determining a recommended test type and a recommended test scope according to the comparison result includes: Determining changed code in the code files according to the comparison result, where the changed code includes front-end code and back-end code corresponding to changes in the software to be tested; Select at least one test type that matches the change code from the multiple test types, and determine the recommended test scope corresponding to the recommended test type according to the change code.

7. The method according to claim 2, wherein When the basic information includes a business architecture diagram, the determining of the recommended test type and the recommended test scope according to the comparison result includes: Determine the changed architecture relationship in the business architecture diagram according to the comparison result, and determine the changed configuration resources corresponding to the changed architecture relationship according to the deployment configuration list; Select at least one test type that matches the changed architecture relationship and the changed configuration resources from the multiple test types, and determine the recommended test scope corresponding to the recommended test type according to the changed architecture relationship and the changed configuration resources.

8. The method according to any one of claims 1-7, characterized in that, The performing of the test environment deployment according to the deployment configuration list includes: Obtain environment deployment resources according to the selected deployment method, where the environment deployment resources support the deployment of a specified number of test environments; Use the environment deployment resources to perform the deployment of the corresponding number of test environments according to the deployment configuration list.

9. A software testing device, characterized in that, Includes: An information receiving module, configured to receive the necessary test information of the software to be tested, where the necessary test information includes the basic information corresponding to the current test version of the software to be tested and the deployment configuration list; A test recommendation module, configured to determine the recommended test type and the recommended test scope according to the necessary test information, and generate an automation script according to the recommended test type and the recommended test scope; An environment deployment module, configured to perform test environment deployment according to the deployment configuration list, and execute the automation script in the deployed test environment to complete the test.

10. An electronic device, characterized in that, Includes a memory and a processor; instructions are stored in the memory, and when the instructions are called by the processor, the processor executes the method according to any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, Includes computer program instructions, and when the computer program instructions are called by a computer, the computer implements the method according to any one of claims 1-8.

Images