CN112711538B

CN112711538B - Test system simulation method, device, computer equipment and storage medium

Info

Publication number: CN112711538B
Application number: CN202011627382.2A
Authority: CN
Inventors: 钟世亮; 陈仲伟; 杨子豪
Original assignee: China Merchants Finance Technology Co Ltd
Current assignee: China Merchants Finance Technology Co Ltd
Priority date: 2020-12-30
Filing date: 2020-12-30
Publication date: 2024-03-19
Anticipated expiration: 2040-12-30
Also published as: CN112711538A

Abstract

The invention discloses a test system simulation method, a test system simulation device, computer equipment and a storage medium, which comprise the steps of obtaining a system simulation request, wherein the system simulation request comprises system creation parameters; based on the system creation parameters, creating an empty test system corresponding to the system creation parameters, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identifier; forming a data acquisition request based on the original system identifier, and acquiring system simulation parameters corresponding to the original system identifier based on the data acquisition request; loading the system simulation parameters into the original simulation system to obtain the target simulation system. According to the technical scheme, potential safety hazards to the target system are avoided, and the safety of the target system is improved.

Description

Test system simulation method, device, computer equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a test system simulation method, a test system simulation device, a computer device, and a storage medium.

Background

When a tester needs to test a target system (i.e., a software system that needs to be tested), it often involves the situation that the target system needs to call a third party simulation system interface. In the prior art, when a tester calls a third-party simulation system interface to test a target system, the following test mode is generally adopted: 1. the wall is opened from the target system to the third party simulation system, and if callback of the interface of the third party simulation system is involved, the wall is opened from the third party simulation system to the target system; 2. and completely copying the third-party simulation system beside the target system, and calling a third-party simulation system interface by constructing a third-party simulation system copy. However, the above test method has the following problems: 1. the security policy of the target system is limited, and the situation that the target system directly opens the wall to the third-party simulation system is not allowed exists; 2. the third-party simulation system is likely to be stained with data and the like, and potential safety hazards are caused to the third-party simulation system; 3. the construction of third party simulation system copies requires significant manpower and material resources.

Disclosure of Invention

The embodiment of the invention provides a test system simulation method, a test system simulation device, computer equipment and a storage medium, which are used for solving the problem of potential complete hazards of the existing third-party simulation system.

A test system simulation method comprising the steps of:

acquiring a system simulation request, wherein the system simulation request comprises system creation parameters;

creating an empty test system corresponding to the system creation parameter based on the system creation parameter, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identifier;

forming a data acquisition request based on the original system identifier, and acquiring a system simulation parameter corresponding to the original system identifier based on the data acquisition request;

and loading the system simulation parameters into the original simulation system to obtain a target simulation system.

Further, the forming a data acquisition request based on the original system identifier, and acquiring the system simulation parameters corresponding to the original system identifier based on the data acquisition request, including:

forming a first data acquisition request based on the original system identifier, wherein the first data acquisition request comprises the original system identifier and at least one target interface field;

Displaying an interface editing page based on the data acquisition request;

acquiring a target interface value corresponding to at least one target interface field from the interface editing page;

and determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identification.

forming a second data acquisition request based on the original system identification, wherein the second data acquisition request comprises a target database address;

acquiring a target interface information table from a target database based on the target database address;

acquiring at least one target interface field and a target interface value corresponding to the at least one target interface field from the target interface information table;

Forming a third data acquisition request based on the original system identifier, wherein the third data acquisition request comprises a target system identifier;

inquiring a system database based on the target system identifier, and judging whether historical test data corresponding to the target system identifier exists or not;

if historical test data corresponding to the target system identification exists, determining the historical test data as system simulation parameters corresponding to the original system identification;

and if the historical test data corresponding to the target system identifier does not exist, acquiring the target test data corresponding to the target system identifier by adopting preset test data acquisition logic based on the target system identifier, and determining the target test data as the system simulation parameter corresponding to the original system identifier.

Further, the acquiring, by using preset test data acquiring logic, target test data corresponding to the target system identifier, and determining the target test data as a system simulation parameter corresponding to the original system identifier, includes:

testing the target system corresponding to the target system identifier, and acquiring interface interaction data between the test system and the target system in real time;

Analyzing the interface interaction data to obtain interface analysis data;

and encrypting the interface analysis data to obtain target test data, and determining the target test data as system simulation parameters corresponding to the original system identification.

Further, the interface analysis data comprises at least one target interface field and a target interface value corresponding to the target interface field; encrypting the interface analysis data to obtain target test data, and determining the target test data as a system simulation parameter corresponding to the original system identifier, wherein the method comprises the following steps:

acquiring an interface field type corresponding to each target interface field;

if the interface field type is a sensitive field type, performing desensitization processing on a target interface value corresponding to the sensitive field type to obtain a desensitized interface value, and encrypting the desensitized interface value to obtain first encrypted data;

if the interface field type is a non-sensitive field type, encrypting a target interface value corresponding to the non-sensitive field type to obtain second encrypted data;

and acquiring target test data based on the first encrypted data and the second encrypted data, and determining the target test data as a system simulation parameter corresponding to the original system identifier.

Further, the loading the system simulation parameters into the original simulation system to obtain a target simulation system includes:

