CN112667506A - Interface testing method and related device - Google Patents
Interface testing method and related device Download PDFInfo
- Publication number
- CN112667506A CN112667506A CN202011570135.3A CN202011570135A CN112667506A CN 112667506 A CN112667506 A CN 112667506A CN 202011570135 A CN202011570135 A CN 202011570135A CN 112667506 A CN112667506 A CN 112667506A
- Authority
- CN
- China
- Prior art keywords
- interface
- tested
- extended attribute
- processor
- extended
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 114
- 238000012545 processing Methods 0.000 claims abstract description 83
- 230000007246 mechanism Effects 0.000 claims abstract description 22
- 238000010998 test method Methods 0.000 claims abstract description 4
- 238000003860 storage Methods 0.000 claims description 6
- 230000006978 adaptation Effects 0.000 claims description 5
- 230000007613 environmental effect Effects 0.000 claims description 4
- 238000000034 method Methods 0.000 description 26
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 238000013507 mapping Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000000605 extraction Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000002360 preparation method Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
An interface test method and related device, comprising: obtaining a test request of an interface to be tested, wherein the test request comprises: basic attributes matched with the interface to be tested; marking the interface to be tested based on user operation, adding an extended attribute to the test request, and taking the interface to be tested after marking operation as a marked interface; acquiring the extension attribute of the marked interface based on a program reflection mechanism; calling an interface processing chain matched with the extended attribute; processing the interface to be tested by adopting a processor corresponding to the interface processing chain; and feeding back the processing result of the interface to be tested to a sender of the test request. According to the scheme, the extended attribute is added to the interface to be tested through marking operation, the using identity is marked for the interface to be tested, and then the appropriate processor is selected for processing according to the using identity, so that different testing interfaces can be processed by the same processor, code redundancy is reduced, and reusability of the processor is improved.
Description
Technical Field
The invention relates to the technical field of data testing, in particular to an interface testing method and a related device.
Background
As the testing time required for continuous delivery becomes shorter and shorter, but the quality requirements also become higher and higher; how to effectively ensure the on-line and release quality of a product under the condition of insufficient test time? The interface automation test provides necessary technical support at this time. The interface automatic test comprises the automatic test of a single interface and the automatic test of multiple interfaces (wherein, the automatic test is divided into no dependency relationship between the interfaces and the dependency relationship between the interfaces), and the automatic test without the dependency relationship between the single interface and the multiple interfaces can be completely completed by the existing unit test framework (unit, unit and test NG). As shown in FIG. 1, the unit testing frames have packaged corresponding pre-processing (e.g., building a pre-testing preparation environment) and post-processing (e.g., restoring a post-testing environment) to meet the requirements of the interface testing;
however, the interface testing process will also face a situation of verifying the correctness of the business logic by calling each service interface, and the input-output ratio of the interface testing process is higher than that of an end-to-end automation test (such as a UI test), so it is also a popular practice in the industry to verify the business logic by using interface assembly; but now face a series of problems that the above-described unit test framework cannot solve. The problems are as follows:
the configuration conditions are not uniform: the precondition and the postcondition required by each assembled interface are inconsistent, and the condition dependency is strong.
Code coupling is severe: the success or failure processing strategy of each assembled interface request is different, and the part of the processing of the interface is coupled into the code, so that the code is redundant.
The dependency between the interfaces is strong: in the process of verifying the service logic through the interface, there is data that the downstream interface relies on the upstream interface to call for successful pass-back, for example: the interface of the 'loading menu list' needs the token returned by the response after the calling of the upstream 'login' interface is successful as the entry parameter, and then the test of the interface can be carried out.
Disclosure of Invention
In view of this, embodiments of the present invention provide an interface testing method and a related apparatus, so as to reduce redundant codes in a testing process.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
an interface testing method, comprising:
obtaining a test request of an interface to be tested, wherein the test request comprises: basic attributes matched with the interface to be tested;
marking the interface to be tested based on user operation, adding an extended attribute to the test request, and taking the interface to be tested after marking operation as a marked interface;
acquiring the extension attribute of the marked interface based on a program reflection mechanism;
calling an interface processing chain matched with the extended attribute;
processing the interface to be tested by adopting a processor corresponding to the interface processing chain;
and feeding back the processing result of the interface to be tested to a sender of the test request.
Optionally, the interface testing method includes:
the extended attributes include: a first extended attribute and a second extended attribute;
the first extended attribute is a control judgment condition for selecting an interface processing chain;
the second extended attribute is used for providing necessary parameters for adaptation for a processor corresponding to the interface processing chain.
Optionally, in the interface testing method, the first extended attribute includes but is not limited to: one or a combination of both of a priority parameter and a type parameter;
the second extended attribute includes, but is not limited to: one or a combination of both of the environmental parameter and the extracted value.
Optionally, in the interface testing method, the obtaining of the extended attribute of the marked interface based on the program reflection mechanism includes:
and acquiring the extension attribute of the marked interface based on a java program reflection mechanism.
An interface test apparatus comprising:
the device comprises an acquisition unit and a test unit, wherein the acquisition unit is used for acquiring a test request of an interface to be tested, and the test request comprises: basic attributes matched with the interface to be tested;
the processing unit is used for marking the interface to be tested based on user operation, adding an extended attribute to the test request and taking the interface to be tested after marking operation as a marked interface;
the calling unit is used for acquiring the extended attribute of the marked interface based on a program reflection mechanism and calling an interface processing chain matched with the extended attribute;
the execution unit is used for processing the interface to be tested by adopting the processor corresponding to the interface processing chain;
and the feedback unit is used for feeding back the processing result of the interface to be tested to the sender of the test request.
Optionally, the interface testing apparatus includes:
the extended attributes include: a first extended attribute and a second extended attribute;
the first extended attribute is a control judgment condition for selecting an interface processing chain;
the second extended attribute is used for providing necessary parameters for adaptation for a processor corresponding to the interface processing chain.
Optionally, in the interface testing apparatus, the first extended attribute includes but is not limited to: one or a combination of both of a priority parameter and a type parameter;
the second extended attribute includes, but is not limited to: one or a combination of both of the environmental parameter and the extracted value.
Optionally, in the interface testing apparatus, the obtaining of the extended attribute of the marked interface based on the program reflection mechanism includes:
and acquiring the extension attribute of the marked interface based on a java program reflection mechanism.
A readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the steps of any of the above described interface test methods.
An interface test apparatus comprising a memory and a processor;
the memory is used for storing programs;
the processor is configured to execute the program to implement each step of the interface testing method according to any one of the above descriptions.
Based on the technical scheme, according to the scheme provided by the embodiment of the invention, before the interface to be tested is tested, a user can decouple the relation between the interface object to be tested and the interface processing chain, so that according to different use scenes of the interface to be tested, an extended attribute is added to the interface to be tested through marking operation, a use identity is marked to the interface to be tested based on the extended attribute, and then a proper processor is selected for processing according to the use identity, so that different test interfaces can be processed by adopting the same processor, the code redundancy is reduced, and the reusability of the processor is improved.
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 embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a conventional unit test frame;
fig. 2 is a schematic flowchart of an interface testing method disclosed in an embodiment of the present application;
FIG. 3 is a schematic diagram of a processor;
fig. 4 is a schematic structural diagram of an interface testing apparatus disclosed in an embodiment of the present application;
FIG. 5 is a schematic view of a processing flow of extended attributes of the processor to different interfaces to be tested, which are obtained by calling different interface processing chains;
fig. 6 is a schematic structural diagram of an interface test apparatus disclosed in an embodiment of the present application.
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 only a part of the embodiments of the present invention, and not all of the 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.
In order to reduce redundant code, the present application provides an interface testing method, referring to fig. 2, which may include:
step S101: obtaining a test request of an interface to be tested, wherein the test request comprises: basic attributes matched with the interface to be tested;
when the interface is tested, the step is to obtain a test request of the interface to be tested, wherein the test request of the interface to be tested comprises basic attributes such as a URL (uniform resource locator), a test method, basic parameters and the like which are matched with the interface to be tested;
step S102: marking the interface to be tested based on user operation, adding an extended attribute to the test request, and taking the interface to be tested after marking operation as a marked interface;
in the scheme, before the interface to be tested is tested, marking operation can be performed on the interface to be tested, the marking operation can be completed based on user operation, an extended attribute matched with the interface to be tested can be added to a test request corresponding to the interface to be tested through the marking operation, and the interface to be tested is marked as a marked interface.
The extended attribute is an extended attribute matched with the interface to be tested, and specifically contained data content of the extended attribute can be selected based on test requirements, for example, the extended attribute can include one or a combination of more of priority, type, environment, extracted value and the like, and a processor for testing the interface to be tested can be determined through the extended parameter;
step S103: acquiring the extension attribute of the marked interface based on a program reflection mechanism;
in this step, before testing the interface to be tested, an extended attribute of the marked interface is dynamically acquired through a program reflection mechanism, where the program reflection mechanism may refer to a Java program reflection mechanism or other program reflection mechanisms, and a core of the Java program reflection mechanism is to dynamically load a class and acquire detailed information of the class when a program runs, so as to operate an attribute and a method of the class or the object. The essence of the method is that after the JVM obtains a class object, the class object is decompiled, so that various information of the object is obtained;
step S104: calling an interface processing chain matched with the extended attribute;
in this step, in a system applying the method, a mapping relationship between the extended attribute and an interface processing chain may be stored in advance, the mapping relationship is stored in a preset mapping table, after a corresponding extended attribute of the interface to be tested is obtained based on a program reflection mechanism, an interface processing chain matched with the extended attribute is searched based on the mapping table, in this scheme, each interface processing chain corresponds to one or more processors, and when the interface processing chain is determined, a processor for testing the interface to be tested is also determined.
Step S105: processing the interface to be tested by adopting a processor corresponding to the interface processing chain;
after the interface processor determines, the interface processor reads the basic attribute and the extended attribute of the interface to be tested through the interface processing chain, and processes the interface to be tested based on the basic attribute and the extended attribute, where the processing content may include, but is not limited to, log recording, performance statistics, security control, transaction processing, exception handling, and the like.
Step S106: feeding back the processing result of the interface to be tested to a sender of the test request;
in this step, after the test of the interface to be tested is completed, a corresponding processing result is generated, and after the processing result is obtained, the processing result is fed back to the sender of the test request.
In the scheme, before the interface to be tested is tested, a user can decouple the relation between an object of the interface to be tested and an interface processing chain, so that an extended attribute is added to the interface to be tested through marking operation according to different use scenes of the interface to be tested, a use identity is marked for the interface to be tested based on the extended attribute, and a proper processor is selected for processing according to the use identity, so that different test interfaces can be processed by adopting the same processor, code redundancy is reduced, and reusability of the processor is improved.
In the scheme, each processor corresponding to the interface processing chain supports longitudinal and transverse expansion, so that the flexibility of interface processing is improved, and the problems of difference of configuration processing of each interface and dependency between the interfaces when the service logic is verified through the interfaces are solved.
In conclusion, the device solves the problems of configuration difference, interface dependency and code redundancy in a complex interface set verification scene.
In a specific embodiment of the present application, the extended attributes may be divided into two categories, that is, the extended attributes include: a first extended attribute and a second extended attribute;
the first extended attribute is a control judgment condition for selecting an interface processing chain, that is, a corresponding interface processing chain can be obtained by mapping through the first extended attribute. Such as: the attributes such as priority, type and the like can find an interface processing chain corresponding to the interface priority and type, and the interfaces to be tested are sequentially processed according to the interface processing chain sequence, at this time, the attributes such as priority, type and the like are the first extended attributes.
The second extended attribute is used for providing necessary parameters for adaptation for a processor corresponding to the interface processing chain. Such as: according to the type and priority mapping of the interface to be tested, an interface processing chain matched with the interface to be tested is mapped, the interface processing chain corresponds to a pre-processor of an environment processor, the processor is used for preparing a database connection environment before testing the interface to be tested, and the environment processor can know whether the connection is a test library, a pre-release library or a production library according to the environment type. In the same way, the marking of the extraction value can be provided for the extraction processor corresponding to the interface processing chain, and the value indicated by the extraction value can be extracted for the downstream interface to use. When the mark is printed for the interface to be tested, the default value of the extension attribute can be preset, the marking workload is reduced, and the interface testing efficiency is improved; the adding of the extended attributes such as priority, type, environment, extraction value, etc. to the interface is not limited thereto.
In the technical solutions disclosed in the above embodiments of the present application, referring to fig. 3, fig. 3 is a diagram for further explaining a processor corresponding to an interface processing chain, and the processor corresponding to the interface processing chain is abstracted and divided into two main categories: a pre-processor and a post-processor, the pre-processor being primarily used to provide test preparation, e.g. test data preparation, database connections, etc., prior to testing of the tape test interface, which may be done by the pre-processor. The post processor is mainly used for completing operations related to recovery and processing of the test request after the test of the interface to be tested succeeds or fails, for example, the post processor may include a data recovery processor, a failure retry processor, and the like. In this scheme, the processors corresponding to the interface processing chain are not limited to log records, performance statistics, security control, transaction processing, exception processing, and the like.
The following describes the interface testing device provided by the embodiment of the present invention, and the interface testing device described below and the interface testing method described above may be referred to correspondingly.
Referring to fig. 4, an interface testing apparatus disclosed in an embodiment of the present application may include:
the acquisition unit 1, corresponding to step S101 in the method, is configured to obtain a test request of an interface to be tested, where the test request includes: basic attributes matched with the interface to be tested;
a processing unit 2, corresponding to step S102 in the method, configured to perform a marking operation on the to-be-tested interface based on a user operation, add an extended attribute to the test request, and use the to-be-tested interface subjected to the marking operation as a marked interface;
a calling unit 3, corresponding to steps S103-S104 in the above method, configured to obtain an extended attribute of a marked interface based on a program reflection mechanism, and call an interface processing chain matched with the extended attribute, where the different processing chains may call different processors to perform corresponding processing on the extended attribute of different interfaces, for example, as shown in fig. 5, fig. 5 is a schematic processing flow diagram of the extended attribute of different interfaces to be tested, where the processor is obtained by calling the different interface processing chains;
an execution unit 4, corresponding to step S105 in the method, configured to process the interface to be tested by using the processor corresponding to the interface processing chain;
a feedback unit 5, corresponding to step S106 in the method, configured to feed back a processing result of the interface to be tested to a sender of the test request.
Corresponding to the method, the application also discloses a readable storage medium, wherein a plurality of instructions are stored in the readable storage medium, and the instructions are suitable for being loaded by a processor to execute the steps in the interface testing method according to any one of the embodiments of the application.
The embodiment discloses interface test equipment, which comprises a memory and a processor;
fig. 6 is a hardware structure diagram of an interface test device according to an embodiment of the present invention, which is shown in fig. 6 and includes: the method can comprise the following steps: a memory 100 and a processor 200;
the interface test device further comprises a communication interface 300 and a communication bus 400, wherein the memory 100, the processor 200 and the communication interface 300 are communicated with each other through the communication bus 400.
The memory 100 is used for storing program codes; the program code includes computer operational instructions.
The processor 200 may be a central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention. The processor 200 is configured to call the program code, and when the program code is executed, is configured to perform the method according to any of the above embodiments of the present application.
For example, the processor 200 is configured to call the program code to perform:
obtaining a test request of an interface to be tested, wherein the test request comprises: basic attributes matched with the interface to be tested;
marking the interface to be tested based on user operation, adding an extended attribute to the test request, and taking the interface to be tested after marking operation as a marked interface;
acquiring the extension attribute of the marked interface based on a program reflection mechanism;
calling an interface processing chain matched with the extended attribute;
processing the interface to be tested by adopting a processor corresponding to the interface processing chain;
and feeding back the processing result of the interface to be tested to a sender of the test request.
For convenience of description, the above system is described with the functions divided into various modules, which are described separately. Of course, the functionality of the various modules may be implemented in the same one or more software and/or hardware implementations of the invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
It is further 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.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An interface testing method, comprising:
obtaining a test request of an interface to be tested, wherein the test request comprises: basic attributes matched with the interface to be tested;
marking the interface to be tested based on user operation, adding an extended attribute to the test request, and taking the interface to be tested after marking operation as a marked interface;
acquiring the extension attribute of the marked interface based on a program reflection mechanism;
calling an interface processing chain matched with the extended attribute;
processing the interface to be tested by adopting a processor corresponding to the interface processing chain;
and feeding back the processing result of the interface to be tested to a sender of the test request.
2. The interface test method of claim 1, comprising:
the extended attributes include: a first extended attribute and a second extended attribute;
the first extended attribute is a control judgment condition for selecting an interface processing chain;
the second extended attribute is used for providing necessary parameters for adaptation for a processor corresponding to the interface processing chain.
3. The interface testing method of claim 2, wherein the first extended attribute includes, but is not limited to: one or a combination of both of a priority parameter and a type parameter;
the second extended attribute includes, but is not limited to: one or a combination of both of the environmental parameter and the extracted value.
4. The interface testing method according to claim 1, wherein the obtaining extended attributes of the marked interface based on the program reflection mechanism comprises:
and acquiring the extension attribute of the marked interface based on a java program reflection mechanism.
5. An interface testing apparatus, comprising:
the device comprises an acquisition unit and a test unit, wherein the acquisition unit is used for acquiring a test request of an interface to be tested, and the test request comprises: basic attributes matched with the interface to be tested;
the processing unit is used for marking the interface to be tested based on user operation, adding an extended attribute to the test request and taking the interface to be tested after marking operation as a marked interface;
the calling unit is used for acquiring the extended attribute of the marked interface based on a program reflection mechanism and calling an interface processing chain matched with the extended attribute;
the execution unit is used for processing the interface to be tested by adopting the processor corresponding to the interface processing chain;
and the feedback unit is used for feeding back the processing result of the interface to be tested to the sender of the test request.
6. The interface test apparatus of claim 5, comprising:
the extended attributes include: a first extended attribute and a second extended attribute;
the first extended attribute is a control judgment condition for selecting an interface processing chain;
the second extended attribute is used for providing necessary parameters for adaptation for a processor corresponding to the interface processing chain.
7. The interface test apparatus of claim 6, wherein the first extended attribute includes, but is not limited to: one or a combination of both of a priority parameter and a type parameter;
the second extended attribute includes, but is not limited to: one or a combination of both of the environmental parameter and the extracted value.
8. The interface testing apparatus of claim 5, wherein the obtaining extended attributes of the marked interface based on the program reflection mechanism comprises:
and acquiring the extension attribute of the marked interface based on a java program reflection mechanism.
9. A readable storage medium comprising, in combination,
the storage medium stores a plurality of instructions adapted to be loaded by a processor to perform the steps of the interface testing method of any one of claims 1 to 4.
10. An interface test apparatus comprising a memory and a processor;
the memory is used for storing programs;
the processor, configured to execute the program, implementing the steps of the interface testing method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011570135.3A CN112667506A (en) | 2020-12-26 | 2020-12-26 | Interface testing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011570135.3A CN112667506A (en) | 2020-12-26 | 2020-12-26 | Interface testing method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112667506A true CN112667506A (en) | 2021-04-16 |
Family
ID=75409897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011570135.3A Pending CN112667506A (en) | 2020-12-26 | 2020-12-26 | Interface testing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112667506A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116991713A (en) * | 2023-07-17 | 2023-11-03 | 上海一谈网络科技有限公司 | Method, device, computer equipment and storage medium for executing use cases across environments |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600048A (en) * | 2018-04-12 | 2018-09-28 | 平安科技（深圳）有限公司 | Interface testing method, device, equipment and computer readable storage medium |
| CN109558320A (en) * | 2018-11-28 | 2019-04-02 | 深圳前海微众银行股份有限公司 | System detection method, device, system, equipment and computer readable storage medium |
| CN110032511A (en) * | 2019-03-19 | 2019-07-19 | 深圳市买买提信息科技有限公司 | A kind of interface test method and interface testing equipment |
| US20190291743A1 (en) * | 2018-03-23 | 2019-09-26 | Infineon Technologies Ag | Advanced driver assistance systems test-interface for automated driving sensors |
| CN110531969A (en) * | 2019-08-27 | 2019-12-03 | 中国工商银行股份有限公司 | The method, apparatus of data processing calculates equipment and medium |
-
2020
- 2020-12-26 CN CN202011570135.3A patent/CN112667506A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190291743A1 (en) * | 2018-03-23 | 2019-09-26 | Infineon Technologies Ag | Advanced driver assistance systems test-interface for automated driving sensors |
| CN108600048A (en) * | 2018-04-12 | 2018-09-28 | 平安科技（深圳）有限公司 | Interface testing method, device, equipment and computer readable storage medium |
| CN109558320A (en) * | 2018-11-28 | 2019-04-02 | 深圳前海微众银行股份有限公司 | System detection method, device, system, equipment and computer readable storage medium |
| CN110032511A (en) * | 2019-03-19 | 2019-07-19 | 深圳市买买提信息科技有限公司 | A kind of interface test method and interface testing equipment |
| CN110531969A (en) * | 2019-08-27 | 2019-12-03 | 中国工商银行股份有限公司 | The method, apparatus of data processing calculates equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 蔡渊、方连航、陈华军、杨航；: "一种基于IEC 61968标准接口测试自动化的实现方法", 电子世界, vol. 2014, no. 13, 15 July 2014 (2014-07-15), pages 10 - 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116991713A (en) * | 2023-07-17 | 2023-11-03 | 上海一谈网络科技有限公司 | Method, device, computer equipment and storage medium for executing use cases across environments |
| CN116991713B (en) * | 2023-07-17 | 2024-02-20 | 上海一谈网络科技有限公司 | Method, device, computer equipment and storage medium for executing use cases across environments |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107885656B (en) | Automatic product algorithm testing method and application server | |
| CN109189665B (en) | Method and device for recording, replaying and automatically testing data | |
| CN111177005A (en) | Service application testing method, device, server and storage medium | |
| CN107145437B (en) | Java annotation test method and device | |
| CN114064208A (en) | Method and device for detecting application service state, electronic equipment and storage medium | |
| CN113377667A (en) | Scene-based testing method and device, computer equipment and storage medium | |
| CN112667506A (en) | Interface testing method and related device | |
| CN111538659A (en) | Interface testing method and system for service scene, electronic device and storage medium | |
| CN111459809A (en) | Software testing method based on rapid demand version iteration | |
| CN117370203B (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN112882957B (en) | Test task validity checking method and device | |
| CN114238295A (en) | Data sorting method and device based on grouping | |
| CN109388420A (en) | Application upgrade test method, device, computer equipment and storage medium | |
| CN112433935A (en) | Test method, test device, electronic equipment and storage medium | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN115167842A (en) | Visual development method, device, system, electronic equipment and medium of business | |
| CN114356346A (en) | Application program deployment method, device, storage medium and electronic equipment | |
| CN110618943B (en) | Security service test method and device, electronic equipment and readable storage medium | |
| CN113300912A (en) | Equipment testing method and device and electronic equipment | |
| CN111597101A (en) | SDK access state detection method, computer device and computer readable storage medium | |
| CN112015436A (en) | Short message platform deployment method and device, computing equipment and computer storage medium | |
| CN115545677B (en) | Online process specification detection method and system based on automatic case execution condition | |
| CN116340187B (en) | Rule engine migration test method and device, electronic equipment and storage medium | |
| CN110865933A (en) | Method, system, terminal and storage medium for rapidly testing effective value of BIOS option | |
| CN116431463A (en) | Interface automatic test method and device, storage medium and electronic equipment |
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 |