CN110851351A - Deployment environment testing method, apparatus, computer equipment and storage medium - Google Patents

Abstract

An embodiment of the present invention discloses a deployment environment testing method. The method includes: when the triggering of the test start event is monitored, obtaining an expected result file pointed to by the path information input in the interface, and the expected result file is obtained. The result file is the expected data of the database and/or the expected configuration of the deployment environment; pull the installed database data and/or the configured deployment environment configuration of the current deployment environment, and compare it with the expected result file; If they are the same, the test is passed; if the two data are different, record the abnormal field with the difference between the two data, and return the abnormal field to the input interface for display. The above solution realizes the test of system environment configuration and installed data in the deployment environment, and checks whether the environment of the deployment system is correct before the acceptance of the deployment software, so that some potential environment configuration risks can be eliminated in advance before the acceptance process, and the test efficiency be improved.

Description

Deployment environment testing method, apparatus, computer equipment and storage medium

technical field

The present invention relates to the field of system testing, and in particular, to a deployment environment testing method, device, computer equipment and storage medium.

Background technique

In a software development project, after each software version is handed over and deployed, due to the difference between the developer's system environment and the customer's deployment environment, some functional blocking problems or recession problems are not uncommon. The existing test method is single-step debugging test, which is to trace the process of program execution step by step, monitor the changes of variable values, and find the cause of the bug. However, in the single-step debugging test It does not include testing the system environment configuration of the deployment environment and the installed database. Therefore, the existing single-step debugging test results cannot reflect the correctness of the system environment configuration and installed database files. If the system environment is improperly configured or the database is installed In the case of garbled files, the deployed software cannot run normally. How to implement the system environment configuration in the deployment environment and test the correctness of the installed data files is an urgent problem to be solved.

SUMMARY OF THE INVENTION

In view of this, the purpose of the embodiments of the present invention is to provide a deployment environment testing method, device, computer equipment and storage medium, which realizes the testing of the system environment configuration and the installed data files in the deployment environment, and starts when the deployment software starts. Check whether the environment of the deployed system is correct before acceptance, so that some potential environment configuration risks and various abnormalities caused by garbled data in the database can be eliminated in advance before the acceptance process, and the test efficiency can be improved.

To achieve the above purpose, an embodiment of the present invention provides a deployment environment testing method, including the following steps:

Create an input interface, monitor the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected result file pointed to by the path information input in the interface. The result file is the expected data of the database and/or the expected configuration of the deployment environment;

Pull the installed database data and/or the configured deployment environment configuration of the current deployment environment, and compare it with the expected result file;

If the two data are the same, the test is passed; if the two data are different, the abnormal field with the difference between the two data is recorded, and the abnormal field is returned to the input interface for display.

Preferably, the step of pulling the installed database data and/or the configured deployment environment configuration data of the current deployment environment, and comparing the data with the expected result file, includes:

Parse the expected database data in the expected result file, record the field name and expected value of each form page of the expected database data as a key-value pair, and obtain a key-value pair set;

Traverse each key-value pair in the set, use each key in the key-value pair as a query field, and query the correctness of the value corresponding to each key in the installed database data of the deployment environment one by one. .

Preferably, the step of pulling the installed database data and/or the set deployment environment configuration data of the current deployment environment, and comparing the data with the expected result file, further includes:

Parse the expected configuration of the deployment environment in the expected result file, and use each parameter name and its corresponding parameter value in the expected configuration of the deployment environment as a parameter key-value pair to obtain a set of parameter key-value pairs;

Traverse the set of parameter key-value pairs, use the key of each key-value pair in the set as a query field, and query the correctness of the value corresponding to each key in the set deployment environment configuration parameters one by one.

Preferably, before the step of parsing the database expected data in the expected result file, recording the field name and expected value of each form page of the database expected data as a key-value pair, and obtaining a set of key-value pairs, Also includes:

Attempt to connect to the database installed in the current deployment environment. If the connection is successful, the data will be pulled. If the connection fails, an error message box will be displayed.

Preferably, if the two data are the same, the test will pass; if the two data are different, record the abnormal field with the difference between the two data, and return the abnormal field to the input interface for display After the steps, also include:

Copy the data content corresponding to the abnormal field in the expected result file, and perform overwriting processing on the abnormal field in the installed database data and/or the set deployment environment configuration data of the current deployment environment.

Preferably, by copying the data content corresponding to the abnormal field in the expected result file, the abnormal field in the installed database data and/or the set deployment environment configuration data of the current deployment environment The steps for overwriting processing are:

Copy the data content corresponding to the abnormal field in the expected result file, and allocate a new interval in the system memory for environment simulation;

Load an instance module including the data content in the simulation environment, and if the instance module runs normally, perform overwriting processing on the abnormal field in the to-be-verified file.

Preferably, in the process of recording the abnormal field, the corresponding index value is pulled and stored together, and the index value is used to quickly locate the abnormal field in its source text.

In order to achieve the above purpose, the embodiment of the present invention also provides a device for testing the deployment environment, including:

The interface module is used to create an input interface, monitor the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected result pointed to by the path information input in the interface file, the expected result file is the expected data of the database and/or the expected configuration of the deployment environment;

The test module is used to pull the installed database data and/or the set deployment environment configuration of the current deployment environment, and compare it with the expected result file; if the data of the two are the same, the test passes; If the data are not the same, record the abnormal fields with differences between the two data, and return the abnormal fields to the input interface for display.

To achieve the above object, an embodiment of the present invention also provides a computer device, the computer device includes a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that: The computer program, when executed by a processor, implements the steps of testing a deployment environment as claimed in any one of claims 1 to 7.

To achieve the above object, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program can be executed by at least one processor, so that the at least one A processor performs the steps of testing the deployment environment as claimed in any one of claims 1 to 7.

Compared with the prior art, the deployment environment testing method, device, computer equipment, and computer-readable storage medium proposed in the embodiments of the present invention realize the testing of the system environment configuration and the installed data files in the deployment environment, and are Check whether the environment of the deployment system is correct before the acceptance of the deployment software, so that some potential environment configuration risks and various abnormalities caused by garbled data in the database can be eliminated in advance before the acceptance process, and the test efficiency can be improved.

Description of drawings

Fig. 1 is the step flow chart of the deployment environment testing method of the present invention;

2 is a schematic flowchart of step S200 in Embodiment 1 of the deployment environment testing method of the present invention;

3 is a schematic flowchart of another embodiment of step S200 in Embodiment 1 of the deployment environment testing method of the present invention;

FIG. 4 is a schematic flowchart after step S300 in Embodiment 1 of the deployment environment testing method of the present invention;

FIG. 5 is a schematic diagram of a program module of Embodiment 2 of a deployment environment testing apparatus according to the present invention;

FIG. 6 is a schematic diagram of a hardware structure of Embodiment 3 of a computer device according to the present invention.

Detailed ways

In order to better understand the technical solutions of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

It should be understood that the described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. As used in the embodiments of the present invention and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

It should be understood that the term "and/or" used in this document is only an association relationship to describe the associated objects, indicating that there may be three kinds of relationships, for example, A and/or B, which may indicate that A exists alone, and A and B exist at the same time. B, there are three cases of B alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be understood that although the terms first, second, etc. may be used to describe the designated keywords in the embodiments of the present invention, the designated keywords should not be limited to these terms. These terms are only used to distinguish specific keywords from one another. For example, without departing from the scope of the embodiments of the present invention, the first specified keyword may also be referred to as the second specified keyword, and similarly, the second specified keyword may also be referred to as the first specified keyword.

Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "corresponding to determining" or "responsive to detecting". Similarly, the phrases "if determined" or "if detected (stated condition or time)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)," depending on the context )" or "in response to detection (a stated condition or event)".