performing interface association identification on the system simulation parameters to obtain an association interface field and an association interface value;

and carrying out key value association on the association interface field and the association interface value to obtain association interface data, loading the association interface data into the original simulation system, and obtaining a target simulation system.

A test system simulation apparatus, comprising:

the system comprises a request acquisition module, a system simulation module and a system simulation module, wherein the request acquisition module is used for acquiring a system simulation request, and the system simulation request comprises system creation parameters;

the system creation module is used for creating an empty test system corresponding to the system creation parameter based on the system creation parameter, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identifier;

the parameter acquisition module is used for forming a data acquisition request based on the original system identifier and acquiring system simulation parameters corresponding to the original system identifier based on the data acquisition request;

and the parameter loading module is used for loading the system simulation parameters into the original simulation system and obtaining a target simulation system.

Further, the parameter obtaining module includes:

a first request sub-module, configured to form a first data acquisition request based on the original system identifier, where the first data acquisition request includes the original system identifier and at least one target interface field;

the page display sub-module is used for displaying an interface editing page based on the data acquisition request;

the first interface acquisition sub-module is used for acquiring at least one target interface value corresponding to the target interface field from the interface editing page;

and the first parameter determination submodule is used for determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier.

Further, the parameter obtaining module includes:

a second request sub-module, configured to form a second data acquisition request based on the original system identifier, where the second data acquisition request includes a target database address;

the information table acquisition sub-module is used for acquiring a target interface information table from a target database based on the target database address;

a second interface obtaining sub-module, configured to obtain at least one target interface field and a target interface value corresponding to at least one target interface field from the target interface information table;

And the second parameter determination submodule is used for determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier.

Further, the parameter obtaining module includes:

a third request sub-module, configured to form a third data acquisition request based on the original system identifier, where the third data acquisition request includes a target system identifier;

the data judging sub-module is used for inquiring a system database based on the target system identifier and judging whether historical test data corresponding to the target system identifier exists or not;

a third parameter determining sub-module, configured to determine, if there is historical test data corresponding to the target system identifier, the historical test data as a system simulation parameter corresponding to the original system identifier;

and the fourth parameter determination submodule is used for acquiring target test data corresponding to the target system identifier by adopting preset test data acquisition logic based on the target system identifier if the historical test data corresponding to the target system identifier does not exist, and determining the target test data as the system simulation parameter corresponding to the original system identifier.

Further, the fourth parameter determination submodule includes:

the interactive data unit is used for testing the target system corresponding to the target system identifier and acquiring interface interactive data between the test system and the target system in real time;

the analysis data unit is used for analyzing the interface interaction data to obtain interface analysis data;

and the encryption processing unit is used for carrying out encryption processing on the interface analysis data to obtain target test data, and determining the target test data as system simulation parameters corresponding to the original system identification.

Further, the encryption processing unit includes:

a field type subunit, configured to obtain an interface field type corresponding to each of the target interface fields;

the desensitization processing subunit is used for carrying out desensitization processing on a target interface value corresponding to the sensitive field type if the interface field type is the sensitive field type, obtaining a desensitized interface value, encrypting the desensitized interface value and obtaining first encrypted data;

the first encryption subunit is configured to encrypt a target interface value corresponding to a non-sensitive field type if the interface field type is the non-sensitive field type, and obtain second encrypted data;

And the second encryption subunit is used for acquiring target test data based on the first encryption data and the second encryption data, and determining the target test data as a system simulation parameter corresponding to the original system identifier.

Further, the parameter loading module includes:

the association identification sub-module is used for carrying out interface association identification on the system simulation parameters and obtaining an association interface field and an association interface value;

and the key value association sub-module is used for carrying out key value association on the association interface field and the association interface value to obtain association interface data, loading the association interface data into the original simulation system and obtaining a target simulation system.

A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the test system simulation method described above when executing the computer program.

A computer readable storage medium storing a computer program which when executed by a processor implements the test system simulation method described above.

According to the test system simulation method, the device, the computer equipment and the storage medium, the server acquires the system simulation request, the system simulation request comprises the system creation parameters, the empty test system corresponding to the system creation parameters is created based on the system creation parameters, the empty test system is determined to be an original simulation system, the original simulation system comprises an original system identifier, the original simulation system is replaced by the original simulation system after the wall is opened in the target system, potential safety hazards to the target system are avoided, and the safety of the target system is improved; forming a data acquisition request based on the original system identifier, acquiring system simulation parameters corresponding to the original system identifier based on the data acquisition request, avoiding causing stain data to the original simulation system, and improving the safety and reliability of the original simulation system; loading the system simulation parameters into the original simulation system to obtain the target simulation system, so that the server can normally call the target simulation system under any condition, and the reliability of the simulation system is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 2 is another flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 3 is another flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 4 is another flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 5 is another flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 6 is another flow chart of a test system simulation method in accordance with an embodiment of the present invention;

FIG. 7 is another flow chart of a test system simulation method according to an embodiment of the invention;

FIG. 8 is a schematic diagram of an application environment of a test system simulation method according to an embodiment of the invention;

FIG. 9 is a schematic diagram of a test system simulator according to an embodiment of the invention;

