Software automated testing method, device, equipment and readable storage medium

Abstract

The present invention relates to the field of software testing, and in particular, to a software automated testing method, apparatus, device, and readable storage medium. The method comprises obtaining library table data of a software testing environment to be tested; inputting the library table data into a first processing module for screening and filtering to obtain first scenario data; inputting the first scenario data into a second processing module for loading to obtain an automated script loaded with the first scenario data; inputting the automated script into a third processing module for execution to obtain software automated testing results. The present invention matches data of the corresponding environment based on an established data model and in combination with the test environment required for actual testing, loads data that meets the test scenario into the automated script, and implements software automated testing through scheduling and execution using automated tools, thereby achieving full decoupling of test data, test scripts, and test environments in software automated testing.

Description

Technical Field

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

[0002] In the software testing industry, existing technologies only separate a single type of test script from test data. Switching to a new test environment requires re-preparing test data. If test scripts are used in different software automation testing tools, different test data types and formats are required. Switching test environments and inconsistent testing tools are common testing processes, and existing approaches can severely impact software automation testing efficiency and the utilization of automated scripts. Existing technologies rely on test scripts from software automation testing tools, which are not adaptable to various test environments and fail to cover a wide range of test scenarios. Summary of the Invention

[0003] The purpose of the present invention is to provide a software automated testing method, apparatus, device, and readable storage medium to improve the above-mentioned problems. To achieve the above-mentioned purpose, the technical solution adopted by the present invention is as follows:

[0004] In one aspect, the present application provides a software automation testing method, the method comprising:

[0005] Obtain the library table data of the software testing environment that needs to be tested;

[0006] Inputting the library table data into a first processing module for screening and filtering to obtain first scenario data, wherein the first processing module is a data processing model that uses data cleaning to remove dirty data and uses data cleaning to remove non-business data, and the first scenario data is test scenario data generated by combining the software test environment library table data;

[0007] Inputting the first scene data into a second processing module for loading to obtain an automation script loaded with the first scene data, wherein the second processing module is a module including at least one automation script, and the second processing module is a module for loading scene data;

[0008] The automation script is input into the third processing module for execution to obtain the software automation test result. The third processing module is a software automation test execution module, and the software automation test execution module is a module that controls the automation script to perform software automation testing.

[0009] Optionally, obtaining the software test environment library table data to be tested includes:

[0010] Obtain software testing environment data;

[0011] Classifying the software testing environment data to obtain system library table data under different environments;

[0012] Matching the system library table data in at least one software test environment with the first processing module, determining the software test environment library table data that needs to be tested, and calling the software test environment library table data that needs to be tested in real time.

[0013] Optionally, the step of inputting the software test environment library table data to be tested into a first processing module for screening and filtering to obtain first scenario data includes:

[0014] Extract, clean and integrate the software test environment database data to be tested in real time to obtain processed environment data;

[0015] Obtain the generation rules of scene data and input them into the database for storage;

[0016] The generated rule of the scene data is called to process the processed environmental data to generate the first scene data in real time.

[0017] Optionally, inputting the first scene data into the second processing module for loading to obtain an automation script file loaded with the first scene data includes:

[0018] Detecting whether the interface of the second processing module is connected to the interface of the first processing module;

[0019] If the interface of the second processing module is connected to the interface of the first processing module, the first scene data is loaded into the automation script to obtain an automation script file loaded with the first scene data;

[0020] If the interface of the second processing module is not docked with the interface of the first processing module, the interface of the second processing module is matched and docked with the interface of the first processing module, and the first scene data is loaded into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

[0021] Optionally, the step of inputting the first scene data into the second processing module for loading to obtain an automated script loaded with the first scene data further includes:

[0022] Matching the first scenario data with the current software test environment library table data to determine whether the first scenario data is scenario data generated from the current software test environment library table data;

[0023] If the first scenario data is scenario data generated from the current software test environment library table data, sending the first scenario data to the second processing module for loading;

[0024] If the first scenario data is not scenario data generated from the current software test environment library table data, the first scenario data is marked in red for storage, and the current software test environment library table data is used to generate second scenario data.

[0025] Optionally, the step of inputting the automation script file into a third processing module for execution to obtain a software automation test result further includes:

[0026] Calling new test environment library table data from the software test environment library table data;

