CN106648945B - Interface data testing method and device and electronic equipment - Google Patents

Interface data testing method and device and electronic equipment Download PDF

Info

Publication number
CN106648945B
CN106648945B CN201610873345.7A CN201610873345A CN106648945B CN 106648945 B CN106648945 B CN 106648945B CN 201610873345 A CN201610873345 A CN 201610873345A CN 106648945 B CN106648945 B CN 106648945B
Authority
CN
China
Prior art keywords
file
interface data
format file
binary format
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.)
Expired - Fee Related
Application number
CN201610873345.7A
Other languages
Chinese (zh)
Other versions
CN106648945A (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.)
Beijing Kingsoft Internet Security Software Co Ltd
Original Assignee
Beijing Kingsoft Internet Security Software 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 Beijing Kingsoft Internet Security Software Co Ltd filed Critical Beijing Kingsoft Internet Security Software Co Ltd
Priority to CN201610873345.7A priority Critical patent/CN106648945B/en
Publication of CN106648945A publication Critical patent/CN106648945A/en
Application granted granted Critical
Publication of CN106648945B publication Critical patent/CN106648945B/en
Expired - Fee Related 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/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751Error or fault detection not based on redundancy

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the invention discloses an interface data testing method, an interface data testing device and electronic equipment, relates to an interface testing technology, and can improve the function testing efficiency. The interface data testing method comprises the following steps: constructing a simulation server for interface data testing; setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file; calling a pre-written file conversion script in the simulation server, and storing a target protocol format file in a binary format of a non-binary format file; and acquiring the target protocol format file according to the data exception test flow so as to carry out data exception test. The invention is suitable for carrying out function test on the interface.

Description