FIG. 10 is a schematic diagram of a computer device in accordance with an embodiment of the invention.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The test system simulation method provided by the embodiment of the invention can be applied to an application environment shown in fig. 8. Specifically, the test system simulation method is applied to a test system simulation system, the test system simulation system comprises a client and a server as shown in fig. 8, and the client and the server are communicated through a network and are used for realizing test system simulation. The client is also called a client, and refers to a program corresponding to the server for providing local service for the client. The client may be installed on, but is not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 1, a test system simulation method is provided, and the method is applied to the server in fig. 8 for illustration, and includes the following steps:

s11: a system simulation request is obtained, the system simulation request including system creation parameters.

The system simulation request is a request for creating a simulation system corresponding to the target system. The target system is the system that needs to be tested. For example, the target system may be a real service system, and in order to improve reliability and stability of the service system, the service system needs to be tested. The system creation parameters are parameters corresponding to the target system and are used for creating a simulation system corresponding to the target system. For example, system creation parameters include, but are not limited to, target system name and target system address, etc. Illustratively, the target system name may be api. The target system address may be url: api.

As an example, the server obtains a system simulation request, which includes a target system name api.abc and a target system address url: api.abc.com, so that in the subsequent steps the target system name api.abc and the target system address url: and (3) api.abc.com, and creating a simulation system corresponding to the target system.

S12: based on the system creation parameters, creating an empty test system corresponding to the system creation parameters, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identification.

Wherein the empty test system is a system comprising only the target system name and the target system address. The original simulation system is a simulation system determined from the empty test system. The original system identifier is an identifier corresponding to the original simulation system.

As an example, the server creates an empty test system corresponding to the system creation parameter based on the system creation parameter, e.g., the server is based on the target system name api. Abc and the target system address url: api.abc.com, creates a target system name api.abc and a target system address url: and determining the empty test system corresponding to the api.abc.com as an original simulation system, and determining the target system name api.abc as an original system identification. In this way, the server may pass the target system name api. Abc and the target system address url: determining an access address api.abc.simu.cmft.com of the original simulation system, and accessing the original simulation system; or the original simulation system access address api.abc.com is determined by binding host to the original simulation system, and the original simulation system is directly accessed by the original simulation system access address api.abc.com. It should be noted that, when the server accesses the original simulation system and adopts the original simulation system to test the target system, the server does not need to test the target system by opening a wall to the target system, thereby improving the safety of the target system. It can be understood that the server creates an empty test system corresponding to the system creation parameter based on the system creation parameter, determines the empty test system as an original simulation system, replaces the original simulation system from the wall opening in the target system, avoids potential safety hazards to the target system, and improves the safety of the target system.

S13: forming a data acquisition request based on the original system identifier, and acquiring the system simulation parameters corresponding to the original system identifier based on the data acquisition request.

The data acquisition request is a request formed based on the original system identifier and is used for acquiring the system simulation parameters corresponding to the original system identifier. The system simulation parameters are parameters acquired based on the data acquisition request. For example, system simulation parameters include, but are not limited to, a target interface field and a target interface value. The target interface field is a field in the interface call parameters. For example, the target interface fields include, but are not limited to, interface request methods, interface request addresses, interface input parameters, call return values, call return states, and the like. As an example, the interface request method is a method of requesting an application service of the target system. For example, the interface request method includes, but is not limited to, one of GET, POST, PUT and DELETE, etc. The interface request address is an address corresponding to the target system address. For example, http:// xxx.com/api/v1/user, the data format is a string. The interface input parameters are parameters input to the application service of the target system. For example, the interface input parameter may be a request payload, and the data format is a string. For example, the target interface values include, but are not limited to, call return values, call return states, and the like. The call returns a value that the application service of the target system returns based on the system test request. For example, the call return value may specifically be response, and the data format is a character string. The call return state is the state in which the application service of the target system returns the call return value. For example, the call return state may specifically be status. The target interface value is the value in the call return data corresponding to the target interface field.

Specifically, the server acquires the target interface field and the target interface value corresponding to the target interface field based on the data acquisition request, and determines the target interface value corresponding to the target interface field as the system simulation parameter corresponding to the original system identifier. As an example, the data acquisition request includes a target database address, and the server acquires a pre-stored target interface field and a target interface value corresponding to the target interface field from a database corresponding to the target database address based on the target database address, and determines the target interface value corresponding to the target interface field as a system simulation parameter corresponding to the original system identifier. The target database address is a pre-stored target interface field and an address corresponding to a database of target interface values corresponding to the target interface field.

The server obtains the target interface field and the target interface value corresponding to the target interface field based on the data obtaining request, and determines the target interface value corresponding to the target interface field as the system simulation parameter corresponding to the original system identifier. However, since the wrong system simulation parameters may be copied during the copying process, the wrong system simulation parameters may exist in the target simulation system copy. In the application, the target interface field and the target interface field in the system simulation parameters are data stored in the target database in advance, and are safety data, so that the stain data of the original simulation system is avoided, and the safety and reliability of the original simulation system are improved.

S14: loading the system simulation parameters into the original simulation system to obtain the target simulation system.

The target simulation system is a simulation system corresponding to the target system, and is obtained after loading system simulation parameters by the original simulation system.