[0027] Inputting the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, wherein the third scenario data is test scenario data generated by combining the new test environment library table data;

[0028] Rematching the interface connecting the first processing module and the second processing module, and connecting to the second processing module interface matching the third scene data;

[0029] Loading the third scene data into a second automation script through the second processing module interface to obtain a second automation script loaded with the third scene data;

[0030] The second automation script is input into the third processing module for execution to obtain a new software automation test result, which is then stored.

[0031] In a second aspect, an embodiment of the present application provides a software automation testing device, the device comprising:

[0032] A first acquisition unit is used to acquire library table data of a software test environment to be tested;

[0033] a first processing unit, configured to input the library table data into a first processing module for screening and filtering to obtain first scenario data, wherein the first processing module is a data processing model that uses data cleaning to remove dirty data and uses data cleaning to remove non-business data, and the first scenario data is test scenario data generated by combining the software test environment library table data;

[0034] a second processing unit, configured to input the first scene data into a second processing module for loading, thereby obtaining an automation script loaded with the first scene data, wherein the second processing module is a module including at least one automation script, and is a module for loading scene data;

[0035] The third processing unit is used to input the automation script into the third processing module for execution to obtain the software automation test results. The third processing module is a software automation test execution module, and the software automation test execution module is a module that controls the automation script to perform software automation testing.

[0036] Optionally, the device comprises:

[0037] A first acquisition subunit is used to acquire software test environment data;

[0038] A first processing subunit is used to classify the software test environment data to obtain system library table data under different environments;

[0039] The second processing sub-unit is used to match the system library table data in at least one software testing environment with the first processing module, determine the software testing environment library table data that needs to be tested, and call the software testing environment library table data that needs to be tested in real time.

[0040] Optionally, the device comprises:

[0041] The third processing sub-unit is used to extract, clean and integrate the software test environment library table data to be tested in real time to obtain processed environment data;

[0042] The second acquisition subunit is used to acquire generation rules of scene data and input them into the database for storage;

[0043] The fourth processing sub-unit is used to call the generation rule of the scene data to process the processed environmental data and generate the first scene data in real time.

[0044] Optionally, the device comprises:

[0045] a fifth processing subunit, configured to detect whether the interface of the second processing module is connected to the interface of the first processing module;

[0046] a first judgment subunit, configured to load the first scenario data into the automation script if the interface of the second processing module is connected to the interface of the first processing module, to obtain an automation script file loaded with the first scenario data;

[0047] The second judgment sub-unit is used to match and dock the interface of the second processing module with the interface of the first processing module if the interface of the second processing module has not been docked with the interface of the first processing module, and load the first scene data into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

[0048] Optionally, the device further comprises:

[0049] A first judging unit is configured to match the first scenario data with the current software test environment library table data to judge whether the first scenario data is scenario data generated from the current software test environment library table data;

[0050] a second judgment unit, configured to send the first scenario data to the second processing module for loading if the first scenario data is scenario data generated from the current software test environment library table data;

[0051] The third judgment unit is used to mark the first scenario data in red for storage if the first scenario data is not scenario data generated by the current software test environment library table data, and generate second scenario data from the current software test environment library table data.

[0052] Optionally, the device further comprises:

[0053] A fourth processing unit, configured to call new test environment library table data from the software test environment library table data;

[0054] a fifth processing unit, configured to input the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, wherein the third scenario data is test scenario data generated by combining the new test environment library table data;

[0055] a sixth processing unit, configured to re-match the interface connecting the first processing module and the second processing module, and access the interface of the second processing module matching the third scene data;

[0056] a seventh processing unit, configured to load the third scenario data into a second automation script through the second processing module interface, to obtain the second automation script loaded with the third scenario data;

[0057] The eighth processing unit is used to input the second automation script into the third processing module for execution, obtain a new software automation test result, and store it.

[0058] In a third aspect, an embodiment of the present application provides a software automated testing device, comprising a memory and a processor. The memory is used to store a computer program; the processor is used to implement the steps of the above-mentioned software automated testing method when executing the computer program.

[0059] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned software automation testing method are implemented.

[0060] The beneficial effects of the present invention are:

[0061] 1. This invention implements a fully decoupled software automation testing solution for test data, test environment, and test scripts. Based on an established data model and the test environment required for actual testing, data matching and extraction are performed for the corresponding environment. Data that meets the test scenario is loaded into the automation script, and scheduling and execution are completed through automated tools to achieve software automation testing. This achieves the complete decoupling of the three elements of software automation testing: test data, test scripts, and test environment.

[0062] 2. This invention ensures the diversity and timeliness of software automation test data, and can also test the latest data while achieving automation;

[0063] 3. The present invention constructs a platform-based software automation testing framework, simplifies the learning and use costs of various software automation testing frameworks, and greatly improves testing efficiency.

[0064] 4. The present invention constructs a platform-based software automation testing framework, simplifies the learning and use costs of various software automation testing frameworks, and greatly improves testing efficiency.

[0065] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or understood by practicing the embodiments of the present invention. The purposes and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0067] Figure 1 A flowchart of a software automation testing method according to an embodiment of the present invention is shown;

[0068] Figure 2 Schematic diagram of the structure of a software automation testing device according to an embodiment of the present invention;

[0069] Figure 3 This is a structural diagram of a software automation testing device described in an embodiment of the present invention. DETAILED DESCRIPTION

[0070] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0071] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are used only to distinguish the description and should not be understood as indicating or implying relative importance.

[0072] Example 1

[0073] like Figure 1 As shown, this embodiment provides a software automation testing method, which includes step S1, step S2, step S3, step S4 and step S5.

[0074] Step S1: Obtain the library table data of the software testing environment to be tested;

[0075] Step S2: Input the library table data into a first processing module for screening and filtering to obtain first scenario data. The first processing module is a data processing model that uses data cleaning to remove dirty data and uses data cleaning to remove non-business data. The first scenario data is test scenario data generated by combining the software test environment library table data.

[0076] Step S3: inputting the first scene data into a second processing module for loading, thereby obtaining an automation script loaded with the first scene data, wherein the second processing module is a module including at least one automation script, and the second processing module is a module for loading scene data;

[0077] Step S4: input the automation script into the third processing module for execution to obtain the software automation test result. The third processing module is a software automation test execution module, and the software automation test execution module is a module that controls the automation script to perform software automation testing.

[0078] It is understood that the data cleaning module in the present invention determines the business system for the required test data based on the test scenario, extracts the database table data of the business system into the business class basic data pool through data cleaning and integration, and then constructs a test scenario data matching model based on data relationship calculation and data relationship matching, combined with the test scenario. This matching model includes a data transfer module between scenarios, scenario combination relationships, and transaction chain association relationships. This data cleaning module is actually an abstract data class, applicable to any test environment, and can update the available data in real time based on the current data in the environment. The present invention also provides a test environment module, which provides source data for the first processing module and is composed of various test environments. It mainly obtains the library table data of each business system in the corresponding environment for real-time or scheduled extraction by the first processing module; the second processing module in the present invention is mainly used to run test data in various environments and complete software automation testing. It is the carrier of test data execution and supports various software automation testing tools, including common interface automation tools, QTP automation tools, Web interface automation tools, App interface automation tools, automation automation tools, etc. The third processing module in the present invention is used to perform software testing to achieve 24-hour unattended and automatic full-scene switching software automation testing.

[0079] Furthermore, any module in this invention can be used independently, and any module can be accessed and used through the external interfaces provided by each other, realizing pluggable testing of environments, data, and scripts. This solution also facilitates the independent expansion and application of each module. On the one hand, machine control ensures the freshness, diversity, and timeliness of scenario data. On the other hand, it builds a platform-based software automation testing framework, simplifying the learning and use costs of various software automation testing frameworks and greatly improving testing efficiency.

[0080] In a specific embodiment of the present disclosure, step S1 includes step S11, step S12 and step S13.

[0081] Step S11: Acquire software testing environment data;

[0082] Step S12: classify the software test environment data to obtain system library table data under different environments;

[0083] Step S13: Match the system library table data in at least one software test environment with the first processing module, determine the software test environment library table data that needs to be tested, and call the software test environment library table data that needs to be tested in real time.

[0084] It is understood that the test environment module in the present invention provides source data for the first processing module. The test environment module includes various test environments. Its main function is to obtain the library table data of each business system in the corresponding environment for the first processing module to extract and use in real time or on a scheduled basis.

[0085] In a specific embodiment of the present disclosure, step S2 includes step S21, step S22 and step S23.