Example 1

Referring to FIG. 1 , it is a flowchart of steps for testing a deployment environment provided by an embodiment of the present invention. It can be understood that, the flowchart in the embodiment of the present invention does not limit the order of executing steps. details as follows:

Step S100 creates an input interface, monitors the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected result file pointed to by the path information input in the interface, so The expected result file described above is the expected data of the database and/or the expected configuration of the deployment environment.

Creating an input interface to allow technicians to perform related operations is the first step of the present invention to realize the technical solution.

Specifically, the processing unit creates a thread to run the pre-edited form program. After the program runs, a form frame will pop up on the system desktop, wherein the form frame includes at least two text input boxes and a trigger button, the text input box is used for the technician to input the preparation document path and other verification data path information, and the trigger button is used to monitor the trigger operation of the technician to perform the deployment environment test.

Among them, the preparation file can also be called the expected result file, which is used as the benchmark file for the subsequent comparison test. It is preset by the technician. The expected file path entered in the text input box, the file data pointed to by the pull path, if it is in the local disk of the hardware device, the path can be "C: \\windows\\setup.ins " for example, if all The expected result file described above is in the external device, taking the U disk of sandisk brand as an example, its path can be G:sandisk: \\setup.ins ,

Expected result files include two types, one is database expected data, because under different system environments, some database data will be garbled or formatted when deployed from the developer's development environment to the client's hardware device, resulting in Data is lost or changed, which makes the deployed software unable to run normally. Therefore, technicians are required to prepare the correct expected database data in advance to conduct a comparative test on the database data in the current deployment environment, so as to know whether the database data in the current deployment environment is correct. Unusual problems such as data loss or change occur. For example, technicians compile programs under the condition that JAVA simulates the Android development environment on the computer PC side, and the customer's demand is that the software can run normally on the mobile phone side. Although the operating systems of both are Android systems, due to the The hardware devices of the mobile phones are different, and the versions of the two Android systems may also be inconsistent. There are natural differences. When the software is transferred from the technician's computer to the mobile phone, the database data transferred together is deformed and the environment configuration exists. Differences, deploying software will naturally have some functional blocking problems or regression problems.

The other type is the expected configuration of the deployment environment. General software has its own minimum requirements for hardware devices and software environments. For example, software that only supports 64-bit Windows systems cannot run normally in 32-bit Windows systems. Therefore, It is also necessary for technicians to pre-write the expected configuration file of the deployment environment, which is used to compare and test the set deployment environment configuration data, and then judge whether the currently set deployment environment configuration data satisfies the operation of the deployment software.

Exemplarily, the expected configuration data of the deployment environment can be as follows in Table 1:

Table 1

When monitoring the verification start event triggered by the trigger button in the interface, the processing unit obtains the relevant information of the expected result file pointed to by the input path of the input box, and then calls the expected result file pointed to by the path, and loads it into the cache , which can be called at any time for subsequent inspection steps.

Step S200 pulls the installed database data and/or the set deployment environment configuration of the current deployment environment, and compares it with the expected result file; if the two data are the same, the test passes; if the two data are not the same , record the abnormal field with difference between the two data, and return the abnormal field to the input interface for display.

After obtaining the expected file, pull the installed database data in the current deployment environment and/or pull the currently set deployment environment configuration, and perform a comparative test with the expected result file.

Specifically, the window in the aforementioned step S100 is also set with two check boxes, which correspond to the triggering of the database test and the deployment environment configuration test respectively. If the technician only checks the check box corresponding to the database test, then only the Pulls the installed database data of the current deployment environment, does not pull the configuration data of the deployment environment, and does not test the configuration data of the deployment environment. The check box is checked to trigger the corresponding test content.

