CN110704328A - Interface testing method and device, electronic equipment and readable storage medium - Google Patents
Interface testing method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN110704328A CN110704328A CN201910979129.4A CN201910979129A CN110704328A CN 110704328 A CN110704328 A CN 110704328A CN 201910979129 A CN201910979129 A CN 201910979129A CN 110704328 A CN110704328 A CN 110704328A
- Authority
- CN
- China
- Prior art keywords
- interface
- url
- result
- test
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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/3684—Test management for test design, e.g. generating new test cases
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides an interface testing method, an interface testing device, electronic equipment and a storage medium, and aims to reduce the error rate of manually inputting interface information and improve the interface testing efficiency. The method is applied to a use case platform and comprises the following steps: the method comprises the steps of obtaining an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of a case platform, sending a query request carrying the interface URL to an interface document platform when the query operation of the user on the interface URL is detected, receiving and displaying a value of an interface parameter variable name corresponding to the interface URL and an interface response result returned by the interface document platform, obtaining an assertion result input by the user on the test case editing interface, wherein the assertion result is set by the user according to the interface response result and the value of the interface parameter variable name, generating a test case according to the value of the interface parameter variable name and the assertion result, and executing the test case to obtain a test result.
Description
Technical Field
The present invention relates to the field of test technologies, and in particular, to an interface test method and apparatus, an electronic device, and a readable storage medium.
Background
Interface testing is a test that tests an interface between components of a system. The interface test is mainly used for detecting interaction points between external systems and between internal subsystems. The key point of the test is to check the exchange of data, transfer and control management processes, mutual logic dependency relationship between systems and the like. The interface test is generally used for interactive development among multiple systems or test of development of an application system with multiple subsystems. The interface test is suitable for the bottom-layer framework system and the central service system which provide services for other systems, and mainly tests the interfaces provided by the systems to the outside to verify the correctness and stability of the interfaces.
In the existing interface test, after a developer determines product requirements, an interface protocol is determined and interface information is input on an interface document platform, the tester performs interface test on a case platform, test case editing and input comprise an interface URL, an interface method, interface description, a module, interface parameters, an interface response result and the like, the compiling of an interface test case is completed, the time cost is high, and input errors can be generated due to manual editing, so that the interface case test fails.
Disclosure of Invention
The embodiment of the invention provides an interface testing method and device, electronic equipment and a readable storage medium, and aims to reduce the error rate of manually inputting interface information and improve the interface testing efficiency.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides an interface testing method, which is applied to a use case platform, and the method includes:
acquiring an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of the case platform;
when the query operation of a user for the interface URL is detected, sending a query request carrying the interface URL to an interface document platform;
receiving and displaying the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform;
receiving an assertion result input by a user, wherein the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
and executing the test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
Optionally, when a query operation of the user for the interface URL is detected, sending a query request to the interface document platform, including:
when the query operation of a user for the interface URL is detected, judging whether the interface URL is matched with a preset regular expression, wherein the preset regular expression is set according to rules which all the interface URLs accord with;
and sending a query request to the interface document platform under the condition that the interface URL is matched with the preset regular expression.
Optionally, after obtaining the test result, the method further includes:
comparing the test result with the assertion result, and determining whether the interface to be tested corresponding to the interface URL passes the test;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
Optionally, after sending the query request carrying the interface URL to an interface document platform, the method further includes:
receiving and displaying a request success prompt returned by the interface document platform; or
And receiving and displaying the reason for the failure of the request returned by the interface document platform.
In a second aspect, an embodiment of the present invention provides an interface testing method, which is applied to an interface document platform, and the method includes:
receiving a query request which is sent by a use case platform and carries an interface URL of an interface to be tested;
inquiring the value of the interface parameter variable name corresponding to the interface URL and an interface response result from a pre-stored interface information database;
sending the value of the interface parameter variable name corresponding to the interface URL and an interface response result to the use case platform so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user can input an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
Optionally, before receiving a query request carrying an interface URL of an interface to be tested, which is sent by the use case platform, the method further includes:
obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and storing the values of the interface parameter variable names corresponding to the plurality of interface URLs and the interface response results into the interface information database.
In a third aspect, an embodiment of the present invention further provides an interface testing apparatus, which is applied to a use-case platform, and the apparatus includes:
the first obtaining module is used for obtaining an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of the case platform;
the request module is used for sending a query request carrying the interface URL to an interface document platform when the query operation of a user for the interface URL is detected;
the receiving and displaying module is used for receiving and displaying the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform;
the receiving module is used for receiving an assertion result input by a user, wherein the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
and the test module is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
Optionally, the request module includes:
the judging submodule is used for judging whether the interface URL is matched with a preset regular expression when the query operation of a user for the interface URL is detected, wherein the preset regular expression is set according to the rule that a plurality of interface URLs all accord with;
and the request submodule is used for sending a query request to the interface document platform under the condition that the interface URL is matched with the preset regular expression.
Optionally, the apparatus further comprises:
the comparison module is used for comparing the test result with the assertion result and determining whether the interface to be tested corresponding to the interface URL passes the test or not;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
Optionally, after sending the query request carrying the interface URL to the interface document platform, the apparatus further includes:
the second receiving and displaying module is used for receiving and displaying a request success prompt returned by the interface document platform; or
And the third receiving and displaying module is used for receiving and displaying the reason of the request failure returned by the interface document platform.
In a fourth aspect, an embodiment of the present invention further provides an interface testing apparatus, applied to an interface document platform, where the apparatus includes:
the receiving module is used for receiving a query request which is sent by the use case platform and carries the interface URL of the interface to be tested;
the query module is used for querying the value of the interface parameter variable name corresponding to the interface URL and an interface response result from a pre-stored interface information database;
the sending module is used for sending the value of the interface parameter variable name corresponding to the interface URL and an interface response result to the use case platform so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user can input an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
Optionally, before receiving a query request carrying an interface URL of an interface to be tested, which is sent by the use-case platform, the apparatus further includes:
the second obtaining module is used for obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and the storage module is used for storing the values of the interface parameter variable names and the interface response results corresponding to the plurality of interface URLs and the plurality of interface URLs into the interface information database.
In a fifth aspect, an embodiment of the present invention additionally provides an electronic device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor implementing the steps of the interface testing method of the first or second aspect.
In a sixth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program, when executed by a processor, implements the steps of the interface testing method according to the first aspect or the second aspect.
In the embodiment of the invention, a case platform acquires an interface Uniform Resource Locator (URL) input by a user, and sends a query request carrying the interface URL to an interface document platform when detecting a query operation of the user for the interface URL, the interface document platform queries a value of an interface parameter variable name and an interface response result corresponding to the interface URL according to the query request and sends the value to the case platform, the case platform receives and displays the value of the interface parameter variable name and the interface response result, which are returned by the interface document platform, corresponding to the interface URL, of the interface URL, the case platform acquires an assertion result input by the user on a test case editing interface, generates a test case according to the value of the interface parameter variable name and the assertion result, and executes the test case to obtain a test result. By adopting the interface testing method provided by the embodiment of the invention, the case platform can conveniently acquire the value of the interface parameter variable name and the interface response result of the tested interface, and a tester can finish the editing of the test case only by inputting the assertion result, thereby finishing the interface test, reducing the errors generated by manually inputting the value of the interface parameter variable name and the assertion result editing case, and improving the efficiency and the quality of the interface test.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without inventive labor.
FIG. 1 is a schematic diagram of an implementation environment shown in accordance with an exemplary embodiment;
FIG. 2 is a flow chart illustrating steps of a method for testing an interface according to an embodiment of the present invention;
FIG. 3 is a flow chart of steps in another method for testing an interface in accordance with an embodiment of the present invention;
FIG. 4 is a schematic diagram of an interface testing apparatus according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of another interface testing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a hardware structure of an electronic device in the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
FIG. 1 is a schematic diagram illustrating one implementation environment in accordance with an example embodiment. Referring to fig. 1, the implementation environment includes: a use case platform 100 and an interface document platform 200.
The use case platform 100 and the interface document platform 200 are communicatively connected, wherein the connection mode may be a wired connection or a wireless connection.
In the existing interface test, after a developer determines product requirements, an interface protocol is determined and interface information is input on an interface document platform, the tester performs interface test on a case platform, test case editing and input comprise an interface URL, an interface method, interface description, a module, interface parameters, an interface response result and the like, the compiling of an interface test case is completed, the time cost is high, and input errors can be generated due to manual editing, so that the interface case test fails.
Referring to fig. 2, fig. 2 is a flowchart of steps of an interface testing method in an embodiment of the present invention, which is applied to a use-case platform, and as shown in fig. 2, the method includes the following steps:
step S201: and acquiring an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of the case platform.
Before interface testing, a user needs to acquire a path for storing interface information of an interface to be tested, and then inputs an interface Uniform Resource Locator (URL) on a test case editing interface of a case platform according to the path for storing the interface information of the interface to be tested. For example, the interface URL may be entered as: http:// app.58. com/api/community/subject/list.
Step S202: and when the query operation of the user for the interface URL is detected, sending a query request carrying the interface URL to an interface document platform.
The test case editing interface of the case platform is added with a query function, a user clicks for query after inputting an interface Uniform Resource Locator (URL), and the case platform sends a query request carrying the interface URL to the interface document platform when detecting the query operation of the user aiming at the interface URL.
In this embodiment, in order to ensure that the URL format of the input interface uniform resource locator is correct and avoid errors generated during user input, a possible implementation manner is:
when the query operation of a user for the interface URL is detected, judging whether the interface URL is matched with a preset regular expression, wherein the preset regular expression is set according to rules which all the interface URLs accord with;
and sending a query request to the interface document platform under the condition that the interface URL is matched with a preset regular expression.
The interface URL has a certain input format, and includes 3 parts, for example: http:// www.example.com/home. Where "http", often referred to as URL patterns, always occurs before the colon and two slashes, and serves to tell the web client how to access a resource. In this example, it tells the web client to initiate a request using the hypertext transfer protocol, i.e., HTTP. Common URL patterns are also ftp, mailto, and git. "www.example.com" is the second part of the URL, which is the resource path or host (host). It tells the client the exact location of the resource. "Home" is the third part of the URL, namely the URL path. It represents what local resources (for the server) the client is requesting. According to the 3 parts of the interface URL, a regular expression is formulated to judge whether the input interface URL meets the rule or not. And after the interface URL is matched with a preset regular expression, sending a query request to the interface document platform.
Step S203: and receiving and displaying the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform.
After receiving the query request, the interface document platform feeds back interface information to the use case platform, and after receiving the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform, the use case platform displays the value of the interface parameter variable name and the interface response result at the corresponding position of the test case editing interface, wherein the value of the interface parameter variable name is information which needs to be carried when the interface request is sent. For example, the values of the received interface parameter variable names may be: issueid 120, pageumber 2, pagesize 10, sortValue 1568630416000, spid 4; the interface response result is an interface response result obtained after the interface is requested, and for example, the interface response result may be: "data" { "sortValue":1568630416000, "interlogic vo" [ ], "articleld":0}, "message": operation success ", and" status ": 1. Further, use case editing may also include at least one of: interface methods, interface descriptions, modules, and the like. By way of example, the interface method may be: get, interface description is an explanation of the interface, for example: topic level page, etc., the module indicates what scope of the test requirements the interface belongs to, for example: wireless app-co-town tribes-topics, etc.
In an implementable manner, after sending the query request carrying the interface URL to an interface document platform, the method further comprises:
receiving and displaying a request success prompt returned by the interface document platform; or
And receiving and displaying the reason for the failure of the request returned by the interface document platform.
In this embodiment, the request may fail for a variety of reasons, such as: the requested interface to be tested does not exist or the requested interface information corresponding to the interface to be tested does not exist, if the request is successful, the interface document platform sends a request success prompt to the case platform, the case platform receives the request success prompt sent by the interface document platform and then displays the request on the test case editing interface, if the request is failed, the interface document platform sends a request failure reason to the case platform, and after the case platform receives the request failure reason sent by the interface document platform, the request failure reason is displayed on the test case editing interface, for example, the displayed request failure reason can be: the requested interface to be tested does not exist or the interface information corresponding to the requested interface to be tested does not exist, and the like.
Step S204: receiving an assertion result input by a user, wherein the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
in this embodiment, according to the obtained value of the interface parameter variable name, the user may input an assertion result in the test case editing interface, and for the same interface, the value of each group of interface parameter variable names has a test result corresponding thereto, so that the user refers to the interface response result and the value of the interface parameter variable name when editing the assertion result, where assertion is a statement that a specific premise is true, and the assertion result is a result of pre-determination and is the same as a result correctly returned after the test case is correctly executed by the interface to be tested, and for example, the input assertion result may be: sortvalue, value 1568630416000; condition is equal to.
Step S205: and executing the test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
In this embodiment, after the steps of step S201 to step S204 are completed, the editing work of the test case is completed, the case platform may generate the test case according to the value of the interface parameter variable name and the assertion result, execute the test case, and test the interface to be tested to obtain a test result, and according to the above example, the obtained test result is:
"message": the "execution was successful",
"resDescripte": "Co-verify 1, all passes",
“failReason”:“”，
“actuaList”：[
{gpath“：”data.sortValue”，
“value”:“1568630416000”}]。
in a possible embodiment, after obtaining the test result, the method further comprises:
comparing the test result with the assertion result, and determining whether the interface to be tested corresponding to the interface URL passes the test;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
In this embodiment, the assertion result is a result obtained when it is assumed that the interface to be tested has no problem, and the assertion result input by the user is compared with the obtained test result, and if the assertion result is the same as the test result, it is verified that the interface to be tested has no problem, and if the assertion result is different from the test result, it is verified that the interface to be tested has a problem, and fails in the test.
In the embodiment of the invention, a case platform acquires an interface Uniform Resource Locator (URL) input by a user, and sends a query request carrying the interface URL to an interface document platform when detecting a query operation of the user for the interface URL, the interface document platform queries a value of an interface parameter variable name and an interface response result corresponding to the interface URL according to the query request and sends the value to the case platform, the case platform receives and displays the value of the interface parameter variable name and the interface response result, which are returned by the interface document platform, corresponding to the interface URL, of the interface URL, the case platform acquires an assertion result input by the user on a test case editing interface, generates a test case according to the value of the interface parameter variable name and the assertion result, and executes the test case to obtain a test result. By adopting the interface testing method provided by the embodiment of the invention, the case platform can conveniently acquire the value of the interface parameter variable name and the interface response result of the tested interface, and a tester can finish the editing of the test case only by inputting the assertion result, thereby finishing the interface test, reducing the errors generated by manually inputting the value of the interface parameter variable name and the assertion result editing case, and improving the efficiency and the quality of the interface test.
Referring to fig. 3, fig. 3 is a flowchart of steps of another interface testing method in the embodiment of the present invention, applied to an interface document platform, as shown in fig. 3, the method includes the following steps:
step S301: and receiving a query request which is sent by the use case platform and carries the interface URL of the interface to be tested.
Step S302: inquiring the value of the interface parameter variable name corresponding to the interface URL and an interface response result from a pre-stored interface information database;
in this embodiment, the interface document platform receives a query request sent by the use-case platform, where the query request carries an interface URL of an interface to be tested, and the interface document platform queries, through information in the query request, a value of an interface parameter variable name and an interface response result corresponding to the interface URL from a pre-stored interface information database.
Step S303: sending the value of the interface parameter variable name corresponding to the interface URL and an interface response result to the use case platform so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user can input an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
In this embodiment, the interface document platform sends the value of the interface parameter variable name and the interface response result corresponding to the interface URL to the use case platform, so that the use case platform obtains information such as the value of the interface parameter variable name after receiving the returned value of the interface parameter variable name and the interface response result, and for the same interface, the value of each group of interface parameter variable names has a test result corresponding to the value of the interface parameter variable name according to the obtained value of the interface parameter variable name. The case platform can generate a test case according to the value of the interface parameter variable name and the assertion result, execute the test case, and test the tested interface to obtain a test result.
In a possible implementation manner, before receiving a query request carrying an interface URL of an interface to be tested, which is sent by a use case platform, the method further includes:
obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and storing the values of the interface parameter variable names corresponding to the plurality of interface URLs and the interface response results into the interface information database.
In this embodiment, before testing the interface, a user needs to establish an interface information database in advance on an interface document platform, obtain a plurality of interface URLs and values of interface parameter variable names and interface response results corresponding to the plurality of interface URLs, and store the values and the interface response results into the interface information database, where an association relationship is established between the interface URLs and the values of the interface parameter variable names and the interface response results corresponding to the interface URLs, so that the interface document platform can quickly find the values of the interface parameter variable names and the interface response results corresponding to the interface URLs according to the interface URL information.
In the embodiment of the invention, a case platform acquires an interface Uniform Resource Locator (URL) input by a user, and sends a query request carrying the interface URL to an interface document platform when detecting a query operation of the user for the interface URL, the interface document platform queries a value of an interface parameter variable name and an interface response result corresponding to the interface URL according to the query request and sends the value to the case platform, the case platform receives and displays the value of the interface parameter variable name and the interface response result, which are returned by the interface document platform, corresponding to the interface URL, of the interface URL, the case platform acquires an assertion result input by the user on a test case editing interface, generates a test case according to the value of the interface parameter variable name and the assertion result, and executes the test case to obtain a test result. By adopting the interface testing method provided by the embodiment of the invention, the case platform can conveniently acquire the value of the interface parameter variable name and the interface response result of the tested interface, and a tester can finish the editing of the test case only by inputting the assertion result, thereby finishing the interface test, reducing the errors generated by manually inputting the value of the interface parameter variable name and the assertion result editing case, and improving the efficiency and the quality of the interface test.
Based on the same inventive concept, an embodiment of the present invention provides an interface testing apparatus. Referring to fig. 4, fig. 4 is a schematic diagram of an interface testing apparatus according to an embodiment of the present invention. As shown in fig. 4, the apparatus is applied to a use case platform, and includes:
a first obtaining module 401, configured to obtain an interface uniform resource locator URL input by a user on a test case editing interface of the case platform;
a request module 402, configured to send a query request carrying the interface URL to an interface document platform when a query operation of a user for the interface URL is detected;
a receiving and displaying module 403, configured to receive and display a value of an interface parameter variable name corresponding to the interface URL and an interface response result returned by the interface document platform;
a receiving module 404, configured to receive an assertion result input by a user, where the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
a test module 405, configured to execute a test case generated based on at least the value of the interface parameter variable name and the assertion result, so as to obtain a test result.
Optionally, the request module includes:
the judging submodule is used for judging whether the interface URL is matched with a preset regular expression when the query operation of a user for the interface URL is detected, wherein the preset regular expression is set according to the rule that a plurality of interface URLs all accord with;
and the request submodule is used for sending a query request to the interface document platform under the condition that the interface URL is matched with the preset regular expression.
Optionally, the apparatus further comprises:
the comparison module is used for comparing the test result with the assertion result and determining whether the interface to be tested corresponding to the interface URL passes the test or not;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
Optionally, after sending the query request carrying the interface URL to the interface document platform, the apparatus further includes:
the second receiving and displaying module is used for receiving and displaying a request success prompt returned by the interface document platform; or
And the third receiving and displaying module is used for receiving and displaying the reason of the request failure returned by the interface document platform.
Referring to fig. 5, fig. 5 is a schematic diagram of another interface testing apparatus according to an embodiment of the present invention. As shown in fig. 5, the apparatus is applied to an interface document platform, and includes:
a receiving module 501, configured to receive a query request carrying an interface URL of an interface to be tested, where the query request is sent by a use case platform;
a query module 502, configured to query, from a pre-stored interface information database, a value of an interface parameter variable name corresponding to the interface URL and an interface response result;
a sending module 503, configured to send the value of the interface parameter variable name corresponding to the interface URL and the interface response result to the use case platform, so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user inputs an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
Optionally, before receiving a query request carrying an interface URL of an interface to be tested, which is sent by the use-case platform, the apparatus further includes:
the second obtaining module is used for obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and the storage module is used for storing the values of the interface parameter variable names and the interface response results corresponding to the plurality of interface URLs and the plurality of interface URLs into the interface information database.
Referring to fig. 6, fig. 6 is a schematic diagram of a hardware structure of an electronic device implementing various embodiments of the present invention.
The electronic device 600 includes, but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, and a power supply 611. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 6 does not constitute a limitation of the electronic device, and that the electronic device may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the electronic device includes, but is not limited to, a mobile phone, a desktop computer, a tablet computer, a notebook computer, a palm computer, and the like.
It should be understood that, in the embodiment of the present invention, the radio frequency unit 601 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 610; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. Further, the radio frequency unit 601 may also communicate with a network and other devices through a wireless communication system.
The electronic device provides wireless broadband internet access to the user via the network module 602, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media.
The audio output unit 603 may convert audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into an audio signal and output as sound. Also, the audio output unit 603 may also provide audio output related to a specific function performed by the electronic apparatus 600 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 603 includes a speaker, a buzzer, a receiver, and the like.
The input unit 604 is used to receive audio or video signals. The input Unit 604 may include a Graphics Processing Unit (GPU) 6041 and a microphone 6042, and the Graphics processor 6041 processes image data of a still picture or video obtained by an image capturing apparatus (such as a camera) in a video capture mode or an image capture mode. The processed image frames may be displayed on the display unit 606. The image frames processed by the graphic processor 6041 may be stored in the memory 609 (or other storage medium) or transmitted via the radio frequency unit 601 or the network module 602. The microphone 6042 can receive sound, and can process such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 601 in case of the phone call mode.
The electronic device 600 also includes at least one sensor 605, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 6061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 6061 and/or the backlight when the electronic apparatus 600 is moved to the ear. As one type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of an electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 605 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.
The display unit 606 is used to display information input by the user or information provided to the user. The Display unit 606 may include a Display panel 6061, and the Display panel 6061 may be configured by a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 607 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device. Specifically, the user input unit 607 includes a touch panel 6071 and other input devices 6072. Touch panel 6071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 6071 using a finger, stylus, or any suitable object or accessory). The touch panel 6071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 610, receives a command from the processor 610, and executes the command. In addition, the touch panel 6071 can be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The user input unit 607 may include other input devices 6072 in addition to the touch panel 6071. Specifically, the other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein again.
Further, the touch panel 6071 can be overlaid on the display panel 6061, and when the touch panel 6071 detects a touch operation on or near the touch panel 6071, the touch operation is transmitted to the processor 610 to determine the type of the touch event, and then the processor 610 provides a corresponding visual output on the display panel 6061 according to the type of the touch event. Although the touch panel 6071 and the display panel 6061 are shown in fig. 6 as two separate components to implement the input and output functions of the electronic device, in some embodiments, the touch panel 6071 and the display panel 6061 may be integrated to implement the input and output functions of the electronic device, and this is not limited here.
The interface unit 608 is an interface for connecting an external device to the electronic apparatus 600. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 608 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the electronic device 600 or may be used to transmit data between the electronic device 600 and external devices.
The memory 609 may be used to store software programs as well as various data. The memory 609 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 609 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 610 is a control center of the electronic device, connects various parts of the whole electronic device by using various interfaces and lines, performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 609, and calling data stored in the memory 609, thereby performing overall monitoring of the electronic device. Processor 610 may include one or more processing units; preferably, the processor 610 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 610.
The electronic device 600 may further include a power supply 611 (e.g., a battery) for supplying power to the various components, and preferably, the power supply 611 may be logically connected to the processor 610 via a power management system, such that the power management system may be used to manage charging, discharging, and power consumption.
In addition, the electronic device 600 includes some functional modules that are not shown, and are not described in detail herein.
Preferably, an embodiment of the present invention further provides an electronic device, including: the processor 610, the memory 609, and a computer program stored in the memory 609 and capable of running on the processor 610, where the computer program, when executed by the processor 610, implements each process of the above method embodiment based on applet simulation positioning, and can achieve the same technical effect, and are not described herein again to avoid repetition.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements each process of the above method embodiment based on applet simulation positioning, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, 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 like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. 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.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered 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 (14)
1. An interface testing method is applied to a case platform, and comprises the following steps:
acquiring an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of the case platform;
when the query operation of a user for the interface URL is detected, sending a query request carrying the interface URL to an interface document platform;
receiving and displaying the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform;
receiving an assertion result input by a user, wherein the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
and executing the test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
2. The method of claim 1, wherein sending a query request to an interface document platform upon detecting a query operation by a user for the interface URL comprises:
when the query operation of a user for the interface URL is detected, judging whether the interface URL is matched with a preset regular expression, wherein the preset regular expression is set according to rules which all the interface URLs accord with;
and sending a query request to the interface document platform under the condition that the interface URL is matched with the preset regular expression.
3. The method of claim 1, wherein after obtaining the test results, the method further comprises:
comparing the test result with the assertion result, and determining whether the interface to be tested corresponding to the interface URL passes the test;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
4. The method according to any one of claims 1-3, wherein after sending the query request carrying the interface URL to the interface document platform, the method further comprises:
receiving and displaying a request success prompt returned by the interface document platform; or
And receiving and displaying the reason for the failure of the request returned by the interface document platform.
5. An interface testing method is applied to an interface document platform, and comprises the following steps:
receiving a query request which is sent by a use case platform and carries an interface URL of an interface to be tested;
inquiring the value of the interface parameter variable name corresponding to the interface URL and an interface response result from a pre-stored interface information database;
sending the value of the interface parameter variable name corresponding to the interface URL and an interface response result to the use case platform so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user can input an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
6. The method according to claim 5, wherein before receiving the query request carrying the interface URL of the interface to be tested, which is sent by the use case platform, the method further comprises:
obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and storing the values of the interface parameter variable names corresponding to the plurality of interface URLs and the interface response results into the interface information database.
7. An interface testing apparatus, applied to a use case platform, the apparatus comprising:
the first obtaining module is used for obtaining an interface Uniform Resource Locator (URL) input by a user on a test case editing interface of the case platform;
the request module is used for sending a query request carrying the interface URL to an interface document platform when the query operation of a user for the interface URL is detected;
the receiving and displaying module is used for receiving and displaying the value of the interface parameter variable name corresponding to the interface URL and the interface response result returned by the interface document platform;
the receiving module is used for receiving an assertion result input by a user, wherein the assertion result is set by the user according to a value corresponding to the interface variable name and the interface response result;
and the test module is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
8. The apparatus of claim 7, wherein the request module comprises:
the judging submodule is used for judging whether the interface URL is matched with a preset regular expression when the query operation of a user for the interface URL is detected, wherein the preset regular expression is set according to the rule that a plurality of interface URLs all accord with;
and the request submodule is used for sending a query request to the interface document platform under the condition that the interface URL is matched with the preset regular expression.
9. The apparatus of claim 7, further comprising:
the comparison module is used for comparing the test result with the assertion result and determining whether the interface to be tested corresponding to the interface URL passes the test or not;
the test result is the same as the assertion result and represents that the interface to be tested passes the test, and the test result is different from the assertion result and represents that the interface to be tested does not pass the test.
10. The apparatus according to any of claims 7-9, wherein after sending the query request carrying the interface URL to the interface document platform, the apparatus further comprises:
the second receiving and displaying module is used for receiving and displaying a request success prompt returned by the interface document platform; or
And the third receiving and displaying module is used for receiving and displaying the reason of the request failure returned by the interface document platform.
11. An interface testing apparatus, applied to an interface document platform, the apparatus comprising:
the receiving module is used for receiving a query request which is sent by the use case platform and carries the interface URL of the interface to be tested;
the query module is used for querying the value of the interface parameter variable name corresponding to the interface URL and an interface response result from a pre-stored interface information database;
the sending module is used for sending the value of the interface parameter variable name corresponding to the interface URL and an interface response result to the use case platform so that the use case platform receives and displays the value of the interface parameter variable name corresponding to the interface URL and the interface response result, and a user can input an assertion result on a test case editing interface of the use case platform according to the value corresponding to the interface variable name and the interface response result;
the case platform is used for executing a test case generated at least based on the value of the interface parameter variable name and the assertion result to obtain a test result.
12. The apparatus according to claim 11, wherein before receiving the query request carrying the interface URL of the interface to be tested, which is sent by the use case platform, the apparatus further comprises:
the second obtaining module is used for obtaining a plurality of interface URLs input by a user and values of interface parameter variable names and interface response results corresponding to the interface URLs;
and the storage module is used for storing the values of the interface parameter variable names and the interface response results corresponding to the plurality of interface URLs and the plurality of interface URLs into the interface information database.
13. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the interface testing method according to any one of claims 1 to 6.
14. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the interface testing method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910979129.4A CN110704328B (en) | 2019-10-15 | 2019-10-15 | Interface testing method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910979129.4A CN110704328B (en) | 2019-10-15 | 2019-10-15 | Interface testing method and device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110704328A true CN110704328A (en) | 2020-01-17 |
| CN110704328B CN110704328B (en) | 2021-09-07 |
Family
ID=69199676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910979129.4A Active CN110704328B (en) | 2019-10-15 | 2019-10-15 | Interface testing method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704328B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111625473A (en) * | 2020-07-01 | 2020-09-04 | 北京字节跳动网络技术有限公司 | Interface test case generation method and device, storage medium and electronic equipment |
| CN112068813A (en) * | 2020-09-03 | 2020-12-11 | 中国平安财产保险股份有限公司 | Data processing method, apparatus and medium |
| CN112367220A (en) * | 2020-10-27 | 2021-02-12 | 深圳市优必选科技股份有限公司 | Interface testing method and device, storage medium and electronic equipment |
| CN112416419A (en) * | 2020-11-16 | 2021-02-26 | 北京五八信息技术有限公司 | Data processing method and device |
| CN112559319A (en) * | 2020-11-09 | 2021-03-26 | 深圳市六度人和科技有限公司 | Interface bug processing method and device, electronic equipment and storage medium |
| CN112559356A (en) * | 2020-12-18 | 2021-03-26 | 杭州兑吧网络科技有限公司 | Automatic software testing method and system |
| CN115809201A (en) * | 2022-12-23 | 2023-03-17 | 广州市保伦电子有限公司 | Interface test control method, device, equipment and medium based on two-dimensional table |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090287960A1 (en) * | 2008-05-15 | 2009-11-19 | International Business Machines Corporation | Methods, systems and computer program products for cpu signaturing to aide in performance analysis |
| CN106155891A (en) * | 2015-04-02 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Interface test method, interface description data library generating method and device |
| CN106886494A (en) * | 2017-03-07 | 2017-06-23 | 深圳国泰安教育技术股份有限公司 | A kind of automatic interface testing method and its system |
| CN107203473A (en) * | 2017-05-26 | 2017-09-26 | 四川长虹电器股份有限公司 | The automatization test system and method for automatic expansion interface test case |
| CN107748717A (en) * | 2017-09-26 | 2018-03-02 | 深圳市牛鼎丰科技有限公司 | Automatic interface testing method, device, storage medium and computer equipment |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
-
2019
- 2019-10-15 CN CN201910979129.4A patent/CN110704328B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090287960A1 (en) * | 2008-05-15 | 2009-11-19 | International Business Machines Corporation | Methods, systems and computer program products for cpu signaturing to aide in performance analysis |
| CN106155891A (en) * | 2015-04-02 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Interface test method, interface description data library generating method and device |
| CN106886494A (en) * | 2017-03-07 | 2017-06-23 | 深圳国泰安教育技术股份有限公司 | A kind of automatic interface testing method and its system |
| CN107203473A (en) * | 2017-05-26 | 2017-09-26 | 四川长虹电器股份有限公司 | The automatization test system and method for automatic expansion interface test case |
| CN107748717A (en) * | 2017-09-26 | 2018-03-02 | 深圳市牛鼎丰科技有限公司 | Automatic interface testing method, device, storage medium and computer equipment |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111625473A (en) * | 2020-07-01 | 2020-09-04 | 北京字节跳动网络技术有限公司 | Interface test case generation method and device, storage medium and electronic equipment |
| CN111625473B (en) * | 2020-07-01 | 2023-08-22 | 北京字节跳动网络技术有限公司 | Interface test case generation method and device, storage medium and electronic equipment |
| CN112068813A (en) * | 2020-09-03 | 2020-12-11 | 中国平安财产保险股份有限公司 | Data processing method, apparatus and medium |
| CN112367220A (en) * | 2020-10-27 | 2021-02-12 | 深圳市优必选科技股份有限公司 | Interface testing method and device, storage medium and electronic equipment |
| CN112367220B (en) * | 2020-10-27 | 2022-11-29 | 深圳市优必选科技股份有限公司 | Interface testing method and device, storage medium and electronic equipment |
| CN112559319A (en) * | 2020-11-09 | 2021-03-26 | 深圳市六度人和科技有限公司 | Interface bug processing method and device, electronic equipment and storage medium |
| CN112416419A (en) * | 2020-11-16 | 2021-02-26 | 北京五八信息技术有限公司 | Data processing method and device |
| CN112559356A (en) * | 2020-12-18 | 2021-03-26 | 杭州兑吧网络科技有限公司 | Automatic software testing method and system |
| CN115809201A (en) * | 2022-12-23 | 2023-03-17 | 广州市保伦电子有限公司 | Interface test control method, device, equipment and medium based on two-dimensional table |
| CN115809201B (en) * | 2022-12-23 | 2023-10-20 | 广东保伦电子股份有限公司 | Interface test control method, device, equipment and medium based on two-dimensional table |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110704328B (en) | 2021-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110704328B (en) | Interface testing method and device, electronic equipment and readable storage medium | |
| CN111143005B (en) | Application sharing method, electronic equipment and computer readable storage medium | |
| CN107943489B (en) | Data sharing method and mobile terminal | |
| CN109656827B (en) | Control tree generation method and terminal equipment | |
| CN106649126B (en) | Method and device for testing application program | |
| CN110855313B (en) | Signal control method and electronic equipment | |
| CN111049980A (en) | Application sharing method, electronic equipment and computer readable storage medium | |
| CN111143002A (en) | Application sharing method, electronic equipment and computer readable storage medium | |
| CN111597540B (en) | Login method of application program, electronic device and readable storage medium | |
| CN110069407B (en) | Function test method and device for application program | |
| CN112749074B (en) | Test case recommending method and device | |
| CN110225040B (en) | Information processing method and terminal equipment | |
| CN110456923B (en) | Gesture sensing data processing method and electronic equipment | |
| CN109857659B (en) | Control operation method and device | |
| CN109443261B (en) | Method for acquiring folding angle of folding screen mobile terminal and mobile terminal | |
| CN109815349B (en) | Information acquisition method and terminal equipment | |
| CN109218082B (en) | Network configuration parameter processing method, device and equipment | |
| CN109871324B (en) | Control operation method and device | |
| CN111130995B (en) | Image control method, electronic device, and storage medium | |
| CN111556178A (en) | Analytic system, method, equipment and storage medium | |
| CN111209031A (en) | Data acquisition method and device, terminal equipment and storage medium | |
| CN111309390A (en) | Method for acquiring configuration information and electronic equipment | |
| CN111045588B (en) | Information viewing method and electronic equipment | |
| CN110928769B (en) | Method and device for positioning based on applet simulation, electronic equipment and storage medium | |
| CN109783379B (en) | Script execution exception determining method and device |
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 |