[0086] Step S21: extract, clean and integrate the software test environment library table data to be tested in real time to obtain processed environment data;

[0087] Step S22: Obtaining the generation rules of scene data and inputting them into the database for storage;

[0088] Step S23: calling the scene data generation rule to process the processed environmental data to generate first scene data in real time.

[0089] It can be understood that the first processing module in the present invention relies on scenario automation, and the pre-established data combination relationship that meets the scenario can realize the dynamic value of the automation field and the dynamic linkage value between the fields with related relationships, and abstract the data cleaning module, which is similar to a filter. All environmental data that meets the test can be loaded with this data cleaning module to extract the scenario data that meets the automation script. Therefore, if the normal test environment includes TRA, TC and other environments, the data of these environments can be extracted to meet the scenario data of the environment of the automation script. This extraction is real-time and is dynamically updated according to the updates and changes of the current environmental data, which ensures the timeliness, freshness and diversity of the software automation test data.

[0090] In a specific embodiment of the present disclosure, step S3 includes step S31, step S32 and step S33.

[0091] Step S21: Detect whether the interface of the second processing module and the interface of the first processing module are connected;

[0092] Step S22: If the interface of the second processing module is connected to the interface of the first processing module, the first scene data is loaded into the automation script to obtain an automation script file loaded with the first scene data;

[0093] Step S23: If the interface of the second processing module is not docked with the interface of the first processing module, the interface of the second processing module is matched and docked with the interface of the first processing module, and the first scene data is loaded into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

[0094] It's understandable that the present invention, through the extraction of scenario data models, removes the strong dependency between automated scripts and test data. The scenario data model is also independent of the form of the automated software test script, whether it's an interface automation script, an interface automation script, or a QTP script, nor does it rely on the automated software testing tools used by the automated software test script. Because the platform provides a form similar to an external API, it can connect to test scripts from any testing tool to complete data transmission.

[0095] It can be understood that the second processing module is mainly used to support various software automation testing tools, including common interface automation tools, QTP automation tools, Web interface automation tools, App interface automation tools, automation tools, etc. This module is connected to the interface of the first processing module, and uses the automation scripts on various automation tools to load scene data to realize data filling of the automation script.

[0096] The third module can be understood to load the automated script of scene data to perform software testing, realizing 24-hour unattended and automatic full-scene switching software automation testing.

[0097] In a specific embodiment of the present disclosure, step S4 further includes step S5, step S6 and step S7.

[0098] Step S5: Match the first scenario data with the current software test environment library table data to determine whether the first scenario data is scenario data generated from the current software test environment library table data;

[0099] Step S6: If the first scenario data is scenario data generated from the current software test environment library table data, the first scenario data is sent to the second processing module for loading;

[0100] Step S7: If the first scenario data is not scenario data generated from the current software test environment library table data, the first scenario data is marked in red for storage, and second scenario data is generated from the current software test environment library table data.

[0101] It can be understood that the present invention determines whether the scenario data is real-time scenario data by determining whether the first scenario data is scenario data generated by the current software testing environment library table data, and then dynamically updates and changes according to the update changes of the current environment data, thereby ensuring the timeliness, freshness and diversity of the software automation test data.

[0102] In a specific embodiment of the present disclosure, step S4 further includes steps S8, S9, S10, S11 and S12.

[0103] Step S8: calling new test environment library table data from the software test environment library table data;

[0104] Step S9: input the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, wherein the third scenario data is test scenario data generated by combining the new test environment library table data;

[0105] Step S10: rematching the interface connecting the first processing module and the second processing module, and connecting to the second processing module interface matching the third scene data;

[0106] Step S11: loading the third scene data into a second automation script through the second processing module interface to obtain a second automation script loaded with the third scene data;

[0107] Step S12: input the second automation script into the third processing module for execution, obtain a new software automation test result, and store it.

[0108] It is understandable that the above steps are intended to ensure that automated data is no longer dead data, and there is no need to maintain a set of automated data every time a new environment is added. At the same time, the data loaded by the automated script is obtained through real-time or scheduled calculations every day, so the scenario data is different each time the automated script is run. This ensures the most important point of testing, the diversity of scenario data, and can also update scenario data according to the updated data of the environment, so as to promptly discover defects that may be caused by changes in the latest version.