Interface data testing method and device and electronic equipment
Technical Field
The present invention relates to interface testing technologies, and in particular, to a method and an apparatus for testing interface data, and an electronic device.
Background
With the continuous development of computer communication and internet technologies, more and more applications are developed, more and more interfaces are developed in each application, and each application performs data transmission through a corresponding interface, for example, an X interface of one application needs to call a Y interface of another application to acquire data for interaction. Before the two interfaces transmit data to each other, the two parties agree with each other in a data communication format.
Google cache Protocol (Google Protocol Buffer) provides a data description language for Google (Google) corporation, can use a structured data sequence in the fields of data storage, communication protocols and the like, and is a serialized structured data format which is independent of language and platform and can be expanded. The most important characteristic is that data is stored based on binary system, so that compared with the traditional Extensible Markup Language (XML) data storage format or lightweight data exchange format (JSON, JavaScript Object notification), the data access code has small data volume (for example, the size of a Protobuf message only needs 1/10-1/3 of XML), high parsing speed (the parsing speed is 20-100 times faster than XML), and good downward or upward compatibility, and can be generated by using a compiler of Protobuf, so that the data access code is a light and efficient structured data storage format, and is widely applied to data storage or data exchange of Remote Procedure Call (RPC), for example, data exchange between interfaces.
However, for a newly developed interface, normal function test and abnormal function test are required to collect function test data, so as to verify whether the developed interface is correct, whether the interface operates stably, and interface functions such as a processing mechanism of the interface on abnormal data, so as to optimize the developed interface function. And the Protobuf file is used as a data transmission format between interfaces, and because the test data in the Protobuf file node is binary data, the specific content of the test data cannot be directly obtained, when the test data of the node needs to be modified to perform an abnormal test, the binary character string in which range is in the test data of the target node to be modified cannot be obtained, so that the functional test efficiency is low.
Disclosure of Invention
In view of this, embodiments of the present invention provide an interface data testing method and apparatus, and an electronic device, which can improve functional testing efficiency, so as to solve a problem of low functional testing efficiency in an existing interface data testing method, when test data of a node needs to be modified for performing an exception test, because test data in a Protobuf file node is binary data, it is impossible to know which range of binary character strings is test data of a target node to be modified.
In a first aspect, an embodiment of the present invention provides an interface data testing method, including:
constructing a simulation server for interface data testing;
setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file;
calling a pre-written file conversion script in the simulation server, and storing a target protocol format file in a binary format of a non-binary format file;
and acquiring the target protocol format file according to the data exception test flow so as to carry out data exception test.
With reference to the first aspect, in a first implementation manner of the first aspect, before invoking a file conversion script written in advance in the simulation server and converting a stored non-binary format file into a binary format target protocol format file, the method further includes:
and modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the modifying interface data test parameters of nodes in the non-binary format file includes:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
With reference to the first aspect or the first implementation manner of the first aspect, in a third implementation manner of the first aspect, the non-binary format file is a lightweight data exchange format file or an extensible markup language file.
With reference to the first aspect or the first implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the file conversion script is an object-oriented, interpreted computer programming language script.
In a second aspect, an embodiment of the present invention provides an interface data testing apparatus, including: a simulation server construction module, a parameter setting module, a file conversion module and a test module, wherein,
the simulation server construction module is used for constructing a simulation server for interface data testing;
the parameter setting module is used for setting interface data testing parameters in the simulation server and storing the interface data testing parameters as a non-binary format file;
the file conversion module is used for calling a file conversion script written in advance in the simulation server and storing a target protocol format file in a non-binary format file binary format;
and the test module is used for acquiring the target protocol format file according to the data exception test flow so as to carry out data exception test.
With reference to the second aspect, in a first implementation manner of the second aspect, the apparatus further includes:
and the parameter editing module is used for modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
With reference to the first implementation manner of the second aspect, in a second implementation manner of the second aspect, the modifying interface data test parameters of nodes in the non-binary format file includes:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
With reference to the second aspect or the first implementation manner of the second aspect, in a third implementation manner of the second aspect, the non-binary format file is a lightweight data exchange format file or an extensible markup language file.
With reference to the second aspect or the first implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the file conversion script is an object-oriented, interpreted computer programming language script.
In a third aspect, an embodiment of the present invention provides an electronic device, where the electronic device includes: the device comprises a shell, a processor, a memory, a circuit board and a power circuit, wherein the circuit board is arranged in a space enclosed by the shell, and the processor and the memory are arranged on the circuit board; a power supply circuit for supplying power to each circuit or device of the electronic apparatus; the memory is used for storing executable program codes; the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, and is used for executing any one of the interface data testing methods.
According to the interface data testing method, the interface data testing device and the electronic equipment, a simulation server for interface data testing is constructed; setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file; calling a pre-written file conversion script in the simulation server, and storing a target protocol format file in a binary format of a non-binary format file; according to the data anomaly test flow, the target protocol format file is obtained to carry out data anomaly test, so that the functional test efficiency can be improved, and the problem that in the existing interface data test method, when the test data of the node needs to be modified to carry out the anomaly test, the functional test efficiency is not high because the test data in the Protobuf file node is binary data, and the binary character string in which range is not known as the test data of the target node to be modified can be solved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a method for testing interface data according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a second interface data testing apparatus according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an embodiment of an electronic device according to the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. 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.
Fig. 1 is a schematic flow chart of an interface data testing method according to an embodiment of the present invention, and as shown in fig. 1, the method according to the embodiment may include:
step 101, constructing a simulation server for interface data testing;
in this embodiment, the constructed simulation server (mock server) serves as an upstream application, the format of test data negotiated and used by the upstream application and a downstream application serving as a test is a Protobuf format, and a structure description file (. proto file) is shared.
In this embodiment, the simulation server is a server that responds to a request, for example, a data test request, and returns a response to an interface that sends test data, and is used to simulate to obtain different result return values.
In this embodiment, as an optional embodiment, the constructed simulation server has the following functions:
and A, generating a file corresponding to an object-oriented and interpreted computer programming language (Python) format by using a Protobuf file defined by an interface.
In this embodiment, as an optional embodiment, the file in the Python format is a py file. Python is an open source programming language that is not limited, cross-platform. In this embodiment, the command line for generating the py file is as follows:
protoc--proto_path=ufs_proto/ufs_proto/user_profile.proto--python_out=.
wherein,
profile is the profile defined by the interface, ufs _ profile/ufs _ profile/user _ profile.
And B, calling a pre-written file conversion script, namely a python script, to convert the non-binary format file, for example, a JSON file into a binary format Protobuf file.
And C, returning the test result in a binary format.
In this embodiment, as an optional embodiment, the simulation server is constructed by using an object-oriented, interpreted computer programming language web page framework.
In this embodiment, the object-oriented interpreted computer programming language web frame (Webpy) is a lightweight open-source python web frame, which can quickly implement a web page and facilitate setting of interface data test parameters.
102, setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file;
in this embodiment, virtual test data for interface function testing is constructed in the simulation server, and then the constructed test data is saved as a JSON file.
In this embodiment, as an optional embodiment, the non-binary format file is a lightweight data interchange format file (JSON file) or an extensible markup language file (XML file), and the like, and this embodiment does not limit this.
103, calling a file conversion script written in advance in the simulation server, and storing a target protocol format file in a non-binary format file binary format;
in this embodiment, as an optional embodiment, the file conversion script is a python script.
And 104, acquiring the target protocol format file according to the data exception test flow to perform data exception test.
In this embodiment, as an optional embodiment, a downstream interface may be assigned to the simulation server to obtain upstream data.
In this embodiment, as an optional embodiment, before calling a file conversion script written in advance in the simulation server and converting a stored non-binary format file into a binary format target protocol format file, the method further includes:
and modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
In this embodiment, as an optional embodiment, modifying the interface data test parameters of the nodes in the non-binary format file includes:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
In this embodiment, if an abnormal case needs to be constructed, only the relevant content in the corresponding JSON file needs to be modified according to the test result. Certainly, in practical application, related content in a non-binary format file (JSON file) may also be modified directly, and then, it is determined whether an expected exception test purpose is achieved according to a test result, for example, if an upstream interface needs to be verified, if a certain preset necessary node is absent in the returned test result content, and if a downstream interface discards dirty data, the preset necessary node (all interface data test parameters of the preset necessary node) may be deleted by modifying the JSON file, then, a python script is called, the modified JSON file is converted into a corresponding Protobuf format, and finally, the modified JSON file is output in a binary format, and a request is initiated by the downstream interface to obtain the related content in the test result file in the binary format. For another example, if the upstream interface needs to be verified, the node attribute value in the returned test result content is illegal, and if the downstream interface discards dirty data, the node attribute value can be modified (the attribute data test parameter corresponding to the preset node) in the JSON file, then a python script is called, the JSON file with the modified attribute value is converted into a corresponding Protobuf format, and finally the obtained product is output in a binary format, and the downstream interface initiates a request to obtain the relevant content in the test result file in the binary format.
In the interface data testing method of the embodiment, a simulation server for interface data testing is constructed; setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file; calling a file conversion script written in advance in the simulation server, and storing the contents of the non-binary format file, the contents of the file in the target protocol format in the binary format; and finally output in binary format. Therefore, by analyzing the non-binary format file, the binary character string in which range is the test data of the target node to be modified can be obtained, and then the modified file binary format target protocol format file is tested, so that the abnormal test can be performed on the interface of the Protobuf storage format, the predicted risk is reduced, and the functional test efficiency is effectively improved; furthermore, test data is modified on the webpage interface, so that the upstream and downstream interfaces can be tested without modifying codes, and time and cost required by functional test can be effectively reduced.
Fig. 2 is a schematic structural diagram of a second interface data testing apparatus according to an embodiment of the present invention, and as shown in fig. 2, the apparatus according to this embodiment may include: a simulation server construction module 21, a parameter setting module 22, a file conversion module 23, and a test module 24, wherein,
the simulation server building module 21 is used for building a simulation server for interface data testing;
in this embodiment, the constructed simulation server (mock server) serves as an upstream application, the format of test data negotiated and used by the upstream application and a downstream application serving as a test is a Protobuf format, and a structure description file (. proto file) is shared.
In this embodiment, as an optional embodiment, the simulation server is constructed by using an object-oriented, interpreted computer programming language web page framework.
The parameter setting module 22 is used for setting interface data testing parameters in the simulation server and storing the interface data testing parameters as a non-binary format file;
in this embodiment, virtual test data for interface function testing is constructed in the simulation server, and then the constructed test data is saved as a JSON file.
In this embodiment, as an optional embodiment, the non-binary format file is a lightweight data exchange format file or an extensible markup language file.
The file conversion module 23 is configured to call a file conversion script written in advance in the simulation server, and store a target protocol format file in a non-binary format file binary format;
in this embodiment, as an optional embodiment, a downstream interface may be assigned to the simulation server to obtain upstream data.
In this embodiment, as an optional embodiment, the file conversion script is an object-oriented, interpreted computer programming language script.
And the test module 24 is configured to obtain the target protocol format file according to the data exception test flow to perform a data exception test.
In this embodiment, as an optional embodiment, the apparatus further includes:
and the parameter editing module (not shown in the figure) is used for modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
In this embodiment, as an optional embodiment, modifying the interface data test parameters of the nodes in the non-binary format file includes:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
In this embodiment, if an abnormal case needs to be constructed, only the relevant content in the corresponding JSON file needs to be modified according to the test result.
The apparatus of this embodiment may be used to implement the technical solution of the method embodiment shown in fig. 1, and the implementation principle and the technical effect are similar, which are not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof.
In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
The embodiment of the invention also provides electronic equipment, and the electronic equipment comprises the device in any one of the embodiments.
Fig. 3 is a schematic structural diagram of an embodiment of an electronic device of the present invention, which can implement the processes of the embodiments shown in fig. 1-2 of the present invention, and as shown in fig. 3, the electronic device may include: the device comprises a shell 31, a processor 32, a memory 33, a circuit board 34 and a power circuit 35, wherein the circuit board 34 is arranged inside a space enclosed by the shell 31, and the processor 32 and the memory 33 are arranged on the circuit board 34; a power supply circuit 35 for supplying power to each circuit or device of the electronic apparatus; the memory 33 is used for storing executable program codes; the processor 32 executes a program corresponding to the executable program code by reading the executable program code stored in the memory 33, so as to execute the interface data testing method according to any one of the foregoing embodiments.
The specific execution process of the above steps by the processor 32 and the steps further executed by the processor 32 by running the executable program code may refer to the description of the embodiment shown in fig. 1-2 of the present invention, and are not described herein again.
The electronic device exists in a variety of forms, including but not limited to:
(1) a mobile communication device: such devices are characterized by mobile communications capabilities and are primarily targeted at providing voice, data communications. Such terminals include: smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) Ultra mobile personal computer device: the equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include: PDA, MID, and UMPC devices, etc., such as ipads.
(3) A portable entertainment device: such devices can display and play multimedia content. This type of device comprises: audio, video players (e.g., ipods), handheld game consoles, electronic books, and smart toys and portable car navigation devices.
(4) A server: the device for providing the computing service comprises a processor, a hard disk, a memory, a system bus and the like, and the server is similar to a general computer architecture, but has higher requirements on processing capacity, stability, reliability, safety, expandability, manageability and the like because of the need of providing high-reliability service.
(5) And other electronic equipment with data interaction function.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
For convenience of description, the above devices are described separately in terms of functional division into various units/modules. Of course, the functionality of the units/modules may be implemented in one or more software and/or hardware implementations of the invention.
From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The above description is only for the specific 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 included in 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 (11)