Simply put, the deployment environment is the platform on which the software runs, that is, a collection of four elements: software environment, hardware, network, and data. The software environment refers to the operating system, database, and other application software when the software under test is running. The environment is relatively complex, and there are many factors that need to be considered, such as the language and version of the operating system, the version and number of coexisting software, and so on.

Taking database testing as an example, the technician presets the installed database path of the deployment environment. Usually, the installed database includes the database data supporting the deployment environment system itself and the self-contained database required for deploying the software. Usually, the paths of the two databases are fixed, and the database data supporting the deployment environment system itself is usually set in the local disk, such as disk C, and the self-contained database required for the deployment software is usually placed and generated by the installation file Under the installation folder, the path is also fixed, for example: C:\\Ping An Financial Internal Client \\mysql .

The processing unit accesses the two databases through the path preset by the technician, pulls the data in them, and compares the pulled data with the expected result file for specific data to obtain the test results.

After the comparison test is completed, the preset selection structure statement is used to output the test results. One is the test passed, and the other is the test failed. The evaluation criteria are the database data of the pulled deployment environment and/or the configuration of the deployment environment. Whether the data of the two expected result files are the same, if they are the same, the test is passed; if they are different, the record of the abnormal field with the difference between the two data is performed, and the return value of the abnormal field is input into the interface for display.

Among them, the abnormal field is obtained by the comparison test. If the database comparison test is used alone, the abnormal field is the field that is different from the database data installed in the current deployment environment and the expected result file data. For example For example, the installed database data contains table A, whose first row of data is "lender; Zhang San; loan amount three million", while the database expected data in the expected result file contains expected table A, the first row of expected table A data If it is "Lender; Zhang San; Loan Amount 2 million", it is regarded as the tested party - the field "loan amount 3 million" in the installed database data of the deployment environment is an abnormal field.

The above description is only an understanding of the exception field, which is intended to represent the difference data between the measured data and the expected data, and the exception field may also be some function instances, codes, arrays, classes, and so on.

Compared with the prior art, the method for testing the deployment environment provided by the present invention realizes the test of the system environment configuration and the installed data files in the deployment environment, and detects whether the environment of the deployment system is correct before the deployment software starts acceptance. , so that some potential environment configuration risks and various anomalies caused by garbled data in the database can be eliminated in advance before the acceptance process, and the test efficiency can be improved.

Exemplarily, referring to FIG. 2 , step S200 may further include:

S210 parses the database expected data in the expected result file, records the field name and expected value of each form page of the database expected data as a key-value pair, and obtains a key-value pair set.

Specifically, the expected data of the database is written in the format of excel, and the processing unit parses the expected data of the database, and records the field name and expected field value in each form page in the file as a key value to the collection , where the field name is key and the expected field value is numeric.

Exemplarily, the expected data of the database includes two forms, and the names of the two forms are "A" and "B", which correspond to database A and database B respectively, and each form records the stored data in the corresponding database. The processing unit parses in the order of the form pages, first parses the form "A", and stores the field names and corresponding field values in the form "A" as a set of key-value pairs using the map object function, as follows:

map.put("Loan Amount", "Three Million")

Among them, "loan amount" is the key, and "three million" is the value, meaning that the loan amount is three million.

map.put("Lender", "Zhangsan")

Among them, "lender" is the key, and "Zhang San" is the value, which means that the lender is Zhang San.

S220 traverses each key-value pair in the set, uses each key in the key-value pair as a query field, and queries the correctness of the value corresponding to each key in the installed database data of the deployment environment one by one.

The processing unit obtains each set of key-value pairs recorded in the preceding steps, extracts the key in the set, uses it as a query field, searches for the value corresponding to the key in the installed database data file of the deployment environment, and matches the The values in the expected result file are compared to analyze their correctness.

Exemplarily, a key-value pair in the expected result file is ("lender", "Zhangsan"), and the key "lender" is not used for query fields, and each form field in the installed database data of the deployment environment. Traverse through the name, and obtain the field value corresponding to the "lender" field name "Li Si". At this time, "Zhang San" is not equal to "Li Si", then the key value of the database data installed in the deployment environment The pair is incorrect, the data corresponding to the key-value pair is distorted.

In addition, while recording the incorrect field value and corresponding name, the location of the field can also be obtained, and an index record is added to allow technicians to quickly locate it in the original database.

Optionally, referring to FIG. 3 , step S200 further includes:

S240 parses the expected configuration of the deployment environment in the expected result file, takes each parameter name and its corresponding parameter value in the expected configuration of the deployment environment as a parameter key-value pair, and obtains a set of parameter key-value pairs;

S250 traverses the set of parameter key-value pairs, uses the key of each key-value pair in the set as a query field, and queries the correctness of the values corresponding to each key in the set deployment environment configuration parameters one by one.

Specifically, it has been explained in the foregoing content that the provided form is provided with a check box, and in terms of only checking the deployment environment configuration test, the processing unit enters the comparison test step of the deployment environment configuration. For the comparison test of the configuration file, obtain the expected configuration of the deployment environment pointed to by the specified path entered in the input interface, parse its specific parameter name and parameter value, define it as a MAP object, and then pull the set deployment environment configuration. Pulling the set environment configuration is the prior art. The present invention will not go into details on how to pull the configuration parameters. The pulled data may be scattered. At this time, the scattered data is sorted out, and the following table can be generated:

configuration item Existing configuration CPU 2.4GHZ Memory 256M hard disk Above 10G network card 10/100M

Table 2

Comparing Table 2 with Table 1 (expected configuration of deployment environment), it can be found that the parameter value of "CPU" in the configured deployment environment configuration is 2.4GHZ, which is inconsistent with the expected file, so "CPU; 2.4GHZ" is an abnormal field .

Optionally, before step S210, it further includes:

Step 210A performs a connection attempt on the database address. If the connection is successful, the database data installed in the deployment environment is pulled. If the connection fails, an error prompt box is displayed.

For the pull and subsequent comparison test of the installed database data in the current deployment environment, firstly, a connection attempt should be made to the installed database address. If it fails, the program will be stopped and an error prompt will be displayed. If successful, the next step will be triggered and the database will be expected. Parsing of the resulting file.

Optionally, referring to FIG. 4 , after step S300, it further includes:

Step 400 replicates the data content corresponding to the abnormal field in the expected result file, and performs overwriting processing on the abnormal field in the installed database file.

Optionally, step 400 includes:

Step 410 copies the data content corresponding to the exception field in the expected result file, and allocates a new interval in the system memory for environment simulation.

Step 420 loads an instance module including the data content in the simulation environment, and if the instance module runs normally, overwrite processing is performed on the abnormal field in the installed database file.

Specifically, after the field value verification is performed, the processing unit records and caches each abnormal field, and after the verification is completed, writes all the abnormal fields into a notepad for display. In addition, the index page number of the abnormal field can also be written into the notepad to facilitate the positioning of the technician.

In addition, the abnormal field is also displayed through a certain text box in the window in step S100, which is not limited in the present invention.

Exemplarily, the output result of the exception field can be as follows:

Database installed database expected file correctness index "system" = "win7" "system" = "win10" error 36 pages "paper"="4*3" "system" = "4*5" error 37 pages "color"="0,10,0" "color" = "50,0,100" error 221 pages

Embodiment 2

Referring to FIG. 5, a schematic diagram of the deployment environment test module of the present invention is shown. In this embodiment, the deployment environment testing apparatus 20 may include or be divided into one or more program modules, and the one or more program modules are stored in a storage medium and executed by one or more processors to complete The present invention can realize the above-mentioned testing method based on deployment environment. The program modules referred to in the embodiments of the present invention refer to a series of computer program instruction segments capable of completing specific functions, and are more suitable for describing the execution process of the deployment environment testing device 20 in the storage medium than the program itself. The following description will specifically introduce the functions of each program module in this embodiment:

The interface module 200 is used to create an input interface, monitor the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected direction pointed to by the path information input in the interface A result file, the expected result file is the expected data of the database and/or the expected configuration of the deployment environment;

The test module 300 is used to pull the installed database data and/or the set deployment environment configuration of the current deployment environment, and compare it with the expected result file; if the two data are the same, the test passes; If the data of the user is different, record the abnormal field with the difference between the two data, and return the abnormal field to the input interface for display.

Embodiment 3

Referring to FIG. 6 , it is a schematic diagram of a hardware architecture of a computer device according to Embodiment 3 of the present invention. In this embodiment, the computer device 2 is a device that can automatically perform numerical calculation and/or information processing according to pre-set or stored instructions. The computer equipment 2 may be a rack-type server, a blade-type server, a tower-type server or a cabinet-type server (including an independent server, or a server cluster composed of multiple servers) and the like. As shown in the figure, the computer equipment 2 at least includes, but is not limited to, a memory 21 , a processor 22 , a network interface 23 , and a deployment environment testing device 20 that can communicate with each other through a system bus. in:

In this embodiment, the memory 21 includes at least one type of computer-readable storage medium, and the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a random access memory ( RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disks, optical disks, and the like. In some embodiments, the memory 21 may be an internal storage unit of the computer device 2 , such as a hard disk or a memory of the computer device 2 . In other embodiments, the memory 21 may also be an external storage device of the computer device 2, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Of course, the memory 21 may also include both the internal storage unit of the computer device 2 and its external storage device. In this embodiment, the memory 21 is generally used to store the operating system and various application software installed in the computer device 2 , such as the program code of the deployment environment testing apparatus 20 in the second embodiment. In addition, the memory 21 can also be used to temporarily store various types of data that have been output or will be output.

In some embodiments, the processor 22 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 22 is typically used to control the overall operation of the computer device 2 . In this embodiment, the processor 22 is configured to run the program code or process data stored in the memory 21, for example, run the deployment environment testing apparatus 20, so as to implement the deployment environment testing method of the first embodiment.

The network interface 23 may include a wireless network interface or a wired network interface, and the network interface 23 is generally used to establish a communication connection between the computer equipment 2 and other electronic devices. For example, the network interface 23 is used to connect the computer device 2 with an external terminal through a network, and establish a data transmission channel and a communication connection between the computer device 2 and the external terminal. The network may be an intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network , Bluetooth (Bluetooth), Wi-Fi and other wireless or wired networks.

In this embodiment, the deployment environment testing device 20 stored in the memory 21 may also be divided into one or more program modules, and the one or more program modules are stored in the memory 21 and are composed of one or more program modules. The processor (the processor 22 in this embodiment) executes to complete the present invention.

For example, FIG. 5 shows a schematic diagram of program modules for implementing the second embodiment of the deployment environment testing apparatus 20. In this embodiment, the deployment environment testing apparatus 20 may be divided into an interface module 200 and a testing module 300, where this The program modules referred to in the invention refer to a series of computer program instruction segments capable of performing specific functions, and are more suitable for describing the execution process of the deployment environment testing device 20 in the computer equipment 2 than programs. The specific functions of the program modules have been described in detail in the second embodiment, and are not repeated here.

Embodiment 4

This embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), only Read-only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Programmable Read-Only Memory (PROM), magnetic memory, magnetic disk, optical disk, server, App application mall, etc., on which computer programs are stored, When the program is executed by the processor, the corresponding function is realized. The computer-readable storage medium of this embodiment is used to store the deployment environment testing apparatus 20, and when executed by the processor, implements the deployment environment testing method of the first embodiment.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.

The above are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied in other related technical fields , are similarly included in the scope of patent protection of the present invention.

Claims (10)

1. a deployment environment testing method, is characterized in that, comprises: Create an input interface, monitor the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected result file pointed to by the path information input in the interface. The result file is the expected data of the database and/or the expected configuration of the deployment environment; Pull the installed database data and/or the configured deployment environment configuration of the current deployment environment, and compare it with the expected result file; If the two data are the same, the test is passed; if the two data are different, the abnormal field with the difference between the two data is recorded, and the abnormal field is returned to the input interface for display. 2. The deployment environment testing method according to claim 1, characterized in that, said pulling the installed database data of the current deployment environment and/or the already set deployment environment configuration data, and carrying it out with the expected result file. The steps of the comparative test include: Parse the expected database data in the expected result file, record the field name and expected value of each form page of the expected database data as a key-value pair, and obtain a key-value pair set; Traverse each key-value pair in the set, use each key in the key-value pair as a query field, and query the correctness of the value corresponding to each key in the installed database data of the deployment environment one by one. 3. The deployment environment testing method according to claim 1, characterized in that, said pulling the installed database data of the current deployment environment and/or the set deployment environment configuration data, and carrying it out with the expected result file. The steps of the comparison test also include: Parse the expected configuration of the deployment environment in the expected result file, and use each parameter name and its corresponding parameter value in the expected configuration of the deployment environment as a parameter key-value pair to obtain a set of parameter key-value pairs; Traverse the set of parameter key-value pairs, use the key of each key-value pair in the set as a query field, and query the correctness of the value corresponding to each key in the set deployment environment configuration parameters one by one. 4. The deployment environment testing method according to claim 2, wherein, by parsing the expected database data in the expected result file, the field name and expected value of each form page of the database expected data are recorded For a key-value pair, before the step of obtaining the set of key-value pairs, it also includes: Attempt to connect to the database installed in the current deployment environment. If the connection is successful, the data will be pulled. If the connection fails, an error message box will be displayed. 5. The deployment environment testing method according to claim 1, wherein, if the two data are the same, the test is passed; if the two data are not the same, record the abnormal field with difference between the two data. , and after the step of returning the abnormal field to the input interface for display, the method further includes: Copy the data content corresponding to the abnormal field in the expected result file, and perform overwriting processing on the abnormal field in the installed database data and/or the set deployment environment configuration data of the current deployment environment. 6. The deployment environment testing method according to claim 5, wherein, the data content corresponding to the abnormal field in the expected result file is copied, and the installed database data and the current deployment environment are compared. /Or the steps for overwriting the exception field in the set deployment environment configuration data are: Copy the data content corresponding to the abnormal field in the expected result file, and allocate a new interval in the system memory for environment simulation; Load an instance module containing the data content in the simulation environment, and if the instance module runs normally, perform overwriting processing on the exception field. 7. The deployment environment testing method according to claim 1, characterized in that, in the process of recording the abnormal field, the corresponding index value is pulled and stored together, and the index value is used to complete the Quickly locate the exception field in its source text. 8. An apparatus for deployment environment testing, wherein the apparatus comprises: The interface module is used to create an input interface, monitor the test start event triggered in the interface, and when the trigger of the test start event is monitored, obtain the expected result pointed to by the path information input in the interface file, the expected result file is the expected data of the database and/or the expected configuration of the deployment environment; The test module is used to pull the installed database data and/or the set deployment environment configuration of the current deployment environment, and compare it with the expected result file; if the data of the two are the same, the test passes; If the data are not the same, record the abnormal fields with differences between the two data, and return the abnormal fields to the input interface for display. 9. A computer device comprising a memory, a processor and a computer program stored on the memory and running on the processor, wherein the computer program is implemented when the processor is executed The steps of the deployment environment testing method according to any one of claims 1 to 7. 10. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and the computer program can be executed by at least one processor, so that the at least one processor executes the The step of testing the deployment environment according to any one of claims 1 to 7.

Images