[0109] Example 2

[0110] like Figure 2As shown, this embodiment provides a software automation testing device, which includes a first acquisition unit 701 , a first processing unit 702 , a second processing unit 703 and a third processing unit 704 .

[0111] The first acquisition unit 701 is used to acquire library table data of the software test environment to be tested;

[0112] A first processing unit 702 is configured to input the library table data into a first processing module for screening and filtering to obtain first scenario data. The first processing module is a data processing model that uses data cleaning to remove dirty data and non-business data. The first scenario data is test scenario data generated by combining the software test environment library table data.

[0113] The second processing unit 703 is configured to input the first scene data into a second processing module for loading, thereby obtaining an automation script loaded with the first scene data. The second processing module is a module including at least one automation script, and the second processing module is a module for loading scene data.

[0114] The third processing unit 704 is used to input the automation script into the third processing module for execution to obtain the software automation test result. The third processing module is a software automation test execution module, and the software automation test execution module is a module that controls the automation script to perform software automation testing.

[0115] In a specific embodiment of the present disclosure, the first acquiring unit 701 includes a first acquiring subunit 7011 , a first processing subunit 7012 , and a second processing subunit 7013 .

[0116] The first acquisition subunit 7011 is used to acquire software testing environment data;

[0117] The first processing sub-unit 7012 is used to classify the software test environment data to obtain system library table data under different environments;

[0118] The second processing sub-unit 7013 is used to match the system library table data in at least one software testing environment with the first processing module, determine the software testing environment library table data that needs to be tested, and call the software testing environment library table data that needs to be tested in real time.

[0119] In a specific embodiment of the present disclosure, the first processing unit 702 includes a third processing sub-unit 7021 , a second acquiring sub-unit 7022 and a fourth processing sub-unit 7023 .

[0120] The third processing sub-unit 7021 is used to extract, clean and integrate the software test environment library table data to be tested in real time to obtain processed environment data;

[0121] The second acquisition subunit 7022 is used to acquire generation rules of scene data and input them into the database for storage;

[0122] The fourth processing sub-unit 7023 is used to call the generation rule of the scene data to process the processed environmental data and generate the first scene data in real time.

[0123] In a specific embodiment of the present disclosure, the second processing unit 703 includes a fifth processing subunit 7031 , a first judgment subunit 7032 and a second judgment subunit 7033 .

[0124] The fifth processing sub-unit 7031 is configured to detect whether the interface of the second processing module is connected to the interface of the first processing module;

[0125] The first judgment subunit 7032 is configured to load the first scenario data into the automation script if the interface of the second processing module is connected to the interface of the first processing module, to obtain an automation script file loaded with the first scenario data;

[0126] The second judgment sub-unit 7033 is used to match and dock the interface of the second processing module with the interface of the first processing module if the interface of the second processing module has not been docked with the interface of the first processing module, and load the first scene data into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

[0127] In a specific implementation of the present disclosure, the device further includes a first judgment unit 705 , a second judgment unit 706 and a third judgment unit 707 .

[0128] A first judging unit 705 is configured to match the first scenario data with the current software test environment library table data to judge whether the first scenario data is scenario data generated from the current software test environment library table data;

[0129] The second judgment unit 706 is configured to send the first scenario data to the second processing module for loading if the first scenario data is scenario data generated from the current software test environment library table data;

[0130] The third judgment unit 707 is used to mark the first scenario data in red for storage if the first scenario data is not scenario data generated from the current software testing environment library table data, and generate second scenario data from the current software testing environment library table data.

[0131] In a specific embodiment of the present disclosure, the apparatus further includes a fourth processing unit 708 , a fifth processing unit 709 , a sixth processing unit 710 , a seventh processing unit 711 and an eighth processing unit 712 .

[0132] The fourth processing unit 708 is configured to call new test environment library table data from the software test environment library table data;

[0133] A fifth processing unit 709 is configured to input the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, where the third scenario data is test scenario data generated by combining the new test environment library table data.

[0134] A sixth processing unit 710 is configured to re-match the interface connecting the first processing module and the second processing module, and access the interface of the second processing module that matches the third scene data;

[0135] The seventh processing unit 711 is configured to load the third scenario data into a second automation script through the second processing module interface to obtain the second automation script loaded with the third scenario data;