1. An interface data testing method, comprising:
constructing a simulation server for interface data testing;
setting interface data test parameters in a simulation server and storing the interface data test parameters as a non-binary format file;
calling a pre-written file conversion script in the simulation server, and converting the stored non-binary format file into a binary format target protocol format file;
and acquiring the target protocol format file according to the data exception test flow so as to carry out data exception test.
2. The method for testing interface data according to claim 1, wherein before calling a file conversion script written in advance in the simulation server to convert the stored non-binary format file into the binary format target protocol format file, the method further comprises:
and modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
3. The method for testing interface data according to claim 2, wherein said modifying test parameters of interface data of nodes in said non-binary format file comprises:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
4. The interface data testing method according to claim 1 or 2, wherein the non-binary format file is a lightweight data exchange format file or an extensible markup language file.
5. The interface data testing method of claim 1 or 2, wherein the file conversion script is an object-oriented, interpreted computer programming language script.
6. An interface data testing apparatus, comprising: a simulation server construction module, a parameter setting module, a file conversion module and a test module, wherein,
the simulation server construction module is used for constructing a simulation server for interface data testing;
the parameter setting module is used for setting interface data testing parameters in the simulation server and storing the interface data testing parameters as a non-binary format file;
the file conversion module is used for calling a file conversion script which is written in advance in the simulation server and converting the stored non-binary format file into a target protocol format file in a binary format;
and the test module is used for acquiring the target protocol format file according to the data exception test flow so as to carry out data exception test.
7. The interface data testing apparatus of claim 6, wherein the apparatus further comprises:
and the parameter editing module is used for modifying the interface data test parameters of the nodes in the non-binary format file according to the data exception test target.
8. The device for testing interface data according to claim 7, wherein said modifying test parameters of interface data of nodes in said non-binary format file comprises:
deleting specific node data in the non-binary format file; or
And modifying the attribute value corresponding to the specific node in the non-binary format file.
9. An interface data testing device according to claim 6 or 7, wherein the non-binary format file is a lightweight data interchange format file or an extensible markup language file.
10. An interface data testing arrangement according to claim 6 or 7, wherein the file conversion script is an object oriented, interpreted computer programming language script.
11. An electronic device, characterized in that the electronic device comprises: the device comprises a shell, a processor, a memory, a circuit board and a power circuit, wherein the circuit board is arranged in a space enclosed by the shell, and the processor and the memory are arranged on the circuit board; a power supply circuit for supplying power to each circuit or device of the electronic apparatus; the memory is used for storing executable program codes; the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, for executing the interface data testing method of any one of the preceding claims 1 to 5.
CN201610873345.7A 2016-09-30 2016-09-30 Interface data testing method and device and electronic equipment Expired - Fee Related CN106648945B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610873345.7A CN106648945B (en) 2016-09-30 2016-09-30 Interface data testing method and device and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610873345.7A CN106648945B (en) 2016-09-30 2016-09-30 Interface data testing method and device and electronic equipment