As an example, the server loads system simulation parameters into the original simulation system to obtain the target simulation system. For example, the target interface field of the server and the target interface value corresponding to the target interface field are loaded to the original simulation system to obtain the target simulation system. Preferably, since in a real service system, that is, a target system, a server increases or modifies data in the target system through POST/PULL, and then obtains the data in the increased or modified target system through GET method, or DELETEs the data in the target system through DELETE, if the target interface field in the target simulation system and the target interface value corresponding to the target interface field are not associated with each other in a key value, the server cannot normally call the target simulation system after deleting the target interface field and the target interface value corresponding to the target interface field. Before the target interface field of the server and the target interface value corresponding to the target interface field are loaded into the original simulation system, the target interface field and the target interface value corresponding to the target interface field are subjected to key value association, so that the server can normally call the target simulation system under any condition, and the reliability of the simulation system is improved.

In the embodiment, a server acquires a system simulation request, wherein the system simulation request comprises system creation parameters, an empty test system corresponding to the system creation parameters is created based on the system creation parameters, the empty test system is determined to be an original simulation system, the original simulation system comprises an original system identifier, and the original simulation system is replaced by a wall opening in a target system, so that potential safety hazards to the target system are avoided, and the safety of the target system is improved; forming a data acquisition request based on the original system identifier, acquiring system simulation parameters corresponding to the original system identifier based on the data acquisition request, avoiding causing stain data to the original simulation system, and improving the safety and reliability of the original simulation system; loading the system simulation parameters into the original simulation system to obtain the target simulation system, so that the server can normally call the target simulation system under any condition, and the reliability of the simulation system is improved.

In one embodiment, as shown in fig. 2, in step S13, a data acquisition request is formed based on an original system identifier, and system simulation parameters corresponding to the original system identifier are acquired based on the data acquisition request, including:

s21: based on the original system identification, a first data acquisition request is formed, the first data acquisition request comprising the original system identification and at least one target interface field.

S22: based on the data acquisition request, the interface editing page is displayed.

S23: and acquiring a target interface value corresponding to at least one target interface field from the interface editing page.

S24: and determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identification.

Wherein the first data acquisition request is a request generated based on the original system identification. The first data acquisition request includes an original system identification and at least one target interface field. The interface editing interface is an interface for acquiring a target interface value corresponding to at least one target interface field.

As an example, the server forms a first data acquisition request based on the original system identification, the first data acquisition request including the original system identification and at least one target interface field. For example, the target interface fields include, but are not limited to, an interface request method, an interface request address uri, and an interface input parameter, and the interface request parameter may be one or more. The server obtains at least one interface request method input by a user, an interface request address uri and a target interface value corresponding to an interface input parameter from an interface editing page, and determines the target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to an original system identifier.

In this embodiment, the server forms a first data acquisition request based on the original system identifier, where the first data acquisition request includes the original system identifier and at least one target interface field; displaying an interface editing page based on the data acquisition request; acquiring a target interface value corresponding to at least one target interface field from an interface editing page; and determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier, and acquiring the corresponding system simulation parameter according to the actual requirement of a user.

In one embodiment, as shown in fig. 3, in step S13, a data acquisition request is formed based on an original system identifier, and system simulation parameters corresponding to the original system identifier are acquired based on the data acquisition request, including:

s31: based on the original system identification, a second data acquisition request is formed, the second data acquisition request including the target database address.

S32: and acquiring a target interface information table from a target database corresponding to the target database address based on the target database address.

S33: and acquiring at least one target interface field and a target interface value corresponding to the at least one target interface field from the target interface information table.

S34: and determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identification.

Wherein the second data acquisition request is a request generated based on the original system identification. The second data acquisition request includes the target database address. The target interface information table is an information table in a target database and comprises at least one target interface field and a target interface value corresponding to the at least one target interface field. The target database is a database corresponding to the target database address and is used for storing at least one target interface field and a target interface value corresponding to the at least one target interface field in advance.

As an example, the server forms a second data acquisition request based on the original system identification. Since the second data acquisition request includes the target database address, the server acquires the target interface information table from the target database based on the target database address. The target interface information table includes at least one target interface field and a target interface value corresponding to the at least one target interface field. The server acquires at least one target interface field and a target interface value corresponding to the at least one target interface field from the target interface information table, and determines the target interface value corresponding to the at least one target interface field as a system simulation parameter corresponding to the original system identifier.

In this embodiment, the server forms a second data acquisition request based on the original system identifier, where the second data acquisition request includes the target database address; acquiring a target interface information table from a target database based on the target database address; acquiring at least one target interface field and a target interface value corresponding to the at least one target interface field from a target interface information table; and determining the target interface value corresponding to the at least one target interface field as a system simulation parameter corresponding to the original system identifier, and directly acquiring the at least one target interface field and the target interface value corresponding to the at least one target interface field from the target interface information table, so that the stain data of the original simulation system can be avoided, and the safety and reliability of the original simulation system are improved.

In one embodiment, as shown in fig. 4, in step S13, a data acquisition request is formed based on an original system identifier, and system simulation parameters corresponding to the original system identifier are acquired based on the data acquisition request, including:

s41: based on the original system identification, a third data acquisition request is formed, the third data acquisition request including the target system identification.

S42: and inquiring a system database based on the target system identification, and judging whether historical test data corresponding to the target system identification exists or not.

