CN112711538A - Test system simulation method and device, computer equipment and storage medium - Google Patents

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

Info

Publication number
CN112711538A
CN112711538A CN202011627382.2A CN202011627382A CN112711538A CN 112711538 A CN112711538 A CN 112711538A CN 202011627382 A CN202011627382 A CN 202011627382A CN 112711538 A CN112711538 A CN 112711538A
Authority
CN
China
Prior art keywords
target
interface
simulation
original
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202011627382.2A
Other languages
Chinese (zh)
Other versions
CN112711538B (en
Inventor
钟世亮
陈仲伟
杨子豪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Merchants Finance Technology Co Ltd
Original Assignee
China Merchants Finance Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Merchants Finance Technology Co Ltd filed Critical China Merchants Finance Technology Co Ltd
Priority to CN202011627382.2A priority Critical patent/CN112711538B/en
Publication of CN112711538A publication Critical patent/CN112711538A/en
Application granted granted Critical
Publication of CN112711538B publication Critical patent/CN112711538B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3696Methods or tools to render software testable
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3664Environments for testing or debugging software

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a test system simulation method, a test system simulation device, computer equipment and a storage medium, wherein the test system simulation method comprises the steps of obtaining a system simulation request, wherein the system simulation request comprises system creation parameters; based on the system creating parameters, creating an empty test system corresponding to the system creating 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 identification, and acquiring system simulation parameters corresponding to the original system identification based on the data acquisition request; and loading the system simulation parameters into the original simulation system to obtain the target simulation system. The technical scheme avoids potential safety hazards to the target system and improves the safety of the target system.

Description

Test system simulation method and 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 and apparatus, a computer device, and a storage medium.
Background
When a tester needs to test a target system (i.e. a software system to be tested), the target system often 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 method is generally adopted: firstly, opening a wall from a target system to a third-party simulation system, and if callback of a third-party simulation system interface is involved, opening the wall from the third-party simulation system to the target system; and secondly, completely copying the third-party simulation system beside the target system, and calling a third-party simulation system interface in a mode of building a third-party simulation system copy. However, the above test method has the following problems: 1. subject to the target system security policy, the target system is not allowed to directly open the wall to the third-party simulation system; 2. taint data and the like may be caused to a third-party simulation system, and potential safety hazards are caused to the third-party simulation system; 3. building third-party simulation system copies requires a large amount of manpower and material resources.
Disclosure of Invention
The embodiment of the invention provides a test system simulation method and device, computer equipment and a storage medium, and aims to solve the problem of complete hidden danger of an existing third-party simulation system.
A test system simulation method, comprising the steps performed by a test system of:
acquiring a system simulation request, wherein the system simulation request comprises a system creation parameter;
based on the system creating parameters, creating an empty test system corresponding to the system creating 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 identification, and acquiring system simulation parameters corresponding to the original system identification 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 obtaining request based on the original system identifier, and obtaining a system simulation parameter corresponding to the original system identifier based on the data obtaining request includes:
forming a first data acquisition request based on the original system identification, wherein the first data acquisition request comprises the original system identification 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.
Further, the forming a data obtaining request based on the original system identifier, and obtaining a system simulation parameter corresponding to the original system identifier based on the data obtaining request includes:
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 at least one target interface value corresponding to the target interface field from the target interface information table;
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.
Further, the forming a data obtaining request based on the original system identifier, and obtaining a system simulation parameter corresponding to the original system identifier based on the data obtaining request includes:
forming a third data acquisition request based on the original system identification, wherein the third data acquisition request comprises a target system identification;
inquiring a system database based on the target system identification, and judging whether historical test data corresponding to the target system identification exist 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;
and if the historical test data corresponding to the target system identification does not exist, acquiring 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 system simulation parameters corresponding to the original system identification.
Further, the acquiring, based on the target system identifier, target test data corresponding to the target system identifier by 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:
testing a target system corresponding to the target system identification, 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 parsing 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 system simulation parameters corresponding to the original system identifier, including:
acquiring an interface field type corresponding to each target interface field;
if the interface field type is a sensitive field type, desensitizing 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 system simulation parameters corresponding to the original system identification.
Further, the loading the system simulation parameters into the original simulation system to obtain a target simulation system includes:
performing interface correlation identification on the system simulation parameters to acquire correlation interface fields and correlation interface values;
and performing 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 a target simulation system.
A test system simulator, comprising:
the request acquisition module is used for acquiring a system simulation request, and the system simulation request comprises system creation parameters;
the system creating module is used for creating an empty test system corresponding to the system creating parameters based on the system creating parameters and determining the empty test system as an original simulation system, and the original simulation system comprises an original system identifier;
a parameter obtaining module, 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;
and the parameter loading module is used for loading the system simulation parameters into the original simulation system to obtain a target simulation system.
Further, the parameter obtaining module comprises:
a first request submodule, configured to form a first data obtaining request based on the original system identifier, where the first data obtaining 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 submodule 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 determining submodule is used for determining a target interface value corresponding to at least one target interface field as the system simulation parameter corresponding to the original system identification.
Further, the parameter obtaining module comprises:
a second request submodule, configured to form a second data obtaining request based on the original system identifier, where the second data obtaining request includes a target database address;
the information table acquisition submodule is used for acquiring a target interface information table from a target database based on the target database address;
the second interface acquisition submodule is used for acquiring at least one target interface field and at least one target interface value corresponding to the target interface field from the target interface information table;
and the second parameter determining submodule is used for determining a target interface value corresponding to at least one target interface field as the system simulation parameter corresponding to the original system identification.
Further, the parameter obtaining module comprises:
a third request submodule, 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 judgment submodule 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 exist or not;
a third parameter determining submodule, 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 determining submodule is used for acquiring target test data corresponding to the target system identifier by adopting a preset test data acquisition logic based on the target system identifier if no historical test data corresponding to the target system identifier exists, and determining the target test data as the system simulation parameters 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 encrypting the interface analysis data, acquiring target test data and determining the target test data as the 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;
a desensitization processing subunit, configured to perform desensitization processing on a target interface value corresponding to the sensitive field type to obtain a desensitization interface value if the interface field type is the sensitive field type, and encrypt the desensitization interface value to obtain first encrypted data;
the first encryption subunit is configured to encrypt a target interface value corresponding to the non-sensitive field type to obtain second encrypted data if the interface field type is the non-sensitive field type;
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 the system simulation parameters corresponding to the original system identification.
Further, the parameter loading module comprises:
the correlation identification submodule is used for carrying out interface correlation identification on the system simulation parameters to obtain correlation interface fields and correlation interface values;
and the key value association submodule is used for carrying out key value association on the associated interface field and the associated interface value, acquiring associated interface data, loading the associated interface data into the original simulation system and acquiring a target simulation system.
A computer device comprising a memory, a processor and a computer program stored in said memory and executable on said processor, said processor implementing the test system simulation method described above when executing said computer program.
A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the above-mentioned test system simulation method.
According to the test system simulation method and device, the computer equipment and the storage medium, the server obtains 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 the original simulation system, the original simulation system comprises the original system identification, the original simulation system replaces the original simulation system from the wall opening in the target system, the potential safety hazard to the target system is avoided, and the safety of the target system is improved; 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, so that taint data on the original simulation system is avoided, and the safety and reliability of the original simulation system are improved; the system simulation parameters are loaded 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 needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 2 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 3 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 4 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 5 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 6 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 7 is another flow chart of a test system simulation method according to an embodiment of the present invention;
FIG. 8 is a diagram illustrating an application environment of the simulation method of the test system according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of a test system simulator in accordance with an embodiment of the present invention;
FIG. 10 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The test system simulation method provided by the embodiment of the invention can be applied to the application environment shown in fig. 8. Specifically, the test system simulation method is applied to a test system simulation system, where the test system simulation system includes a client and a server as shown in fig. 8, and the client and the server communicate with each other through a network to realize test system simulation. The client is also called a user side, and refers to a program corresponding to the server and providing local services for the client. The client may be installed on, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server may be implemented as a stand-alone server or as a server cluster consisting of a plurality of servers.
In an embodiment, as shown in fig. 1, a test system simulation method is provided, which is described by taking the server in fig. 8 as an example, and includes the following steps:
s11: and 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 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 creating parameters are parameters corresponding to the target system and are used for creating a simulation system corresponding to the target system. For example, the system creation parameters include, but are not limited to, a target system name and a target system address, among others. 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: com, so that in subsequent steps, based on the target system name api abc and the target system address url: and api, abc and com, and creating a simulation system corresponding to the target system.
S12: and based on the system creating parameters, creating a null test system corresponding to the system creating parameters, and determining the null test system as an original simulation system, wherein the original simulation system comprises an original system identifier.
The null test system is a system only including a target system name and a target system address. The original simulation system is a simulation system determined from the empty test system. The original system identification is the identification 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 creates an empty test system based on the target system name api. abc and the target system address url: com, create target system name api abc and target system address url: and determining the empty test system as an original simulation system and determining the name api.abc of the target system as an original system identifier. Thus, the server can access the target system address url: api, abc, com, determining an access address api, abc, simula, cmft, com of the original simulation system, and accessing the original simulation system; or determining an original simulation system access address api, abc.com by binding host to the original simulation system, and directly accessing the original simulation system by using the original simulation system access address api, abc.com. It should be noted that, the server accesses the original simulation system through the above method, and when the original simulation system is used to test the target system, the target system does not need to be tested in a way of opening the wall to the target system, so that the security of the target system is improved. The server creates the empty test system corresponding to the system creation parameters based on the system creation parameters, determines the empty test system as an original simulation system, replaces the original simulation system from the wall in the target system, avoids potential safety hazards to the target system, and improves the safety of the target system.
S13: and 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.
The data acquisition request is a request formed based on the original system identifier and is used for acquiring system simulation parameters corresponding to the original system identifier. The system simulation parameters are parameters obtained based on the data acquisition request. For example, the 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 parameter. For example, the target interface field includes, but is not limited to, an interface request method, an interface request address, interface input parameters, a call return value, a call return status, and the like. As an example, the interface request method is a method of requesting an application service of a target system. For example, the interface request method includes, but is not limited to, one of GET, POST, PUT, and DELETE. 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 specifically be a request payload, and the data format is a character string. For example, target interface values include, but are not limited to, call return values, call return states, and the like. And calling the return value to be the value returned by the application service of the target system based on the system test request. For example, the call return value may be response specifically, and the data format is a character string. The call return state is a state in which the application service of the target system returns a call return value. For example, the call return state may be status specifically. The target interface value is the value in the call return data corresponding to the target interface field.
Specifically, the server acquires a target interface field and a 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 obtaining request includes a target database address, the server obtains 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 an address corresponding to a pre-stored target interface field and a database of a target interface value corresponding to the target interface field.
It can be understood that, 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, so the system simulation parameter is directly obtained according to the data obtaining request. However, since the wrong system simulation parameters may also 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 pre-stored in a target database and are safe data, so that taint data on the original simulation system is avoided, and the safety and the reliability of the original simulation system are improved.
S14: and 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 by loading system simulation parameters by the original simulation system.
As an example, the server loads system simulation parameters to the original simulation system to obtain the target simulation system. For example, a server target interface field and a target interface value corresponding to the target interface field are loaded to the original simulation system, and the target simulation system is obtained. Preferably, in a real business system, that is, in a target system, a server adds or modifies data in the target system through POST/PULL, and then acquires the added or modified data in the target system through a GET method, or DELETEs the data in the target system through DELETE, but if a target interface field in the target simulation system and a target interface value corresponding to the target interface field are not keyed, 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 to 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 this embodiment, a server obtains a system simulation request, where the system simulation request includes a system creation parameter, creates an empty test system corresponding to the system creation parameter based on the system creation parameter, and determines the empty test system as an original simulation system, where the original simulation system includes an original system identifier, and replaces a wall in a target system to the original simulation system, so as to avoid potential safety hazards to the target system and improve the safety of the target system; 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, so that taint data on the original simulation system is avoided, and the safety and reliability of the original simulation system are improved; the system simulation parameters are loaded 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, the forming a data obtaining request based on the original system identifier and obtaining the system simulation parameters corresponding to the original system identifier based on the data obtaining request in step S13 include:
s21: based on the original system identification, a first data acquisition request is formed, the first data acquisition request including the original system identification and at least one target interface field.
S22: and displaying an interface editing page based on the data acquisition request.
S23: and acquiring a target interface value corresponding to at least one target interface field from the interface editing page.
S24: and determining the target interface value corresponding to the at least one target interface field as the system simulation parameter corresponding to the original system identification.
The first data acquisition request is a request generated based on an 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 used 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 field includes, but is not limited to, an interface request method, an interface request address uri, and an interface input parameter, which 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, a server forms a first data acquisition request based on an 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 the user.
In one embodiment, as shown in fig. 3, in step S13, forming a data obtaining request based on the original system identifier, and obtaining the system simulation parameters corresponding to the original system identifier based on the data obtaining request includes:
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 the target interface value corresponding to the at least one target interface field as the 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 pre-storing 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 the 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 comprises at least one target interface field and a target interface value corresponding to the at least one target interface field. And 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 the 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 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 a target interface information table; 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 directly acquiring the at least one target interface field and the target interface value corresponding to the at least one target interface field from a target interface information table, so that taint data caused to the original simulation system can be avoided, and the safety and the reliability of the original simulation system are improved.
In one embodiment, as shown in fig. 4, in step S13, forming a data obtaining request based on the original system identifier, and obtaining the system simulation parameters corresponding to the original system identifier based on the data obtaining request includes:
s41: and forming a third data acquisition request based on the original system identification, wherein the third data acquisition request comprises the target system identification.
S42: and querying a system database based on the target system identifier, and judging whether historical test data corresponding to the target system identifier exists or not.
S43: and 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.
S44: and 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 a 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 identification is the identification 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 logic set by a user in a self-defined mode 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 a target system. The interface interaction data comprises 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. And 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. And 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 a 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 understood that, since the target test data is data generated by the real business system, the server determines the target test data as the system simulation parameters corresponding to the original system identification, and the authenticity of the target simulation system can be improved.
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 identification, and judging whether historical test data corresponding to the target system identification exist 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 identification does not exist, the target test data corresponding to the target system identification is obtained by adopting preset test data obtaining logic based on the target system identification, the target test data is determined to be the system simulation parameter corresponding to the original system identification, and the server determines the target test data to be the system simulation parameter corresponding to the original system identification due to the data generated by the service system with real target test data, so that the authenticity of the target simulation system can be improved.
In an embodiment, as shown in fig. 5, in step S44, acquiring target test data corresponding to the target system identifier by using preset test data acquisition logic based on the target system identifier, and determining the target test data as the system simulation parameters corresponding to the original system identifier includes:
s51: and testing the target system corresponding to the target system identification, and acquiring interface interaction data between the test system and the target system in real time.
S52: and 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 is interface data generated between the test system and the target system when the test system calls the target system. The interface analysis data is data obtained by analyzing the interface interaction data. The target test data is data obtained by encrypting the interface analysis data.
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, an interface call parameter, and the like. The server calls the application service corresponding to the interface calling parameter in the target system according to the interface calling parameter in the system test request, obtains calling return data returned by the application service, and determines the interface calling parameter and the calling return data corresponding to the interface calling parameter as interface interaction data. The interface calling parameter is a parameter for calling a service in the target system. The application service is a service in the target system. And calling the return data to be the data generated by the application service according to the interface calling parameters.
It can be understood that, when a user sends a system test request to a server by using a client, because the server tests a real service system, that is, a target system, the server tests the target system corresponding to a target system identifier in the system test request according to the system test request, and obtains interface interaction data between the test system and the target system in real time, so that the interface interaction data obtained by the server is also real data, so that the interface interaction data is processed in subsequent steps to obtain real target test data, and the method replaces the existing method of learning a small amount of manually input target test data through a machine learning algorithm to generate a plurality of target test data, thereby improving the authenticity of the target test data. And the server directly obtains the interface interaction data between the test system and the target system in real time in the process of testing the target system corresponding to the target system identification, and then obtains the target test data according to the interface interaction data, so that the problem that a large amount of target test data are manually input in the prior art is solved, the target test data obtaining efficiency is improved, and the workload is reduced.
As another example, the server parses the interface interaction data, and obtains 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 parameter; 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 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, and acquires interface analysis data. Preferably, the interface parsing data can be in a metadata format, and is convenient to transmit to different test platforms. 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 interface analysis data and improve the accuracy of the interface analysis data.
As another example, the server encrypts the interface analysis data by using an encryption algorithm to obtain the target test data. For example, the Encryption Algorithm includes, but is not limited to, a DES (Data Encryption Standard, DES) Algorithm, an IDEA (International Data Encryption Algorithm, IDEA) Algorithm, and an RSA Algorithm. Therefore, 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 performs desensitization processing on the interface analysis data in the encryption process of the interface analysis data, acquires a desensitization interface value, performs encryption processing on the desensitization interface value, acquires target test data, and determines the target test data as a system simulation parameter corresponding to the original system identifier. 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 is processed in the subsequent steps to obtain real target test data, and the method replaces the conventional method of generating target test data through a computer algorithm, thereby improving the authenticity of the target test data. And the server directly obtains interface interaction data between the test system and the target system in real time in the process of testing the target system corresponding to the target system identification, then obtains target test data according to the interface interaction data, and determines the target test data as system simulation parameters corresponding to the original system identification. The problem that a large amount of target test data are input 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; the interface analysis data is encrypted to obtain the target test data, and the safety of the target test data of the user can be improved.
In an 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, comprising:
s61: and acquiring the interface field type corresponding to each target interface field.
S62: and if the interface field type is the sensitive field type, desensitizing the 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 a 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 system simulation parameters corresponding to the original system identification.
And the interface field type is the type corresponding to the target interface field. The sensitive field type is a field type corresponding to the user sensitive data of the target interface field. For example, user sensitive data includes, but is not limited to, a user password type, a user identification card type, a user phone number type, and the like. The desensitization interface value is obtained after desensitization processing is carried out on a target interface value corresponding to the sensitive field type. The non-sensitive field type is a field type which is not corresponding to the user sensitive data of the target interface field. The first encryption data is data obtained by encrypting the desensitization interface value by adopting a first encryption algorithm. The second encrypted data is 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, the DES algorithm, the IDEA algorithm, and the 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 not identical to 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 using 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 an interface field type corresponding to each target interface field by using a sensitive data identification algorithm, and the server identifies a target interface field in the interface analysis data and a target interface value corresponding to the target interface field by using the sensitive data identification algorithm, for example:
target interface field: username + target interface field: paaswd;
alternatively, the target interface field: username + target interface field: the value of the number of pwd,
paaswd and pwd are both passwords, so paaswd and pwd are identified as user-password type sensitive data, and are desensitized, for example: the user cipher type is desensitized to. Similarly, the user id card type desensitization is 362133 × 4 × and the user mobile phone number type is: 189*****15.
As another example, when exporting the desensitization interface value, the server generates a temporary directory corresponding to the interface request address, generates a file of the interface request method field value + the file name of the UUID, writes the desensitization interface value in the file, and encrypts and packages the temporary directory by using the first encryption algorithm to obtain the first encrypted data. It can be understood that, because the interface field type corresponding to the target interface field is the sensitive field type, the server stores the desensitization interface value in the temporary directory, so that after the temporary directory is encrypted and packaged by using the first encryption algorithm, data in the temporary directory is deleted in time, and the security of the target interface field is improved. 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 file name of the UUID is generated under the temporary directory, a target interface value is written in 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 obtains an interface field type corresponding to each target interface field; if the interface field type is the sensitive field type, desensitizing 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 the non-sensitive field type, encrypting a target interface value corresponding to the non-sensitive field type to obtain second encrypted data; and target test data are obtained based on the first encrypted data and the second encrypted data, so that the safety of the user target test data can be improved.
In one embodiment, as shown in fig. 7, in step S14, loading the system simulation parameters into the original simulation system to obtain the target simulation system includes:
s71: and carrying out interface association identification on the system simulation parameters to obtain an associated interface field and an associated interface value.
S72: and performing 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.
And the associated interface field is obtained by performing interface association identification on the system simulation parameter. The correlation interface value is a value corresponding to an interface field obtained after interface correlation identification is carried out on the system simulation parameter. The associated interface data is data obtained by performing key value association on the associated interface field and the associated interface value.
As an example, in a real business system, that is, in a target system, a server adds or modifies data in the target system through POST/PULL, and then acquires the added or modified data in the target system through a GET method or DELETEs the data in the target system through DELETE, but if a target interface field in the target simulation system and a target interface value corresponding to the target interface field are not keyed, the server may not normally call the target simulation system after the target interface field and the target interface value corresponding to the target interface field are deleted. Therefore, the server adopts an incidence relation identification algorithm to perform interface incidence identification on the system simulation parameters, obtain incidence interface fields and incidence interface values, perform key value association on the incidence interface fields and the incidence interface values, obtain incidence interface data, load the incidence 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 to obtain an associated interface field and an associated interface value; and performing 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 numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In an embodiment, a test system simulation apparatus is provided, and the test system simulation apparatus corresponds to the test system simulation method in the above embodiments one to 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 explained in detail as follows:
a request obtaining module 10, configured to obtain a system simulation request, where the system simulation request includes a system creation parameter;
the system creating module 20 is configured to create an empty test system corresponding to the system creating parameter based on the system creating 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;
and the parameter loading module 40 is used for loading the system simulation parameters into the original simulation system to 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 identification, and the first data acquisition request comprises the original system identification 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 submodule is used for acquiring a target interface value corresponding to at least one target interface field from the interface editing page;
and the first parameter determining submodule is used for determining the target interface value corresponding to at least one target interface field as the system simulation parameter corresponding to the original system identification.
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, and the second data acquisition request comprises a target database address;
the information table acquisition submodule is used for acquiring a target interface information table from a target database based on the address of the target database;
the second interface acquisition submodule 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;
and the second parameter determining submodule is used for determining the target interface value corresponding to the at least one target interface field as the system simulation parameter corresponding to the original system identification.
Further, the parameter obtaining module 30 includes:
a third request submodule, 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 judgment submodule is used for inquiring the system database based on the target system identifier and judging whether historical test data corresponding to the target system identifier exist or not;
a third parameter determining submodule, 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 determining submodule is used for acquiring target test data corresponding to the target system identifier by adopting a 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 parameters 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 encrypting the interface analysis data, acquiring 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:
the field type subunit is used for acquiring the interface field type corresponding to each target interface field;
the desensitization processing subunit is used for desensitizing a target interface value corresponding to the sensitive field type to obtain a desensitization interface value and encrypting the desensitization interface value to obtain first encrypted data if the interface field type is the sensitive field type;
the first encryption subunit is used for encrypting a target interface value corresponding to the non-sensitive field type to acquire second encrypted data if the interface field type is the non-sensitive field type;
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 the system simulation parameters corresponding to the original system identification.
Further, the parameter loading module 40 includes:
the correlation identification submodule is used for carrying out interface correlation identification on the system simulation parameters and acquiring correlation interface fields and correlation interface values;
and the key value association submodule is used for performing 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 and obtaining the target simulation system.
For the specific definition of the test system simulation apparatus, reference may be made to the above definition of the test system simulation method, which is not described herein again. The modules in the test system simulation apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram 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 comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for testing system simulation. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a test system simulation method.
In one embodiment, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the test system simulation method in the foregoing embodiments is implemented, for example, steps S11 to S14, which are not repeated herein to avoid repetition. Alternatively, when the processor executes the computer program, the functions of the modules/units in the embodiment of the test system simulation apparatus, such as the request obtaining module 10, the system creating module 20, the parameter obtaining module 30, and the parameter loading module 40, are implemented, and for avoiding repetition, no further description is given here.
In an embodiment, a computer-readable storage medium is provided, and a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements the test system simulation method in the foregoing embodiments, for example, steps S11 to S14, which are not repeated herein for avoiding repetition. Alternatively, when being executed by the processor, the computer program implements the functions of the modules/units in the embodiment of the test system simulation apparatus, such as the request obtaining module 10, the system creating module 20, the parameter obtaining module 30, and the parameter loading module 40, which are not described herein again to avoid repetition.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile 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), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims (10)