Publications (2)

Publication Number Publication Date
CN106648945A CN106648945A (en) 2017-05-10
CN106648945B true CN106648945B (en) 2019-10-15

Family

ID=58853632

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610873345.7A Expired - Fee Related CN106648945B (en) 2016-09-30 2016-09-30 Interface data testing method and device and electronic equipment

Country Status (1)

Country Link
CN (1) CN106648945B (en)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107329890A (en) * 2017-06-06 2017-11-07 北京金山安全软件有限公司 Test method and device based on Mock and server
CN109815107B (en) * 2017-11-22 2022-06-07 北京京东尚科信息技术有限公司 Method and device for automatic testing
CN110532305B (en) * 2018-05-23 2022-11-08 中国移动通信集团浙江有限公司 Service data cutting-over method and system
CN108804271A (en) * 2018-06-28 2018-11-13 北京潘达互娱科技有限公司 Interface tolerating measure method and device
CN108897691B (en) * 2018-06-29 2022-02-15 百度在线网络技术(北京)有限公司 Data processing method, device, server and medium based on interface simulation service
CN110750409A (en) * 2018-07-23 2020-02-04 北京奇虎科技有限公司 Method, device and system for realizing test
CN109656791B (en) * 2018-11-01 2022-07-12 奇安信科技集团股份有限公司 gPC performance test method and device based on Jmeter
CN111324526B (en) * 2018-12-14 2024-04-26 北京金山云网络技术有限公司 Interface test system, method and server
CN111629014B (en) * 2019-02-27 2023-03-24 北京嘀嘀无限科技发展有限公司 Request agent implementation method, implementation device, server and storage medium
CN110781082B (en) * 2019-10-14 2022-05-20 腾讯科技(深圳)有限公司 Method, device, medium and equipment for generating test case of interface
CN112783753B (en) * 2019-11-07 2024-04-12 北京沃东天骏信息技术有限公司 Testing method and device for stream data processing system
CN111078571B (en) * 2019-12-20 2024-02-02 广州品唯软件有限公司 Test method for analog response, terminal equipment and computer readable storage medium
CN111177003A (en) * 2019-12-30 2020-05-19 北京同邦卓益科技有限公司 Test method, device, system, electronic equipment and storage medium
CN111581097B (en) * 2020-05-09 2024-05-17 深圳市卡数科技有限公司 Performance test method, system, equipment and storage medium for parameterized data
CN113704079B (en) * 2020-05-22 2024-06-18 北京沃东天骏信息技术有限公司 Protobuf-based interface testing method and device
CN111651349B (en) * 2020-05-26 2023-07-14 泰康保险集团股份有限公司 Test method and device
CN112486811A (en) * 2020-11-26 2021-03-12 杭州安恒信息技术股份有限公司 Interface test method, device, equipment and medium
CN112491659B (en) * 2020-12-02 2022-07-01 广州品唯软件有限公司 Flow playback test method and device, computer equipment and storage medium
CN112612563A (en) * 2020-12-16 2021-04-06 上海哔哩哔哩科技有限公司 Page test data generation method and device and computer equipment
CN113742408B (en) * 2021-09-03 2024-02-02 唯品会(广州)软件有限公司 Protobuf protocol dynamic analysis-based data interaction method
CN116257398B (en) * 2023-05-11 2023-10-03 中星联华科技(北京)有限公司 Serial port testing method and system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185734A (en) * 2011-04-18 2011-09-14 华为软件技术有限公司 Automatic interface testing method and server
CN103136095A (en) * 2011-11-28 2013-06-05 阿里巴巴集团控股有限公司 Method, device and system of test application program interface
CN103970737A (en) * 2013-01-24 2014-08-06 腾讯科技(深圳)有限公司 Data constitution method and device
CN105897497A (en) * 2015-07-20 2016-08-24 广州华多网络科技有限公司 Interface test method, application device and service device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140108589A1 (en) * 2012-10-11 2014-04-17 Sanjeev Dhanda Testing an executable binary file using an injection proxy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102185734A (en) * 2011-04-18 2011-09-14 华为软件技术有限公司 Automatic interface testing method and server
CN103136095A (en) * 2011-11-28 2013-06-05 阿里巴巴集团控股有限公司 Method, device and system of test application program interface
CN103970737A (en) * 2013-01-24 2014-08-06 腾讯科技(深圳)有限公司 Data constitution method and device
CN105897497A (en) * 2015-07-20 2016-08-24 广州华多网络科技有限公司 Interface test method, application device and service device