S43: if the historical test data corresponding to the target system identification exists, the historical test data is determined to be the system simulation parameters corresponding to the original system identification.

S44: if the historical test data corresponding to the target system identification does not exist, acquiring the target test data corresponding to the target system identification by adopting preset test data acquisition logic based on the target system identification, and determining the target test data as the system simulation parameters corresponding to the original system identification.

Wherein the third data acquisition request is a request generated based on the original system identification. The third data acquisition request includes a target system identification. The target system identifier is an identifier corresponding to the target system. The system database is a database for storing historical test data. The historical test data is target test data stored in a system database. The preset test data acquisition logic is user-defined logic and is used for acquiring target test data. The target test data is interface interaction data generated between the test system and the target system by adopting preset test data acquisition logic. The target test data is data generated by a real business system, namely, data generated by the target system. The interface interaction data includes at least one target interface field and a target interface value corresponding to the at least one target interface field.

As an example, the server forms a third data acquisition request based on the original system identification. Because the third data acquisition request comprises the target system identifier, the server queries the system database based on the target system identifier, judges whether historical test data corresponding to the target system identifier exists, and if the historical test data corresponding to the target system identifier exists, determines the historical test data as the system simulation parameter corresponding to the original system identifier. If the historical test data corresponding to the target system identification does not exist, acquiring the target test data corresponding to the target system identification by adopting preset test data acquisition logic based on the target system identification, and determining the target test data as the system simulation parameters corresponding to the original system identification. It can be appreciated that, since the target test data is data generated by a real service system, the server determines the target test data as a system simulation parameter corresponding to the original system identifier, so as to improve the authenticity of the target simulation system.

In this embodiment, the server forms a third data acquisition request based on the original system identifier, where the third data acquisition request includes the target system identifier; inquiring a system database based on the target system identifier, and judging whether historical test data corresponding to the target system identifier exists or not; if the historical test data corresponding to the target system identification exists, determining the historical test data as the system simulation parameters corresponding to the original system identification; if the historical test data corresponding to the target system identifier does not exist, acquiring the target test data corresponding to the target system identifier by adopting preset test data acquisition logic based on the target system identifier, determining the target test data as the system simulation parameter corresponding to the original system identifier, and determining the target test data as the system simulation parameter corresponding to the original system identifier by the server due to the data generated by the real business system of the target test data, so that the authenticity of the target simulation system can be improved.

In one embodiment, as shown in fig. 5, in step S44, based on the target system identifier, the target test data corresponding to the target system identifier is acquired by using preset test data acquisition logic, and the target test data is determined as the system simulation parameter corresponding to the original system identifier, including:

s51: and testing the target system corresponding to the target system identifier, and acquiring interface interaction data between the test system and the target system in real time.

S52: analyzing the interface interaction data to obtain interface analysis data.

S53: and encrypting the interface analysis data to obtain target test data, and determining the target test data as system simulation parameters corresponding to the original system identification.

The interface interaction data are interface data generated between the test system and the target system when the test system calls the target system. The interface analysis data is the data after the interface interaction data is analyzed. The target test data is data obtained after the interface analysis data is encrypted.

As an example, the server tests the target system corresponding to the target system identifier according to the target system identifier in the system test request, and obtains interface interaction data between the test system and the target system. It should be noted that the system test request includes, but is not limited to, a target system identifier and an interface call parameter. And the server calls the application service corresponding to the interface call parameter in the target system according to the interface call parameter in the system test request, acquires call return data returned by the application service, and determines the interface call parameter and the call return data corresponding to the interface call parameter as interface interaction data. The interface calling parameter is a parameter for calling the service in the target system. The application service is a service in the target system. The call return data is data generated by the application service according to the interface call parameters.

It can be understood that when the user sends a system test request to the server by using the client, because the server tests the real service system, that is, the target system, the server tests the target system corresponding to the target system identifier in the system test request according to the system test request, and acquires interface interaction data between the test system and the target system in real time, so that the interface interaction data acquired by the server is also real data, the interface interaction data is processed in the subsequent step, so as to acquire the real target test data, replace the existing mode of learning a small amount of manually input target test data by a machine learning algorithm, and generate a plurality of target test data, thereby improving the authenticity of the target test data. And the server directly acquires interface interaction data between the test system and the target system from the process of testing the target system corresponding to the target system identifier in real time, and acquires target test data according to the interface interaction data, so that the problem of inputting the target test data by hand in a large amount is solved, the acquisition efficiency of the target test data is improved, and the workload is reduced.

As another example, the server service parses interface interaction data to obtain an interface request method, an interface request address, an interface input parameter, a call return value, and a call return state in the interface call parameters; and respectively determining an interface request method, an interface request address, an interface input parameter, a call return value and a value corresponding to a call return state from the call return data. The server stores the interface request method, the interface request address, the interface input parameter, the calling return value and the calling return state in association with the values corresponding to the interface request method, the interface request address, the interface input parameter, the calling return value and the calling return state to obtain the interface analysis data. Preferably, the interface parsing data can be in a metadata format, so that the interface parsing data can be conveniently transferred to different test platforms. It can be understood that the server stores the interface request method, the interface request address, the interface input parameter, the call return value and the call return state in association with the values corresponding to the interface request method, the interface request address, the interface input parameter, the call return value and the call return state, so as to avoid errors in the interface analysis data and improve the accuracy of the interface analysis data.