1. A test system simulation method is characterized by comprising the steps executed by a test system:
acquiring a system simulation request, wherein the system simulation request comprises a system creation parameter;
based on the system creating parameters, creating an empty test system corresponding to the system creating 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 identification, and acquiring system simulation parameters corresponding to the original system identification based on the data acquisition request;
and loading the system simulation parameters into the original simulation system to obtain a target simulation system.
2. The test system simulation method of claim 1, wherein the forming a data acquisition request based on the original system identification, the acquiring system simulation parameters corresponding to the original system identification based on the data acquisition request, comprises:
forming a first data acquisition request based on the original system identification, wherein the first data acquisition request comprises the original system identification 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.
3. The test system simulation method of claim 1, wherein the forming a data acquisition request based on the original system identification, the acquiring system simulation parameters corresponding to the original system identification based on the data acquisition request, comprises:
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 at least one target interface value corresponding to the target interface field from the target interface information table;
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.
4. The test system simulation method of claim 1, wherein the forming a data acquisition request based on the original system identification, the acquiring system simulation parameters corresponding to the original system identification based on the data acquisition request, comprises:
forming a third data acquisition request based on the original system identification, wherein the third data acquisition request comprises a target system identification;
inquiring a system database based on the target system identification, and judging whether historical test data corresponding to the target system identification exist 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;
and if the historical test data corresponding to the target system identification does not exist, acquiring 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 system simulation parameters corresponding to the original system identification.
5. The method for simulating a test system according to claim 4, wherein the step of acquiring target test data corresponding to the target system id based on the target system id by using a preset test data acquisition logic and determining the target test data as the system simulation parameters corresponding to the original system id comprises:
testing a target system corresponding to the target system identification, 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.
6. The test system simulation method of claim 5, wherein the interface resolution 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 system simulation parameters corresponding to the original system identifier, including:
acquiring an interface field type corresponding to each target interface field;
if the interface field type is a sensitive field type, desensitizing 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 system simulation parameters corresponding to the original system identification.
7. The test system simulation method of claim 1, wherein the loading the system simulation parameters into the original simulation system to obtain a target simulation system comprises:
performing interface correlation identification on the system simulation parameters to acquire correlation interface fields and correlation interface values;
and performing 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 a target simulation system.
8. A test system simulator, comprising:
the request acquisition module is used for acquiring a system simulation request, and the system simulation request comprises system creation parameters;
the system creating module is used for creating an empty test system corresponding to the system creating parameters based on the system creating parameters and determining the empty test system as an original simulation system, and the original simulation system comprises an original system identifier;
a parameter obtaining module, 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;
and the parameter loading module is used for loading the system simulation parameters into the original simulation system to obtain a target simulation system.
9. 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 one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out a test system simulation method according to any one of claims 1 to 7.
CN202011627382.2A 2020-12-30 2020-12-30 Test system simulation method, device, computer equipment and storage medium Active CN112711538B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011627382.2A CN112711538B (en) 2020-12-30 2020-12-30 Test system simulation method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011627382.2A CN112711538B (en) 2020-12-30 2020-12-30 Test system simulation method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112711538A true CN112711538A (en) 2021-04-27
CN112711538B CN112711538B (en) 2024-03-19