[0136] The eighth processing unit 712 is configured to input the second automation script into the third processing module for execution, obtain a new software automation test result, and store the result.

[0137] It should be noted that, regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated on here.

[0138] Example 3

[0139] Corresponding to the above method embodiment, the embodiment of the present disclosure further provides a software automation testing device. The software automation testing device described below and the software automation testing method described above can be referenced to each other:

[0140] Figure 3 FIG. 8 is a block diagram of a software automation testing device 800 according to an exemplary embodiment. Figure 3As shown, the software automated testing device 800 may include: a processor 801 , a memory 802 , and may further include one or more of a multimedia component 803 , an input / output (I / O) interface 804 , and a communication component 805 .

[0141] The processor 801 is used to control the overall operation of the software automation test device 800 to complete all or part of the steps in the above-mentioned software automation test method. The memory 802 is used to store various types of data to support the operation of the software automation test device 800. For example, these data may include instructions for any application or method operating on the software automation test device 800, as well as application-related data, such as contact data, sent and received messages, pictures, audio, video, etc. The memory 802 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The multimedia component 803 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 802 or sent via the communication component 805. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 804 provides an interface between the processor 801 and other interface modules. The above-mentioned other interface modules may be a keyboard, a mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 805 is used for wired or wireless communication between the software automation test device 800 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more thereof, so the corresponding communication component 805 may include: a Wi-Fi module, a Bluetooth module, an NFC module.

[0142] In an exemplary embodiment, the software automation testing device 800 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above-mentioned software automation testing method.

[0143] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided. When executed by a processor, the program instructions implement the steps of the aforementioned software automated testing method. For example, the computer-readable storage medium may be the aforementioned memory 802 including the program instructions. The program instructions may be executed by the processor 801 of the software automated testing device 800 to perform the aforementioned software automated testing method.

[0144] Example 4

[0145] Corresponding to the above method embodiment, the embodiment of the present disclosure further provides a readable storage medium. The readable storage medium described below and the software automation testing method described above can refer to each other.

[0146] A readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the software automation testing method of the above method embodiment.

[0147] The readable storage medium may specifically be any readable storage medium that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0148] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

[0149] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A software automation testing method, characterized in that: include: Obtain the library table data of the software testing environment that needs to be tested; Inputting the library table data into a first processing module for screening and filtering to obtain first scenario data, wherein the first processing module is a data processing model that uses data cleaning to remove dirty data and uses data cleaning to remove non-business data, and the first scenario data is test scenario data generated by combining the software test environment library table data; Inputting the first scene data into a second processing module for loading to obtain an automation script loaded with the first scene data, wherein the second processing module is a module including at least one automation script, and the second processing module is a module for loading scene data; Input the automation script into a third processing module for execution to obtain a software automation test result. The third processing module is a software automation test execution module. The software automation test execution module is a module that controls the automation script to perform software automation testing; The step of obtaining the software test environment library table data to be tested includes: Obtain software testing environment data; Classifying the software testing environment data to obtain system library table data under different environments; Matching the system library table data in at least one software test environment with the first processing module, determining the software test environment library table data to be tested, and calling the software test environment library table data to be tested in real time; The step of inputting the software test environment library table data to be tested into the first processing module for screening and filtering to obtain the first scenario data includes: Extract, clean and integrate the software test environment database data to be tested in real time to obtain processed environment data; Obtain the generation rules of scene data and input them into the database for storage; The generated rule of the scene data is called to process the processed environmental data to generate the first scene data in real time.

2. The software automation testing method according to claim 1, characterized in that: The step of inputting the first scene data into the second processing module for loading to obtain an automation script file loaded with the first scene data includes: Detecting whether the interface of the second processing module is connected to the interface of the first processing module; If the interface of the second processing module is connected to the interface of the first processing module, the first scene data is loaded into the automation script to obtain an automation script file loaded with the first scene data; If the interface of the second processing module is not docked with the interface of the first processing module, the interface of the second processing module is matched and docked with the interface of the first processing module, and the first scene data is loaded into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

3. The software automation testing method according to claim 1, wherein: The step of inputting the first scene data into the second processing module for loading to obtain an automation script loaded with the first scene data further includes: Matching the first scenario data with the current software test environment library table data to determine whether the first scenario data is scenario data generated from the current software test environment library table data; If the first scenario data is scenario data generated from the current software test environment library table data, sending the first scenario data to the second processing module for loading; If the first scenario data is not scenario data generated from the current software test environment library table data, the first scenario data is marked in red for storage, and the current software test environment library table data is used to generate second scenario data.

4. The software automation testing method according to claim 1, wherein: The step of inputting the automation script file into a third processing module for execution to obtain a software automation test result further includes: Calling new test environment library table data from the software test environment library table data; Inputting the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, wherein the third scenario data is test scenario data generated by combining the new test environment library table data; Rematching the interface connecting the first processing module and the second processing module, and connecting to the second processing module interface matching the third scene data; Loading the third scene data into a second automation script through the second processing module interface to obtain a second automation script loaded with the third scene data; The second automation script is input into the third processing module for execution to obtain a new software automation test result, which is then stored.

5. A software automated testing device, characterized in that: include: A first acquisition unit is used to acquire library table data of a software test environment to be tested; a first processing unit, configured to input the library table data into a first processing module for screening and filtering to obtain first scenario data, wherein the first processing module is a data processing model that uses data cleaning to remove dirty data and uses data cleaning to remove non-business data, and the first scenario data is test scenario data generated by combining the software test environment library table data; a second processing unit, configured to input the first scene data into a second processing module for loading, thereby obtaining an automation script loaded with the first scene data, wherein the second processing module is a module including at least one automation script, and is a module for loading scene data; a third processing unit, configured to input the automation script into a third processing module for execution to obtain a software automation test result, wherein the third processing module is a software automation test execution module, and the software automation test execution module is a module for controlling the automation script to perform software automation testing; A first acquisition subunit is used to acquire software test environment data; A first processing subunit is used to classify the software test environment data to obtain system library table data under different environments; A second processing sub-unit is used to match the system library table data in at least one software test environment with the first processing module, determine the software test environment library table data that needs to be tested, and call the software test environment library table data that needs to be tested in real time; The third processing sub-unit is used to extract, clean and integrate the software test environment library table data to be tested in real time to obtain processed environment data; The second acquisition subunit is used to acquire generation rules of scene data and input them into the database for storage; The fourth processing sub-unit is used to call the generation rule of the scene data to process the processed environmental data and generate the first scene data in real time.

6. The software automation testing device according to claim 5, characterized in that: The device comprises: a fifth processing subunit, configured to detect whether the interface of the second processing module is connected to the interface of the first processing module; a first judgment subunit, configured to load the first scenario data into the automation script if the interface of the second processing module is connected to the interface of the first processing module, to obtain an automation script file loaded with the first scenario data; The second judgment sub-unit is used to match and dock the interface of the second processing module with the interface of the first processing module if the interface of the second processing module has not been docked with the interface of the first processing module, and load the first scene data into the automation script that matches the interface of the first processing module to obtain the automation script loaded with the first scene data.

7. The software automation testing device according to claim 5, characterized in that: The device further comprises: A first judging unit is configured to match the first scenario data with the current software test environment library table data to judge whether the first scenario data is scenario data generated from the current software test environment library table data; a second judgment unit, configured to send the first scenario data to the second processing module for loading if the first scenario data is scenario data generated from the current software test environment library table data; The third judgment unit is used to mark the first scenario data in red for storage if the first scenario data is not scenario data generated by the current software test environment library table data, and generate second scenario data from the current software test environment library table data.

8. The software automation testing device according to claim 5, characterized in that: The device further comprises: A fourth processing unit, configured to call new test environment library table data from the software test environment library table data; a fifth processing unit, configured to input the new test environment library table data into the first processing module for screening and filtering to obtain third scenario data, wherein the third scenario data is test scenario data generated by combining the new test environment library table data; a sixth processing unit, configured to re-match the interface connecting the first processing module and the second processing module, and access the interface of the second processing module matching the third scene data; a seventh processing unit, configured to load the third scenario data into a second automation script through the second processing module interface, to obtain the second automation script loaded with the third scenario data; The eighth processing unit is used to input the second automation script into the third processing module for execution, obtain a new software automation test result, and store it.

9. A software automated testing device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the software automation testing method according to any one of claims 1 to 4 when executing the computer program.

10. A readable storage medium, characterized in that: The readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the software automation testing method according to any one of claims 1 to 4.

Images