As another example, the server encrypts the interface resolution data using an encryption algorithm to obtain the target test data. For example, encryption algorithms include, but are not limited to, DES (Data Encryption Standard, data encryption algorithm, DES for short), IDEA (International Data Encryption Algorithm, international data encryption algorithm, IDEA for short), and RSA algorithm. It can be appreciated that the security of the target test data can be improved by encrypting the interface analysis data. Preferably, the interface analysis data may include private data or sensitive data of the user, and the server further includes desensitizing the interface analysis data in the process of encrypting the interface analysis data, obtaining a desensitized interface value, encrypting the desensitized interface value, obtaining target test data, and determining the target test data as a system simulation parameter corresponding to the original system identifier. It can be understood that the server performs desensitization processing on the interface analysis data to obtain a desensitization interface value, and performs encryption processing on the desensitization interface value to obtain target test data, so that the security of the target test data of the user can be further improved.

In this embodiment, the server tests the target system corresponding to the target system identifier, and obtains interface interaction data between the test system and the target system in real time, so that the interface interaction data in the subsequent step is processed, and real target test data is obtained, so that the conventional mode of generating the target test data through a computer algorithm is replaced, and the authenticity of the target test data is improved. And the server directly acquires interface interaction data between the test system and the target system from the process of testing the target system corresponding to the target system identifier in real time, acquires target test data according to the interface interaction data, and determines the target test data as system simulation parameters corresponding to the original system identifier. The problem of inputting a large amount of target test data manually in the prior art is solved, the acquisition efficiency of the target test data is improved, and the workload is reduced; analyzing the interface interaction data to obtain interface analysis data so as to avoid errors of the interface analysis data and improve the accuracy of the interface analysis data; and encrypting the interface analysis data to obtain target test data, so that the safety of the target test data of the user can be improved.

In one embodiment, as shown in fig. 6, in step S53, the interface parsing data includes at least one target interface field and a target interface value corresponding to the target interface field; encrypting the interface analysis data to obtain target test data, including:

s61: and obtaining the interface field type corresponding to each target interface field.

S62: if the interface field type is the sensitive field type, performing desensitization processing on a target interface value corresponding to the sensitive field type to obtain a desensitized interface value, and encrypting the desensitized interface value to obtain first encrypted data.

S63: and if the interface field type is the non-sensitive field type, encrypting the target interface value corresponding to the non-sensitive field type to obtain second encrypted data.

S64: and acquiring target test data based on the first encrypted data and the second encrypted data, and determining the target test data as a system simulation parameter corresponding to the original system identification.

The interface field type is the type corresponding to the target interface field. The sensitive field type is that the target interface field is the field type corresponding to the sensitive data of the user. For example, the user-sensitive data includes, but is not limited to, a user password type, a user identification card type, a user cell phone number type, and the like. The desensitization interface value is a value obtained by carrying out desensitization processing on the target interface value corresponding to the sensitive field type. The non-sensitive field type is a field type for which the target interface field is not the user sensitive data. The first encrypted data is data obtained by encrypting the desensitization interface value by adopting a first encryption algorithm. The second encrypted data is data obtained by encrypting the target interface value of the non-sensitive field type by adopting a second encryption algorithm. The first encryption algorithm includes, but is not limited to, DES algorithm, IDEA algorithm, and RSA algorithm. The second encryption algorithm includes, but is not limited to, DES algorithm, IDEA algorithm, and RSA algorithm. The first encryption algorithm may or may not be identical to the second encryption algorithm. Preferably, the first encryption algorithm is inconsistent with the second encryption algorithm. The first encryption algorithm is an encryption algorithm with a higher encryption degree. Such as the RSA algorithm.

Specifically, the acquisition server acquires the interface field type corresponding to each target interface field by adopting a sensitive data identification algorithm. The sensitive data identification algorithm is an algorithm capable of carrying out sensitive identification on data.

As an example, the server obtains the interface field type corresponding to each target interface field by using a sensitive data identification algorithm, and the server identifies the target interface field and the target interface value corresponding to the target interface field in the interface analysis data by using a sensitive data identification algorithm, for example:

target interface field: username + destination interface field: paaswd;

alternatively, the target interface field: username + destination interface field: the amount of the active ingredient is pwd,

both paaswd and pwd are passwords, so that paaswd and pwd are identified as user password type sensitive data, and the paaswd and pwd are desensitized, for example: the user password type desensitization is as follows. Likewise, the user id type desensitization is 362133 and 4, and the user phone number type is: 189*****15.

As another example, when the server derives the desensitization interface value, a temporary directory corresponding to the interface request address is generated, a file of the interface request method field value+the random unique character string UUID file name is generated under the temporary directory, the desensitization interface value is written in the file, and the temporary directory is encrypted and packaged by using a first encryption algorithm, so as to obtain first encrypted data. It can be understood that, because the interface field type corresponding to the target interface field is a sensitive field type, the server stores the desensitized interface value in the temporary directory, so as to delete the data in the temporary directory in time after the temporary directory is encrypted and packed by using the first encryption algorithm, thereby improving the security of the target interface field. The server encrypts the desensitization interface value by adopting a first encryption algorithm, so that the security of the first encrypted data can be further improved.

As another example, if the interface field type is a non-sensitive field type, a temporary directory corresponding to the interface request address is generated, a file of the interface request method field value+the random unique character string UUID file name is generated under the temporary directory, the target interface value is written into the file, and the temporary directory is encrypted and packaged by using a second encryption algorithm, so as to obtain second encrypted data.

As another example, the server determines the first encrypted data and the second encrypted data as target test data, and exports the target test data into a metadata format for convenient delivery to different test platforms.

In this embodiment, the server acquires an interface field type corresponding to each target interface field; if the interface field type is a sensitive field type, performing desensitization processing on a target interface value corresponding to the sensitive field type to obtain a desensitized interface value, and encrypting the desensitized interface value to obtain first encrypted data; if the interface field type is a non-sensitive field type, encrypting a target interface value corresponding to the non-sensitive field type to obtain second encrypted data; based on the first encrypted data and the second encrypted data, target test data are obtained, and safety of the target test data of a user can be improved.

In one embodiment, as shown in fig. 7, in step S14, loading system simulation parameters into an original simulation system to obtain a target simulation system includes:

s71: and carrying out interface association identification on the system simulation parameters to obtain an association interface field and an association interface value.

S72: and carrying out key value association on the associated interface field and the associated interface value to obtain associated interface data, and loading the associated interface data into the original simulation system to obtain the target simulation system.

The associated interface field is an interface field obtained after interface association identification is carried out on the system simulation parameters. The associated interface value is a value corresponding to an interface field obtained after interface association identification is carried out on the system simulation parameters. The associated interface data is data obtained by carrying out key value association on the associated interface field and the associated interface value.

As an example, since in a real service system, that is, a target system, a server increases or modifies data in the target system through POST/PULL, and then obtains the data in the increased or modified target system through GET method or DELETEs the data in the target system through DELETE, if the target interface field in the target simulation system and the target interface value corresponding to the target interface field are not associated with each other in a key value, the server may not normally call the target simulation system after deleting the target interface field and the target interface value corresponding to the target interface field. Therefore, the server adopts an association relation recognition algorithm to perform interface association recognition on the system simulation parameters, obtain association interface fields and association interface values, perform key value association on the association interface fields and the association interface values, obtain association interface data, load the association interface data into the original simulation system, and obtain the target simulation system, so that the server can normally call the target simulation system under any condition, and the reliability of the simulation system is improved.

In this embodiment, the server performs interface association identification on the system simulation parameters, and obtains an association interface field and an association interface value; and carrying out key value association on the associated interface field and the associated interface value to obtain associated interface data, loading the associated interface data into the original simulation system to obtain the target simulation system, so that the server can normally call the target simulation system under any condition, and the reliability of the simulation system is improved.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.

In an embodiment, a test system simulation device is provided, where the test system simulation device corresponds to the test system simulation method in the above embodiment one by one. As shown in fig. 9, the test system simulation apparatus includes a request acquisition module 10, a system creation module 20, a parameter acquisition module 30, and a parameter loading module 40. The functional modules are described in detail as follows:

a request acquisition module 10, configured to acquire a system simulation request, where the system simulation request includes a system creation parameter;

A system creation module 20, configured to create an empty test system corresponding to the system creation parameter based on the system creation parameter, and determine the empty test system as an original simulation system, where the original simulation system includes an original system identifier;

a parameter obtaining module 30, configured to form a data obtaining request based on the original system identifier, and obtain a system simulation parameter corresponding to the original system identifier based on the data obtaining request;

the parameter loading module 40 is configured to load the system simulation parameters into the original simulation system, and obtain the target simulation system.

Further, the parameter obtaining module 30 includes:

the first request submodule is used for forming a first data acquisition request based on the original system identifier, and the first data acquisition request comprises the original system identifier and at least one target interface field;

the first interface acquisition sub-module is used for acquiring a target interface value corresponding to at least one target interface field from the interface editing page;

Further, the parameter obtaining module 30 includes:

the second request submodule is used for forming a second data acquisition request based on the original system identification, wherein the second data acquisition request comprises a target database address;

the second interface acquisition sub-module is used for acquiring at least one target interface field and a target interface value corresponding to the at least one target interface field from the target interface information table;

Further, the parameter obtaining module 30 includes:

the third request submodule is used for forming a third data acquisition request based on the original system identifier, wherein the third data acquisition request comprises a target system identifier;

the data judging sub-module is used for inquiring the system database based on the target system identification and judging whether historical test data corresponding to the target system identification exists or not;

Further, the fourth parameter determination submodule includes:

the encryption processing unit is used for carrying out encryption processing on the interface analysis data to obtain target test data, and determining the target test data as system simulation parameters corresponding to the original system identification.

Further, the encryption processing unit includes:

a field type subunit, configured to obtain an interface field type corresponding to each target interface field;

the desensitization processing subunit is used for carrying out desensitization processing on the target interface value corresponding to the sensitive field type if the interface field type is the sensitive field type, obtaining a desensitized interface value, encrypting the desensitized interface value and obtaining first encrypted data;

The first encryption subunit is configured to encrypt a target interface value corresponding to the non-sensitive field type if the interface field type is the non-sensitive field type, and obtain second encrypted data;