Family

ID=75547667

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011627382.2A Active CN112711538B (en) 2020-12-30 2020-12-30 Test system simulation method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112711538B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108804336A (en) * 2018-06-15 2018-11-13 深圳壹账通智能科技有限公司 Interactive system test method, device, computer equipment and storage medium
CN109634837A (en) * 2018-10-23 2019-04-16 平安科技(深圳)有限公司 Automated testing method, device, equipment and storage medium
CN110399159A (en) * 2019-07-23 2019-11-01 广州夏达信息科技有限公司 Dispositions method, device, computer equipment and the storage medium of operating system
WO2020119434A1 (en) * 2018-12-15 2020-06-18 深圳壹账通智能科技有限公司 Method and apparatus for interface data processing, method and apparatus for automated testing, device, and medium
WO2020150194A1 (en) * 2019-01-15 2020-07-23 Qomplx, Inc. Multi-model generative simulation modeling of complex adaptive systems

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108804336A (en) * 2018-06-15 2018-11-13 深圳壹账通智能科技有限公司 Interactive system test method, device, computer equipment and storage medium
CN109634837A (en) * 2018-10-23 2019-04-16 平安科技(深圳)有限公司 Automated testing method, device, equipment and storage medium
WO2020119434A1 (en) * 2018-12-15 2020-06-18 深圳壹账通智能科技有限公司 Method and apparatus for interface data processing, method and apparatus for automated testing, device, and medium
WO2020150194A1 (en) * 2019-01-15 2020-07-23 Qomplx, Inc. Multi-model generative simulation modeling of complex adaptive systems
CN110399159A (en) * 2019-07-23 2019-11-01 广州夏达信息科技有限公司 Dispositions method, device, computer equipment and the storage medium of operating system

