CN115407981A - Front-end data mock method and system based on middleware adaptation - Google Patents
Front-end data mock method and system based on middleware adaptation Download PDFInfo
- Publication number
- CN115407981A CN115407981A CN202211076445.9A CN202211076445A CN115407981A CN 115407981 A CN115407981 A CN 115407981A CN 202211076445 A CN202211076445 A CN 202211076445A CN 115407981 A CN115407981 A CN 115407981A
- Authority
- CN
- China
- Prior art keywords
- api
- data
- directory
- request
- file
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention relates to a front-end data mock method and a system based on middleware adaptation.A pre-set middleware is used for carrying out matching judgment on a mock request and executing a corresponding data processing feedback requested mock data model, and no dependence tool library of any third party is required to be installed through npm, so that no invasion is caused to project codes; meanwhile, multi-model output is supported, such as file flow, picture base64, base64 format messages and inside encryption type messages; the front-end engineer can directly call the data mock service by using the method of the invention, and can obtain the desired model information by transmitting the corresponding data model type according to the own service scene.
Description
Technical Field
The invention relates to the technical field of software program front-end development and testing, in particular to a front-end data mock method and system based on middleware adaptation.
Background
Mock is a common technical mode in front-end development and test work, and under the prior art, the Mock mode mainly adopted comprises:
1) In the front-end engineering, a mock file directory is newly established, and a request is directly sent to read a local mock file in the service processing process so as to achieve the purpose of simulating data return and testing;
2) Js, etc. implement mock functionality using third party open-sourced tool libraries or platforms such as Yapi, mock.
With the update and iteration of the front-end technology in recent years, the tool functions of some third parties for providing the interface mock are increasingly powerful, for example, the configurable function of Yapi and the random data generation function of mock. However, the following problems still exist in the prior art:
1) The created mock data has no storage operation, and subsequent data tracking, changing, comparing and other operations cannot be carried out;
2) Data models that do not support static file types, such as files, pictures, etc.;
3) The most of the derived data is in the json format of a plaintext, and a data model outputting various encryption formats is not supported;
4) Each time data is changed, manual reconfiguration is needed; dynamic data export operation can not be achieved according to different service parameters.
Due to the above problems in the prior art, it is difficult to implement the necessary mock function in some special front-end development test scenarios using the prior art, for example:
1) The method can not adapt to different product lines simultaneously, and the adaptation (base 64, inside) of the message encryption mode of the interface (api) can not be used when the encryption and decryption modes of different apis are involved. For example, for a specific service a, a base64 encryption processing mode is used, and for a specific service B, an intra-row inside mode api is used for access, when 2 service lines relate to a cross-interaction scenario, a third party library and a tool in the prior art cannot dynamically support 2 different data encryption and decryption modes, and a corresponding data model is dynamically matched and output. For such application scenarios, only developers can modify configuration and verify data manually in sequence, and service a and service B are tested in sequence, so that the operation experience is very unfriendly. And the local development link carries out multi-service connectivity test, which is time-consuming and labor-consuming and affects the throughput rate and the development efficiency of the service.
2) Mock simulation of static resource files (img-base 64, file files, etc.) is not supported.
3) The data desired by the user cannot be dynamically output, and only the interface configuration and the output message parameter configuration can be manually changed for one time, so that the development efficiency is seriously influenced. Especially for similar data models, the configuration still needs to be repeated each time it is invoked. For example, a new api-2 needs to be added to the existing api-1 data model, and the api-2 essentially adds a certain attribute on the basis of the api-1 data model, but the whole data model still needs to be reconfigured to obtain the desired data model, and the already existing identity of the api-1 cannot be dynamically added.
On the other hand, because of the existing front-end engineering standard, http requests in projects are subjected to independent unified packaging processing, an existing tool library or a third-party platform is used in actual services, writing can be performed only according to the third-party document specification, and the http packaging writing method in the projects cannot be matched, so that the existing project codes are inevitably invaded. Correspondingly, after debugging in the development link, restoring the code again to the http call of normal service encapsulation. Such intrusion modification and recovery operations are highly error prone, posing additional code bug risks.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a front-end data mock method and a system based on middleware adaptation, which do not need to install any third-party dependent tool library through npm and do not have any invasion to project codes; meanwhile, multi-model output is supported, such as file flow, picture base64, base64 format messages and inside encryption type messages; the front-end engineer can directly call the data mock service by using the method of the invention, and can obtain the desired model information by transmitting the corresponding data model type according to the own service scene.
In order to achieve the above purpose, the technical scheme adopted by the invention comprises the following steps:
a front-end data mock method based on middleware adaptation is characterized by comprising the following steps:
s1, configuring a middleware, and generating a preset api path data configuration file, an initial routers directory and an api directory corresponding to the routers directory;
s2, calling a middleware according to the mock request, and extracting matching parameter contents in the mock request, wherein the matching parameter contents comprise a requested api path, a requested mode, requested feedback original data and a data processing type corresponding to the original data;
s3, judging whether the requested api path exists in an api directory, and when judging that the requested api path exists in the api directory, terminating the mock request execution and feeding back first error information;
s4, when the fact that the requested api path does not exist in the api directory is judged, naming a new corresponding first js file in the api directory by using the requested api path and updating an api path data configuration file;
s5, monitoring the change of the api path data configuration file, naming and creating a corresponding second js file in the routers directory by using the requested api path, and registering a corresponding http request according to a request mode;
s6, calling original data according to the original data fed back by the request and the data processing type corresponding to the original data by using an http request, and executing processing on the original data to generate a data model;
and S7, storing the data model to a first js file, and feeding back the mock request by using the first js file.
Further, the determining whether the api path of the request already exists in the api directory includes:
traversing the api directory to obtain the file name existing in the api directory;
newly building a verification array, and adding the existing file name in the api directory into the verification array;
the api path match validation array of the request is used to determine if it already exists in the api directory.
Further, the first error information includes a change api path hint.
Further, the naming of the new corresponding second js file in the routers directory by using the api path of the request comprises naming the second js file by using the api path of the request in a Router combination mode;
the second js file corresponds to a routers instance.
Further, the step S5 further includes:
verifying whether the original data fed back by the request and the data processing type corresponding to the original data meet the api path data configuration file, and when the verification fails, terminating the mock request execution and feeding back second error information;
and when the verification is passed, naming and creating a second js file corresponding to the new request in the routers directory by using the api path of the request, and registering a corresponding http request according to a request mode.
Further, the data processing types comprise data encryption, data format packaging and data conversion.
The invention also relates to a front-end data mock system based on middleware adaptation, which is characterized in that the system is provided with a middleware, and the middleware comprises:
the api path data configuration file management module is used for generating a preset api path data configuration file and managing and modifying the preset api path data configuration file;
the catalog management module is used for generating and modifying the routers catalog and the api catalog;
the request processing module is used for extracting the matching parameter content in the mock request;
the first judging module is used for judging whether the requested api path exists in the api directory;
the first execution module is used for creating, managing and modifying the first js file;
the second execution module is used for creating, managing and modifying the second js file and registering a corresponding http request according to a request mode;
and the data processing module is used for calling the original data according to the original data fed back by the request and the data processing type corresponding to the original data by using the http request, executing processing on the original data and generating a data model.
The invention also relates to a computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the above-mentioned method.
The invention also relates to an electronic device, characterized in that it comprises a processor and a memory;
the memory is used for storing an api path data configuration file, a routers directory and an api directory;
the processor is used for executing the method by calling the api path data configuration file, the routers directory and the api directory.
The invention also relates to a computer program product comprising a computer program and/or instructions, characterized in that the computer program and/or instructions, when executed by a processor, implement the steps of the above-mentioned method.
The beneficial effects of the invention are as follows:
by adopting the front-end data mock method and the system based on middleware adaptation, a dependency tool library of any third party is not required to be installed through npm, and no invasion is caused to project codes; meanwhile, multi-model output is supported, such as file flow, picture base64, messages in base64 format and messages in inside encryption type; the front-end engineer can directly call the data mock service by using the method of the invention, and can obtain the desired model information by transmitting the corresponding data model type according to the own service scene.
Drawings
Fig. 1 is a schematic flowchart of a front-end data mock method based on middleware adaptation according to the present invention.
Fig. 2 is a schematic structural diagram of a front-end data mock system based on middleware adaptation according to the present invention.
Detailed Description
For a clearer understanding of the contents of the present invention, reference will be made to the accompanying drawings and examples.
The first aspect of the present invention relates to a front-end data mock method based on middleware adaptation, whose step flow is shown in fig. 1, including:
s1, configuring a middleware, and generating a preset api path data configuration file, an initial routers directory and an api directory corresponding to the routers directory.
The api directory has dynamic creation capability and is mapped to the routers directory.
For example, a user accesses a terminal page and submits a request parameter as follows:
params＝{type:’post’,apiUrl:’getUserName’,dataType:’base64’,data:”{‘a’:1,’b’:2}”}
correspondingly, the middleware can parse params and dynamically create a getUserName.js file under the api directory.
And S2, calling a middleware according to the mock request, and extracting matching parameter contents in the mock request, wherein the matching parameter contents comprise the requested api path, the request mode, the requested feedback original data and the data processing type (such as common data processing types of data encryption, data format packaging, data conversion and the like) corresponding to the original data.
Specifically, when the service receives a user action request (mock request), the middleware is called to capture parameter information submitted by the user, and the parameter information includes 4 main fields: apiUrl (api pathname of subsequent request), type (http request mode get, post, etc.), data (original json string data that needs to be processed back), dataType (type of data processing).
And S3, judging whether the requested api path exists in the api directory, and when judging that the requested api path exists in the api directory, terminating the mock request execution and feeding back the first error information.
Specifically, in order to facilitate operation during the determination, the api directory may be traversed, the file name existing under the api directory is obtained, a verification array is newly created, the file name existing under the api directory is added to the verification array, and then the requested api path is used to match the verification array to determine whether the file name exists in the api directory. Preferably, the existing file name can be stored in an array by executing a preset Create-Api-module method, for example:
apiFileNameArray＝[‘api1.js’,’api2.js’,’api3.js’,’api4.js’,’api5.js’...]
and then can judge whether the apiUrl transmitted by the currently received action is already in the apiFileNamearray.
In order to be able to prompt the user more specifically, the first error message preferably comprises a change api path prompt, in particular a prompt returned to the client prompting the user to change the incoming apiUrl nomenclature.
And S4, when the requested api path is judged not to exist in the api directory, naming a new corresponding first js file in the api directory by using the requested api path and updating an api path data configuration file, wherein the first js file is used for storing a data model returned after subsequent data processing.
S5, monitoring the change of the api path data configuration file, naming a new corresponding second js file in a routers directory by using the requested api path in an api path combination Router mode, wherein the second js file corresponds to a routers instance, and registering a corresponding http request according to a request mode.
Preferably, before the second js file is actually created, whether the original data requested to be fed back and the data processing type corresponding to the original data meet the api path data configuration file or not can be verified, and when the verification fails, the mock request execution is terminated and second error information is fed back; and when the verification is passed, newly creating a second js file.
And calling the corresponding data processor according to the dataType, distributing the dataType to the corresponding data processing plant, calling the corresponding data module function, and performing conventional operations such as encryption, data format packaging, conversion and the like. Taking params exemplified in step S1 as an example: analyzing a prams.data Json character string as a Json object, and then calling base64 as an input parameter for encryption processing operation; the return result is a base64 encryption string, and data processing is completed. For other dataType types, the execution principle is the same.
S6, calling original data according to the original data fed back by the request and the data processing type corresponding to the original data by using an http request, and executing processing on the original data to generate a data model;
and S7, storing the data model to a first js file, and feeding back the mock request by using the first js file.
In particular, one may choose to expose the ctx.body for use by the caller after saving the data model in the first js file.
When the front-end data mock is actually implemented by using the method, a developer can integrate the method into a mock service tool and call the mock service tool, for example:
1. replacing the baseUrl requested in the project of the mobile terminal to be the address of the mock service tool;
2. locally accessing an address provided by the mock service, inputting data information needing configuration in a text field of a page, wherein the data information comprises a data export type, a request path of an interface api, a data set used by a service and the like, and clicking to submit;
3. corresponding to the input content, the server receives a request which comprises data information capable of being input by the user; after receiving the data information, calling an interceptor to match the type transmitted by the user, calling a data processing module corresponding to the type, and performing customized data processing; and associating the processed data with the url, creating a data mapping, storing the data mapping into a table of the database, and matching the url stored in the table when a user accesses the corresponding url to derive a data model in the table. And directly accessing the url of the data configured by the url in the project, so as to obtain the data { } data model information corresponding to the url.
In another aspect, the present invention further relates to a front-end data mock system based on middleware adaptation, whose structure is shown in fig. 2, including:
the api path data configuration file management module is used for generating a preset api path data configuration file and managing and modifying the preset api path data configuration file;
the catalog management module is used for generating and modifying the routers catalog and the api catalog;
the request processing module is used for extracting the matching parameter content in the mock request;
the first judging module is used for judging whether the requested api path exists in the api directory;
the first execution module is used for creating, managing and modifying the first js file;
the second execution module is used for creating, managing and modifying the second js file and registering a corresponding http request according to a request mode;
and the data processing module is used for calling the original data according to the original data fed back by the request and the data processing type corresponding to the original data by using the http request, executing processing on the original data and generating a data model.
Preferably, a distribution control module may be further configured to implement a function of distributing the request and the data.
By using this system, the above-described arithmetic processing method can be executed and a corresponding technical effect can be achieved.
Embodiments of the present invention also provide a computer-readable storage medium capable of implementing all the steps of the method in the above embodiments, the computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements all the steps of the method in the above embodiments.
Embodiments of the present invention further provide an electronic device for executing the method, as an implementation apparatus of the method, the electronic device at least has a processor and a memory, and particularly, the memory stores data and related computer programs, such as an api path data configuration file, a routers directory, an api directory, and the like, required for executing the method, and all steps of the implementation method are executed by calling the data and programs in the memory by the processor, and a corresponding technical effect is obtained.
Preferably, the electronic device may comprise a bus architecture, which may include any number of interconnected buses and bridges linking together various circuits including one or more processors and memory. The bus may also link various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter may be the same element, i.e., a transceiver, providing a means for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory may be used for storing data used by the processor in performing operations.
Additionally, the electronic device may further include a communication module, an input unit, an audio processor, a display, a power source, and the like. The processor (or controller, operation control) may include a microprocessor or other processor device and/or logic device, which receives input and controls the operation of various components of the electronic device; the memory may be one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices, and may store the above-mentioned related data information, and may also store a program for executing the related information, and the processor may execute the program stored in the memory to realize information storage or processing, etc.; the input unit is used for providing input to the processor, and can be a key or a touch input device; the power supply is used for supplying power to the electronic equipment; the display is used for displaying display objects such as images and characters, and may be an LCD display, for example. The communication module is a transmitter/receiver that transmits and receives signals via an antenna. The communication module (transmitter/receiver) is coupled to the processor to provide an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal. Based on different communication technologies, a plurality of communication modules, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be disposed in the same electronic device. The communication module (transmitter/receiver) is also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and receive audio input from the microphone to implement the usual telecommunication functions. The audio processor may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor is also coupled to the central processor, so that recording on the local machine can be performed through the microphone, and sound stored on the local machine can be played through the loudspeaker.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a system for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A front-end data mock method based on middleware adaptation is characterized by comprising the following steps:
s1, configuring a middleware, and generating a preset api path data configuration file, an initial routers directory and an api directory corresponding to the routers directory;
s2, calling a middleware according to the mock request, and extracting matching parameter contents in the mock request, wherein the matching parameter contents comprise a requested api path, a requested mode, requested feedback original data and a data processing type corresponding to the original data;
s3, judging whether the requested api path exists in an api directory, and when judging that the requested api path exists in the api directory, terminating the mock request execution and feeding back first error information;
s4, when the fact that the requested api path does not exist in the api directory is judged, naming a new corresponding first js file in the api directory by using the requested api path and updating an api path data configuration file;
s5, monitoring the change of the api path data configuration file, naming and creating a corresponding second js file in the routers directory by using the requested api path, and registering a corresponding http request according to a request mode;
s6, using an http request to call original data according to the original data fed back by the request and the data processing type corresponding to the original data, and performing processing on the original data to generate a data model;
and S7, storing the data model to a first js file, and feeding back the mock request by using the first js file.
2. The method of claim 1, wherein the determining whether the api path of the request already exists in an api directory comprises:
traversing the api directory to obtain the existing file name under the api directory;
creating a verification array, and adding the existing file name in the api directory into the verification array;
the api path match validation array of the request is used to determine if it already exists in the api directory.
3. The method of claim 1, wherein the first error information comprises a change api path hint.
4. The method of claim 1, wherein naming a new corresponding second js file in routers directory using the requested api path comprises naming a second js file using the requested api path in combination with Router;
the second js file corresponds to a routers instance.
5. The method of claim 4, wherein the step S5 further comprises:
verifying whether the original data fed back by the request and the data processing type corresponding to the original data meet the api path data configuration file, and when the verification fails, terminating the execution of the mock request and feeding back second error information;
and when the verification is passed, naming and creating a second js file corresponding to the new request in the routers directory by using the api path of the request, and registering a corresponding http request according to a request mode.
6. The method of claim 1, wherein the data processing types include data encryption, data format wrapping, and data conversion.
7. A front-end data mock system based on middleware adaptation is characterized in that a middleware is provided, and the middleware comprises:
the api path data configuration file management module is used for generating a preset api path data configuration file and managing and modifying;
the catalog management module is used for generating and modifying the routers catalog and the api catalog;
the request processing module is used for extracting the matching parameter content in the mock request;
the first judgment module is used for judging whether the requested api path exists in the api directory;
the first execution module is used for creating, managing and modifying the first js file;
the second execution module is used for creating, managing and modifying the second js file and registering a corresponding http request according to a request mode;
and the data processing module is used for calling the original data according to the original data fed back by the request and the data processing type corresponding to the original data by using the http request, executing processing on the original data and generating a data model.
8. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 6.
9. An electronic device comprising a processor and a memory;
the memory is used for storing an api path data configuration file, a routers directory and an api directory;
the processor to perform the method of any of claims 1 to 6 by calling an api path data configuration file, a routers directory, and an api directory.
10. A computer program product comprising a computer program and/or instructions, characterized in that the computer program and/or instructions, when executed by a processor, implement the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211076445.9A CN115407981A (en) | 2022-09-05 | 2022-09-05 | Front-end data mock method and system based on middleware adaptation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211076445.9A CN115407981A (en) | 2022-09-05 | 2022-09-05 | Front-end data mock method and system based on middleware adaptation |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115407981A true CN115407981A (en) | 2022-11-29 |
Family
ID=84164729
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211076445.9A Pending CN115407981A (en) | 2022-09-05 | 2022-09-05 | Front-end data mock method and system based on middleware adaptation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115407981A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116414366A (en) * | 2023-04-17 | 2023-07-11 | 广东企企通科技有限公司 | Middleware interface generation method, device, equipment and medium |
-
2022
- 2022-09-05 CN CN202211076445.9A patent/CN115407981A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116414366A (en) * | 2023-04-17 | 2023-07-11 | 广东企企通科技有限公司 | Middleware interface generation method, device, equipment and medium |
| CN116414366B (en) * | 2023-04-17 | 2024-01-30 | 广东企企通科技有限公司 | Middleware interface generation method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10705942B1 (en) | Simulated testing of API | |
| CN111078539B (en) | Test method, device, system and computer readable storage medium | |
| US10824549B1 (en) | System and method for regression testing of an application programming interface | |
| CN104503780A (en) | Method and device for providing application channel packet | |
| TW201439792A (en) | System and method for accessing database | |
| WO2020211360A1 (en) | Mock test method and system, electronic device, and computer non-volatile readable storage medium | |
| CN108984202B (en) | Electronic resource sharing method and device and storage medium | |
| CN110543301A (en) | Method and device for generating jenkins code file | |
| CN115407981A (en) | Front-end data mock method and system based on middleware adaptation | |
| CN113238965B (en) | Interface test script generation method, system and storage medium | |
| CN112905460B (en) | Device and method for simulating three-party receipt by automatic interface test | |
| US11368554B2 (en) | Systems and methods for regulating service behavior | |
| CN113778897A (en) | Automatic test method, device, equipment and storage medium of interface | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN112988600A (en) | Service scene testing method and device, electronic equipment and storage medium | |
| CN111078527B (en) | Auxiliary system and method for pressure testing of server | |
| CN115567596A (en) | Cloud service resource deployment method, device, equipment and storage medium | |
| CN114677138A (en) | Data processing method, data processing equipment and computer readable storage medium | |
| CN114035786A (en) | Dependency-based micro-front-end compatible migration method and system | |
| CN113553271A (en) | Method for generating and testing internal test program of application program | |
| CN114595446A (en) | Method for realizing dynamically configurable interface joint debugging sandbox | |
| CN114244830B (en) | File gateway application nonfunctional testing method and system | |
| CN115914219A (en) | Task request processing method, device and system, readable storage medium and electronic equipment | |
| CN115186021A (en) | Configuration management database generation method and device | |
| CN117544549A (en) | Production line testing method, device, equipment and storage 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 |