Also Published As

Publication number Publication date
CN106648945A (en) 2017-05-10

Similar Documents

Publication Publication Date Title
CN106648945B (en) Interface data testing method and device and electronic equipment
CN111639287A (en) Page processing method and device, terminal equipment and readable storage medium
WO2020233369A1 (en) Method for improving software integration system on basis of simulated port, and related device
CN108920496B (en) Rendering method and device
CN105786455B (en) Data processing method and device and terminal
CN110955409B (en) Method and device for creating resources on cloud platform
CN113778897B (en) Automatic test method, device and equipment for interface and storage medium
CN113742014A (en) Interface rendering method and device, electronic equipment and storage medium
CN114996619A (en) Page display method and device, computer equipment and storage medium
CN106940714B (en) A kind of data processing method, device and electronic equipment
CN112631590A (en) Component library generation method and device, electronic equipment and computer readable medium
CN112365192A (en) Method for establishing flow model in manufacturing execution system, electronic device and method for analyzing flow model
US12056492B2 (en) Method and apparatus for generating dependence graph, device, storage medium and program product
CN116360735A (en) Form generation method, device, equipment and medium
CN113642295B (en) Page typesetting method, device and computer program product
CN116382640A (en) Method, device, equipment and storage medium for managing micro-service
US11797277B2 (en) Neural network model conversion method server, and storage medium
CN111539200B (en) Method, device, medium and electronic equipment for generating rich text
CN113419716A (en) Code generation method and device, terminal equipment and storage medium
CN105094773B (en) The method for reusing and system of functions of modules
CN112068814A (en) Method, device, system and medium for generating executable file
CN111338968A (en) Project function module debugging method, device, medium and electronic equipment
CN113361235B (en) HTML file generation method and device, electronic equipment and readable storage medium
CN116880901B (en) Application page analysis method, device, electronic equipment and computer readable medium
CN117270838B (en) Method, device, equipment and medium for generating universal formula script

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
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20191015