and the second encryption subunit is used for acquiring target test data based on the first encryption data and the second encryption data and determining the target test data as a system simulation parameter corresponding to the original system identifier.

Further, the parameter loading module 40 includes:

and the key value association sub-module is used for carrying out key value association on the association interface field and the association interface value, obtaining association interface data, loading the association interface data into the original simulation system and obtaining the target simulation system.

For specific limitations of the test system simulation device, reference may be made to the above description of the test system simulation method, and no further description is given here. The modules in the test system simulation device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for test system simulation. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements a test system simulation method.

In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor executes the computer program to implement the test system simulation method in the above embodiment, for example, steps S11 to S14, and for avoiding repetition, the description is omitted herein. Alternatively, the processor may implement the functions of the modules/units in this embodiment of the test system simulator when executing the computer program, for example, the request acquisition module 10, the system creation module 20, the parameter acquisition module 30, and the parameter loading module 40, which are not described herein in detail for the sake of avoiding repetition.

In an embodiment, a computer readable storage medium is provided, and a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the method for simulating a test system in the above embodiment is implemented, for example, in step S11 to step S14, which is not repeated here. Alternatively, the computer program, when executed by the processor, implements the functions of each module/unit in the embodiment of the test system simulation device, for example, the request acquisition module 10, the system creation module 20, the parameter acquisition module 30, and the parameter loading module 40, which are not described herein again for avoiding repetition.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.

The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.

Claims

1. A test system simulation method, comprising the steps of:

acquiring a system simulation request, wherein the system simulation request comprises system creation parameters; the system simulation request is a request for creating a simulation system corresponding to a target system, the target system is a system to be tested, and the system creation parameter is a parameter corresponding to the target system and is used for creating the simulation system corresponding to the target system;

Creating an empty test system corresponding to the system creation parameter based on the system creation parameter, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identifier; the empty test system is a system only comprising a target system name and a target system address; the original system identifier is the target system name;

loading the system simulation parameters into the original simulation system to obtain a target simulation system;

the forming a data acquisition request based on the original system identifier, and acquiring the system simulation parameters corresponding to the original system identifier based on the data acquisition request, including:

displaying an interface editing page based on the data acquisition request;

Determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier;

or, the forming a data acquisition request based on the original system identifier, and acquiring the system simulation parameters corresponding to the original system identifier based on the data acquisition request, including:

2. The test system simulation method according to claim 1, wherein the acquiring, based on the target system identifier, target test data corresponding to the target system identifier using a preset test data acquisition logic, and determining the target test data as a system simulation parameter corresponding to the original system identifier includes:

Analyzing the interface interaction data to obtain interface analysis data;

3. The test system simulation method of claim 2, wherein the interface parsing data includes at least one target interface field and a target interface value corresponding to the target interface field; encrypting the interface analysis data to obtain target test data, and determining the target test data as a system simulation parameter corresponding to the original system identifier, wherein the method comprises the following steps:

acquiring an interface field type corresponding to each target interface field;

4. The test system simulation method according to claim 1, wherein loading the system simulation parameters into the original simulation system to obtain a target simulation system comprises:

5. A test system simulation apparatus, comprising:

the system comprises a request acquisition module, a system simulation module and a system simulation module, wherein the request acquisition module is used for acquiring a system simulation request, and the system simulation request comprises system creation parameters; the system simulation request is a request for creating a simulation system corresponding to a target system, the target system is a system to be tested, and the system creation parameter is a parameter corresponding to the target system and is used for creating the simulation system corresponding to the target system;

The system creation module is used for creating an empty test system corresponding to the system creation parameter based on the system creation parameter, and determining the empty test system as an original simulation system, wherein the original simulation system comprises an original system identifier; the empty test system is a system only comprising a target system name and a target system address; the original system identifier is the target system name;

the parameter loading module is used for loading the system simulation parameters into the original simulation system to obtain a target simulation system;

the parameter acquisition module is further configured to form a first data acquisition request based on the original system identifier, where the first data acquisition request includes the original system identifier and at least one target interface field; displaying an interface editing page based on the data acquisition request; acquiring a target interface value corresponding to at least one target interface field from the interface editing page; determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier;

Or the parameter acquisition module is further used for forming a second data acquisition request based on the original system identifier, wherein the second data acquisition request comprises a target database address; acquiring a target interface information table from a target database based on the target database address; acquiring at least one target interface field and a target interface value corresponding to the at least one target interface field from the target interface information table; determining a target interface value corresponding to at least one target interface field as a system simulation parameter corresponding to the original system identifier;

or the parameter acquisition module is further configured to form a third data acquisition request based on the original system identifier, where the third data acquisition request includes a target system identifier; inquiring a system database based on the target system identifier, and judging whether historical test data corresponding to the target system identifier exists or not; if historical test data corresponding to the target system identification exists, determining the historical test data as system simulation parameters corresponding to the original system identification; and if the historical test data corresponding to the target system identifier does not exist, acquiring the target test data corresponding to the target system identifier by adopting preset test data acquisition logic based on the target system identifier, and determining the target test data as the system simulation parameter corresponding to the original system identifier.

6. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the test system simulation method according to any of claims 1 to 4 when executing the computer program.

7. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the test system simulation method according to any one of claims 1 to 4.