Also Published As

Publication number Publication date
CN112711538B (en) 2024-03-19

Similar Documents

Publication Publication Date Title
CN110990205B (en) Interface call testing method, device and computer readable storage medium
US10291631B2 (en) System for testing computer application
CN111756729B (en) Network resource access method, device, computer equipment and storage medium
WO2020181839A1 (en) Page data testing method, apparatus, computer device, and storage medium
WO2020253061A1 (en) Page generating method and apparatus, computer device, and storage medium
CN111475824B (en) Data access method, device, equipment and storage medium
CN110363026B (en) File operation method, device, equipment, system and computer readable storage medium
CN109669859B (en) Service testing method, device, computer equipment and storage medium
WO2019144549A1 (en) Vulnerability testing method and device, computer equipment, and storage medium
CN110727935B (en) Single sign-on method, system, computer device and storage medium
CN110245505A (en) Tables of data access method, device, computer equipment and storage medium
CN110889131B (en) File sharing system
CN110597709A (en) Interactive debugging method and device for mixed-mode mobile application and computer equipment
CN115277143A (en) Data secure transmission method, device, equipment and storage medium
CN107645474B (en) Method and device for logging in open platform
CN110647736A (en) Plug-in agent system login method and device, computer equipment and storage medium
CN112650689A (en) Test method, test device, electronic equipment and storage medium
CN112559352A (en) Interface test method, device, equipment and storage medium
CN112711538B (en) Test system simulation method, device, computer equipment and storage medium
CN113114681B (en) Test message processing method, device, computer system and readable storage medium
WO2019019675A1 (en) Simulated website login method and apparatus, server end and readable storage medium
CN110401674B (en) Data access method, device, system, electronic equipment and computer readable medium
CN112711505B (en) Test data acquisition method, device, computer equipment and storage medium
CN114189553B (en) Flow playback method, system and computing device
CN114710338B (en) MITM-based interactive hijacking method, device, electronic equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant