CN112306858A

CN112306858A - Test method and device and electronic equipment

Info

Publication number: CN112306858A
Application number: CN202010439561.7A
Authority: CN
Inventors: 邹勇
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Priority date: 2020-05-21
Filing date: 2020-05-21
Publication date: 2021-02-02

Abstract

The embodiment of the disclosure discloses a test method, a test device and electronic equipment. One embodiment of the method comprises: determining whether to test the target API calling code based on at least one predetermined first URL and a second URL corresponding to the target API calling code, wherein the target API calling code is an API calling code executed in response to a first trigger operation; in response to determining to test the target API call code, sending a network request to a test electronic device, wherein the network request is generated by executing the target API call code, the test electronic device returning test data in response to receiving the network request; and determining the test result of the target API call code according to the interaction result with the electronic equipment for test. Thereby a new test mode can be provided.

Description

Test method and device and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a test method and apparatus, and an electronic device.

Background

With the development of the internet, users can implement various functions using terminal devices. Implementation of the various functions described above may require a server to support them. The server may set various Application Programming Interfaces (APIs) for the terminal device to call, so as to provide data required by the terminal device. The terminal device can use the obtained data to realize the corresponding functions.

It can be understood that, after the user operates the user interaction interface (e.g., login interface, search interface), the terminal may execute the API call code to call the API, thereby implementing the corresponding function. In order to prevent the user from having problems when using the corresponding function, the API call code in the terminal needs to be tested in advance.

Disclosure of Invention

This disclosure is provided to introduce concepts in a simplified form that are further described below in the detailed description. This disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

In a first aspect, an embodiment of the present disclosure provides a testing method applied to a terminal device, where the method includes: determining whether to test the target API calling code based on at least one predetermined first URL and a second URL corresponding to the target API calling code, wherein the target API calling code is an API calling code executed in response to a first trigger operation; in response to determining to test the target API call code, sending a network request to a test electronic device, wherein the network request is generated by executing the target API call code, the test electronic device returning test data in response to receiving the network request; and determining the test result of the target API call code according to the interaction result with the electronic equipment for testing.

In a second aspect, an embodiment of the present disclosure provides a testing method applied to a server, where the method includes: in response to receiving a network request, determining a fourth URL consistent with the second URL in the network request, wherein the network request comprises the second URL corresponding to the target API calling code, the target API calling code is an API calling code executed by the terminal in response to the first trigger operation, and the test data corresponds to the fourth URL; acquiring test data corresponding to the determined fourth URL; and returning the acquired test data.

In a third aspect, an embodiment of the present disclosure provides a testing apparatus, applied to a terminal device, including: a first determining unit, configured to determine whether to test a target API call code based on at least one predetermined first URL and a second URL corresponding to the target API call code, where the target API call code is an API call code executed in response to a first trigger operation; a sending unit, configured to send, in response to determining to test the target API call code, a network request to a test electronic device, where the network request is generated by executing the target API call code, and the test electronic device returns test data in response to receiving the network request; and the second determining unit is used for determining the test result of the target API call code according to the interaction result with the electronic equipment for test.

In a fourth aspect, an embodiment of the present disclosure provides a testing apparatus, applied to a server, including: the first determining module is used for determining a fourth URL consistent with the second URL in the network request in response to receiving the network request, wherein the network request comprises the second URL corresponding to the target API calling code, the target API calling code is an API calling code executed by the terminal in response to the first trigger operation, and the test data corresponds to the fourth URL; the acquisition module is used for acquiring the test data corresponding to the determined fourth URL; a return module for returning the acquired test data

In a fifth aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the test method according to the first aspect or the second aspect.

In a sixth aspect, embodiments of the present disclosure provide a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the steps of the testing method of the first or second aspect as described above.

According to the testing method, the testing device and the electronic equipment, whether the target API calling code is tested or not is determined based on the predetermined first URL and the second URL corresponding to the target API calling code; therefore, whether the target API calling code needs to be tested or not can be determined quickly, and the testing speed is improved. If yes, sending a network request to the electronic equipment for testing; then, determining a test result of the target API call code according to an interaction result with the electronic equipment for testing; therefore, a new testing mode can be provided, and the electronic equipment for testing can provide testing service for the plurality of terminal equipment and can also provide testing service for one terminal for multiple times, so that the testing cost is reduced.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

FIG. 1 is a flow diagram of one embodiment of a testing method according to the present disclosure;

FIG. 2 is a schematic diagram of one application scenario of a testing method according to the present disclosure;

FIG. 3 is a flow chart of an exemplary implementation of step 101 according to the present disclosure;

FIG. 4 is a flow chart of an exemplary implementation of step 101 according to the present disclosure;

FIG. 5 is a flow diagram of yet another embodiment of a testing method according to the present disclosure;

FIG. 6 is a schematic diagram of an application scenario of the corresponding test method of FIG. 5;

FIG. 7 is a schematic diagram of another application scenario of the corresponding test method of FIG. 5;

FIG. 8A is a flow diagram for one embodiment of another testing method according to the present disclosure;

FIG. 8B is a flowchart of an exemplary implementation of step 803 according to the present disclosure;

FIG. 9A is an exemplary schematic of an input interface according to the present disclosure;

FIG. 9B is another exemplary schematic of an input interface according to the present disclosure;

FIG. 10 is a schematic structural diagram of one embodiment of a testing device according to the present disclosure;

FIG. 11 is a schematic block diagram of an embodiment of another testing device according to the present disclosure;

FIG. 12 is an exemplary system architecture to which the testing method of one embodiment of the present disclosure may be applied;

fig. 13 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

Referring to fig. 1, a flow of one embodiment of a testing method according to the present disclosure is shown. The test method is applied to the terminal equipment. The test method as shown in fig. 1 includes the following steps:

step 101, determining whether to test the target API call code based on at least one predetermined first URL and a second URL corresponding to the target API call code.

In this embodiment, an execution subject (for example, a terminal device) of the test method may determine whether to test the target API call code based on at least one predetermined first URL and a second URL corresponding to the target API call code.

Here, the target API call code is API call code executed in response to the first trigger operation.

It is understood that an Application Programming Interface (API) may be a predefined function for implementing a contract for joining different components of a software system. The goal is to provide applications and developers the ability to access a set of routines based on certain software or hardware without having to access native code or understand the details of the internal workings.

Here, a Uniform Resource Locator (URL) may indicate a path of the API provided by the server.

Generally, the execution subject may preset a plurality of API call codes, and the plurality of API call codes may be partly tested and partly not tested. At least one first URL may be predetermined, and the first URL may indicate an API call code that needs to be tested.

In this embodiment, at least one API calling code may be set in the execution body. The target API calling code may be any one of the at least one API calling codes.

By way of example, the execution agent may include at least one of the following API call codes, but is not limited to: search API call codes, login API call codes, upload data API call codes, and the like.

Here, the target API call code may be an API call code executed by the execution subject in response to detection of the first trigger operation. The first trigger operation described above may be predefined.

As an example, the first trigger operation may be an operation (e.g., a click operation) to initiate a search control in a search interface.

By way of example, a login interface of the terminal may include a username entry control, a password entry control, and a send control. The user may enter a username in a username entry control, enter a password in a password entry control, and then click on a send control. Clicking the sending control can be regarded as a predefined first triggering operation, and the triggered API calling code can be a login API calling code; the API call code for logging in the API may be determined as a target API call code.

Step 102, in response to determining to test the target API call code, sending a network request to the electronic device for testing.

In this embodiment, the execution body may send a network request to the electronic device for test in response to determining to test the target API call code.

Here, the network request is generated by executing the target API call code.

Here, the execution agent executes the API call code to generate a network request. The network request can be sent to the real service server without testing the API call code. Under the condition of testing the API call code, the login API call code can be tested by utilizing a preset testing method.

As an example, the login API call code may generate a network request and send the network request. The generated network request may include a path indicating a login to the API, a username and password entered by the user. If the login API call code needs to be tested, the login API call code can be tested by a preset testing method. If the login API call code needs to be tested, the network request can be sent to a real service server, the real service server can start the API according to a path in the received network request, and the API returns a login result to the terminal.

Referring to FIG. 2, an application scenario for determining target API call code is shown.

In fig. 2, a login interface is taken as an example, and a word "please login" is displayed on the interface to prompt the user. A username fill-in control 201, a password fill-in control 202, and a login confirmation control 203 are provided in fig. 2.

And then, the user can perform the first trigger operation in the user interaction interface. Taking the login interface shown in fig. 2 as an example, the user may click the login confirmation control, and the terminal may execute the login API call code in response to detecting the trigger operation. The terminal may then determine the target API call code from this login API call code.

Here, the test electronics return test data in response to receiving the network request.

Here, the test electronic device may transmit test data to the execution body in response to receiving the network request. It is understood that the electronic device for testing may or may not receive the network request.

It should be noted that the test electronic device is provided to store test data collectively. The test data is set once, and can be provided for the terminal for multiple times or simultaneously provided for multiple terminals.

And 103, determining a test result of the target API call code according to the interaction result with the electronic equipment for testing.

In this embodiment, the execution body may determine a test result of the target API call code according to an interaction result with the electronic device for testing.

In some embodiments, the interaction result may include, but is not limited to: the test data is received, the test data is not received, the received test data is correct, and the received test data is wrong.

In some embodiments, if the interaction result is that no test data is received, the test result may be determined to be that the API call code is in error; if the interaction result is that the test data is received, whether the received test data is correct or wrong can be determined, and if the received test data is correct, the test result can be determined to be that the API calling code is correct; if so, the test result may be determined to be that the API call code is in error.

It should be noted that, in the method provided by the embodiment corresponding to fig. 1, whether to test the target API call code is determined based on a predetermined first URL and a second URL corresponding to the target API call code; therefore, whether the target API calling code needs to be tested or not can be determined quickly, and the testing speed is improved. If yes, sending a network request to the electronic equipment for testing; then, determining a test result of the target API call code according to an interaction result with the electronic equipment for testing; therefore, a new testing mode can be provided, and the electronic equipment for testing can provide testing service for the plurality of terminal equipment and can also provide testing service for one terminal for multiple times, so that the testing cost is reduced.

In some embodiments, the steps shown in fig. 1 may be performed by the same client (which may also be understood as an application installed in the terminal), that is, step 101 may be performed in the application, and a change in network settings of the terminal may be avoided, that is, a step of configuring a network agent of the terminal is omitted, so that agent software does not need to be set or a network certificate or the like needs to be configured, thereby saving cost and reducing configuration steps before testing.

In some embodiments, please refer to fig. 3, which illustrates an implementation of step 101, which may include:

step 301, in response to detecting the first trigger operation, determining a target API call code according to the first trigger operation.

Here, the execution subject may determine, in response to detecting a predefined trigger operation on the API call code, the API call code triggered by the predefined trigger operation as the target API call code.

In step 302, it is determined whether a first URL exists that matches a second URL in at least one first URL.

Step 303, in response to determining to exist, determines to test the target API call code.

It should be noted that, the target API calling code is determined first, and then it is determined whether there is a first URL that is consistent with the second URL in the first URL; where present, the target API call code is determined to be tested. Thus, without operating (for example, labeling) each of the first URLs, after the target API call code is determined, the second URL is compared with a part of the first URLs, and the comparison is stopped if the second URL is determined to be consistent with the part of the first URL, thereby possibly reducing the amount of calculation for determining whether to test the target API call code based on at least one of the first URLs and increasing the speed of determining whether to test.

Referring to fig. 4, another implementation of step 101 is shown, which may include:

step 401, selecting an API calling code according to at least one first URL, and establishing an association relationship between the URL corresponding to the selected API calling code and the test tag.

It can be understood that the association relationship between the URL corresponding to the API calling code and the test tag may also be referred to as marking a test tag on the second URL.

After the terminal device determines at least one first URL, if the URL corresponding to the API calling code is consistent with the first URL, the terminal device marks a test tag on the URL corresponding to the API calling code. It is to be understood that the API call code selected here may be an API call code that meets the condition that "the corresponding URL coincides with the first URL" in the terminal device.

Step 402, in response to detecting the first trigger operation, determining a target API call code according to the first trigger operation.

Here, the execution agent may determine, in response to detecting a predefined first trigger operation on the API call code, the API call code triggered by the first trigger operation as the target API call code.

At step 403, in response to determining that the second URL of the target API call code is associated with the test tag, determining to test the target API call code.

It should be noted that after the terminal device determines at least one first URL, if the URL corresponding to the API call code is consistent with the first URL, a test tag is marked on the URL corresponding to the API call code, and after the target API is determined, it may be determined whether to test the target API call code by determining whether the second URL has the test tag. Thus, the amount of calculation after the target API call code is determined can be reduced, and the response speed to the first trigger operation can be improved (that is, if the API call code does not need to be tested, the required data can be quickly returned by the real service server).

With continued reference to fig. 5, a flow of another embodiment of the testing method according to the present disclosure is shown, which may specifically include:

step 501, displaying a configuration interface.

In this embodiment, the execution subject may present a configuration interface, and the configuration interface may include at least one third URL.

In this embodiment, the configuration interface may include at least one URL as the API identification. I.e. the configuration interface may expose at least one API identity.

In some embodiments, the API identification may be an API name, such as "login interface.

It will be appreciated that the above-mentioned URL (i.e., API identification) may indicate an API, and may also indicate API call code. The worker can understand that the API identification can indicate the API calling code, and the API calling code needing to be tested can be set by selecting the API identification.

Optionally, the API indicated by the URL may be an empty shell. That is, at the service end, the API indicated by the API identifier (capable of formally providing the service) may not be established yet, i.e., may not work normally.

Optionally, the configuration interface may be a web page, and the configuration interface may also be a native interface. The server may return a web page in response to the user's operation, the web page including the at least one third URL. Alternatively, the server may send the at least one third URL to the terminal in advance, and the terminal generates a configuration interface including the third URL in response to detecting the user operation.

Generally, the execution subject may preset a plurality of API call codes, and the plurality of API call codes may be partly tested and partly not tested. The execution principal may present a configuration interface in response to an operation by a user. The user can select the third URL from the at least one third URL in the configuration interface to determine the API calling code needing to be tested.

In this embodiment, the preset test electronic device stores the test data corresponding to the fourth URL.

In this embodiment, the at least one third URL in the configuration interface may be a URL sent by the test electronic device to the execution main body. The test electronic device may send a fourth URL corresponding to the test data to the execution main body. It is understood that the fourth URL stored after the execution body receives the third URL may be referred to as a third URL.

Referring to fig. 6, a schematic diagram of a terminal presentation configuration interface is shown. In fig. 6, the prompt word "select URL" may be shown, and a first URL601, a second URL602, and a third URL603 may also be shown; "/api/hello/world" "/api/hello/world 2" "/api/hello/world 3" may be an exemplary URL.

Then, the user can select one or at least two URLs according to the URL selection operation in the configuration interface. For example, the selection operation may be for URL number one 601, and after selection, the URL region may be changed in color to distinguish from the unselected URLs.

Then, the terminal device may take the URL selected by the user as the first URL.

Step 502, in response to detecting a predefined selection operation in the configuration interface, determining at least one first URL according to a third URL targeted by the selection operation.

Here, the third URL to which the selection operation is directed may be determined as the first URL.

Optionally, the selection operation may be a single selection operation or a multiple selection operation. The number of the third URLs for which the selection operation is performed may be one or at least two.

Step 503, determining whether to test the target API calling code based on at least one predetermined first URL and a second URL corresponding to the target API calling code.

Here, the API call code corresponds to the second URL.

In some embodiments, it is determined to test the target API call code if the second URL to which the target API call code corresponds is in the at least one first URL. And if the second URL corresponding to the calling code of the target API is not in the at least one first URL, determining not to test the target API.

In some embodiments, it may be predetermined whether each second URL is in at least one first URL, and if so, the second URL may be tagged with a test tag. After the target API calling code is determined in response to the detection of the predefined trigger operation, if a second URL corresponding to the target API calling code has a test tag, determining to test the target API calling code; and if the second URL corresponding to the target API calling code does not have the test tag, determining not to test the target API calling code.

In some embodiments, the execution agent may send the network request in response to determining that the target API is not tested, and the target API calls the normal electronic device corresponding to the code. Here, the normal electronic device may perform processing such as analysis on the network request, generate a request result corresponding to the network request, and return the request result to the execution main unit. As an example, the network request may be a search request, and the normal electronic device may perform processing such as parsing on the search request, generate a search result corresponding to the search request, and return the search result to the execution main body.

Step 504, in response to determining to test the target API call code, sending a network request to the electronic device for testing.

Here, the network request may include a second URL corresponding to the target API call code.

And 505, determining a test result of the target API call code according to the interaction result with the electronic equipment for test.

Here, the execution agent may determine a test result of the target API call code according to an interaction result with the electronic device for test.

The method provided by the corresponding embodiment of fig. 5 of the present disclosure is to show a third URL in the configuration interface, and then the user makes a selection operation for the third URL, and generates at least one first URL according to the third URL for which the selection operation is directed; then, based on the at least one first URL, determining whether to test a target API call code of the at least one API call code, where the target API call code may be an API call code executed by the terminal device in response to the first trigger operation, and the technical effects may include at least: firstly, a third URL capable of being selected is provided for a user through a configuration interface, so that the user can rapidly configure at least one first URL, the URLs needing to be tested can be added, deleted, changed and checked, and the method is rapid and convenient; secondly, through at least one first URL, when the terminal device executes the API calling code, whether the currently executed API calling code needs to be tested or not can be quickly determined, and therefore testing speed can be improved.

Referring to fig. 7, a diagram of an application scenario of the embodiment shown in fig. 5 is shown. The method comprises the following specific steps:

first, the user may set the fourth URL and the corresponding test data in the input device 702 of the test electronic device 701. Input device 702 may then send the fourth URL and corresponding test data to test electronics 701. The test electronic device may store the fourth URL and the test data in correspondence.

Then, the user may open the configuration interface 7031 of the terminal device 703, and the URL supported by the electronic device for testing may be displayed on the configuration interface, where the URL displayed by the configuration interface may be referred to as a third URL. It will be appreciated that the test electronic device may send a fourth URL to the terminal device, and for ease of distinction, the fourth URL received by the terminal device may be referred to as the third URL.

The user may then select a third URL at the configuration interface.

Then, the terminal device may determine the third URL selected by the user as the first URL, and generate at least one first URL 7032.

And then, the user can make a first trigger operation on a user interaction interface of the terminal equipment. Triggering the terminal equipment to execute a certain API calling code. It will be appreciated that after the API call code is triggered, a network request may be generated that includes the second URL.

Then, the terminal device may determine the API call code triggered to be executed as the target API call code, and execute the determining step 7033: based on the at least one first URL, it is determined whether to send a network request to the test electronic device. It will be appreciated that if a determination is made to send to the test electronics 702, then the API calls code to determine the target for testing. If it is determined not to be sent to the test electronic device, the code is called to determine not to test the target API. If the network request is not a network request to be tested, the network request not to be tested may be sent to the real service server 704, and the service server processes the network request not to be tested and returns service data.

Referring to FIG. 8A, a flow chart 800 of one embodiment of a method for returning test data for use with a test electronic device is shown. The execution of the process 800 is directed to test electronics.

The process 800 may include:

step 801, in response to receiving the network request, determines a fourth URL that is consistent with the second URL in the network request.

In this embodiment, the network request sent by the terminal device may include a second URL corresponding to the target API call code. The test data in the test electronic device may correspond to the fourth URL. In other words, a plurality of fourth URLs may be stored in the test electronic device, each fourth URL corresponding to test data. Optionally, the test data corresponding to any two fourth URLs may be the same or different.

Here, the target API call code is an API call code that the terminal executes in response to the first trigger operation.

In this embodiment, the test electronic device may determine, in response to receiving the network request, a fourth URL that is consistent with the second URL in the network request, and may then obtain test data corresponding to the determined URL.

Step 802, obtaining the test data corresponding to the determined fourth URL.

Step 803, test data is returned.

In this embodiment, the test electronic device may return test data according to the acquired test data.

It should be noted that the test electronic device is provided to store test data. The test data is set once, and can be provided for the terminal for multiple times or simultaneously provided for multiple terminals. The electronic equipment for testing can provide testing service for the plurality of terminal equipment and can also provide testing service for one terminal for a plurality of times, so that the testing cost is reduced.

In some embodiments, step 803 may include: and returning the acquired test data to the terminal equipment.

In some embodiments, the correspondence between the fourth URL and the test data may be established by: presenting an input interface, where the input interface may include a first control, a second control, and a third control; and responding to the detection of the predefined trigger operation on the third control, acquiring the URL received by the first control, acquiring the test data received by the second control, and establishing a corresponding relation between the acquired URL and the acquired test data.

Referring to fig. 9A, fig. 9A is an exemplary diagram of an input interface. In FIG. 9A, a first control 901, a second control 902, and a third control 903 are shown. The first control 901 may expose a typeface of "please enter path" to prompt entry of a URL, "/api/hello/world" may be an exemplary URL. The second control 902 may present a typeface of "please enter test data," which may be exemplary test data. The third control 903 may show a "confirm" typeface.

In some embodiments, FIG. 8B illustrates an exemplary implementation of step 803. Specifically, the test method may include:

step 8031, determining test data corresponding to the user identifier in the network request from the obtained test data.

In some embodiments, the network request sent by the terminal device may include a user identifier. Alternatively, the user identification may indicate the generation of the code or the tester.

In some embodiments, the test electronic device may store test data corresponding to a user identification.

In this embodiment, the electronic device for testing may determine, from the obtained test data, the test data corresponding to the user identifier in the network request.

Step 8032, return the test data corresponding to the user id in the network request.

In this embodiment, the test electronic device may return the test data determined in step 8031 to the terminal device.

It should be noted that by setting the user identifier, different test data can be set for the same URL. This makes it possible to test the same URL (i.e., the same API) by a plurality of worker tests, but the test data obtained by each worker may be different.

In some embodiments, the input interface may further include a fourth control. The corresponding relation between the test data and the user identification can be established in the following way: and in response to the detection of the predefined trigger operation on the third control, acquiring the test data received by the first control and the user identification received by the fourth control, and establishing a corresponding relation between the acquired test data and the acquired user identification.

Referring to fig. 9B, fig. 9B is another exemplary diagram of an input interface. In fig. 9B, a first control 901, a second control 902, a third control 903, and a fourth control 904 are shown. The first control 901 may expose a typeface of "please enter path" to prompt entry of a URL, "/api/hello/world" may be an exemplary URL. The second control 902 may present a typeface of "please enter test data," which may be exemplary test data. The third control 903 may show a "confirm" typeface. The fourth control 904 may present a typeface of "please enter user identification," which may be user identification.

With further reference to fig. 10, as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of a testing apparatus, which corresponds to the embodiment of the method shown in fig. 1, and which may be specifically applied to various electronic devices, for example, may be applied to a terminal device.

As shown in fig. 10, the test apparatus of the present embodiment includes: a first determination unit 1001, a transmission unit 1002, and a second determination unit 1003. The first determining unit is used for determining whether to test the target API calling code based on at least one first URL determined in advance and a second URL corresponding to the target API calling code, wherein the target API calling code is an API calling code executed in response to a first trigger operation; a sending unit, configured to send, in response to determining to test the target API call code, a network request to a test electronic device, where the network request is generated by executing the target API call code, and the test electronic device returns test data in response to receiving the network request; and the second determining unit is used for determining the test result of the target API call code according to the interaction result with the electronic equipment for test.

In this embodiment, specific processes of the first determining unit 1001, the sending unit 1002, and the second determining unit 1003 of the testing apparatus and technical effects brought by the specific processes may refer to related descriptions of step 101, step 102, and step 103 in the corresponding embodiment of fig. 1, which are not described herein again.

In some optional implementations, the at least one first URL is determined by: presenting a configuration interface, wherein the configuration interface comprises at least one third URL; in response to detecting a predefined selection operation in the configuration interface, at least one first URL is determined in accordance with a third URL to which the selection operation is directed.

In some optional implementations, the second URL corresponding to the target API call code based on the predetermined at least one first URL includes: in response to detecting the first trigger operation, determining a target API call code according to the first trigger operation; determining whether there is a first URL that coincides with the second URL among the at least one first URL; in response to determining that there is, determining to test the target API call code.

With further reference to fig. 11, as an implementation of the method shown in the above-mentioned figures, the present disclosure provides an embodiment of a testing apparatus, which corresponds to the method embodiment shown in fig. 8A, and which may be specifically applied to various electronic devices, for example, a server.

As shown in fig. 11, the test apparatus of the present embodiment includes: a first determination module 1101, an acquisition module 1102 and a return module 1103. The first determining module is configured to determine, in response to receiving a network request, a fourth URL consistent with a second URL in the network request, where the network request includes the second URL corresponding to the target API call code, the target API call code is an API call code executed by the terminal in response to the first trigger operation, and the test data corresponds to the fourth URL; the acquisition module is used for acquiring the test data corresponding to the determined fourth URL; and the return module is used for returning the acquired data for the test.

In this embodiment, specific processing of the first determining module 1101, the obtaining module 1102 and the returning module 1103 of the testing apparatus and technical effects thereof may refer to related descriptions of step 801, step 802 and step 803 in the corresponding embodiment of fig. 1, which are not described herein again.

In some optional implementations, the correspondence between the fourth URL and the test data is generated by: displaying an input interface, wherein the input interface comprises a first control, a second control and a third control; and responding to the detection of a second trigger operation on the third control, acquiring the URL received by the first control, acquiring the test data received by the second control, and establishing a corresponding relation between the acquired URL and the acquired test data.

In some optional implementations, the network request includes a user identifier, and the test data corresponds to the user identifier; and returning the acquired test data, comprising: determining test data corresponding to the user identification in the network request from the acquired test data; and returning the test data corresponding to the user identification in the network request.

In some alternative implementations, the input interface further includes a fourth control; and the corresponding relation between the test data and the user identification is established in the following way: and responding to the detection of a second trigger operation on the third control, acquiring the test data received by the first control and the user identification received by the fourth control, and establishing a corresponding relation between the acquired test data and the acquired user identification.

Referring to fig. 12, fig. 12 illustrates an exemplary system architecture to which the testing method of one embodiment of the present disclosure may be applied.

As shown in fig. 12, the system architecture may include

terminal devices

1201, 1202, 1203, network 1204,

servers

1205, 1206. Network 1204 is the medium used to provide communication links between

terminal devices

1201, 1202, 1203 and

servers

1205, 1206. Network 1204 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

Terminal devices

1201, 1202, 1203 may interact with

servers

1205, 1206 through network 1204 to receive or send messages, etc. The

terminal devices

1201, 1202, 1203 may have various client applications installed thereon, such as a web browser application, a search-type application, and a news-information-type application. The client application in the

terminal devices

1201, 1202, 1203 may receive an instruction of the user, and complete a corresponding function according to the instruction of the user, for example, generate an execution API call code according to the instruction of the user to generate a network request, and the like. The

terminal devices

1201, 1202, 1203 may store API calling codes, which may or may not be tested.

The

terminal apparatuses

1201, 1202, 1203 may be hardware or software. When the

terminal devices

1201, 1202, 1203 are hardware, they may be various electronic devices with a display screen, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg Audio Layer 4), laptop portable computers, desktop computers, and the like. When the

terminal apparatuses

1201, 1202, 1203 are software, they may be installed in the electronic apparatuses listed above. It may be implemented as multiple pieces of software or software modules (e.g., software or software modules used to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.

The server 1206 may be a server that provides test data, for example, receives a URL transmitted by the

terminal apparatuses

1201, 1202, 1203, acquires the test data in various ways according to the URL, and transmits the acquired test data to the

terminal apparatuses

1201, 1202, 1203.

The server 1206 may be a server providing various services, for example, receive an information acquisition request sent by the

terminal apparatuses

1201, 1202, 1203, acquire presentation information corresponding to the information acquisition request in various ways according to the information acquisition request, and send relevant data of the presentation information to the

terminal apparatuses

1201, 1202, 1203.

It should be noted that the test method provided by the embodiment of the present disclosure may be executed by a terminal device, and accordingly, the test apparatus may be disposed in the

terminal devices

1201, 1202, and 1203. The testing method provided by the embodiment of the disclosure can be executed by a server, and accordingly, a testing device can be arranged in the server 1205.

It should be understood that the number of terminal devices, networks, and servers in fig. 12 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to fig. 13, shown is a schematic diagram of an electronic device (e.g., the terminal device or server of fig. 12) suitable for use in implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 13, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 1301 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1302 or a program loaded from a storage device 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation of the electronic apparatus 1300 are also stored. The processing device 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

Generally, the following devices may be connected to the I/O interface 1305: input devices 1306 including, for example, touch screens, touch pads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, and the like; an output device 1307 including, for example, a Liquid Crystal Display (LCD), speaker, vibrator, etc.; storage devices 1308 including, for example, magnetic tape, hard disk, etc.; and a communication device 1309. The communication means 1309 may allow the electronic device to communicate wirelessly or by wire with other devices to exchange data. While fig. 13 illustrates an electronic device having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via the communication means 1309, or installed from the storage device 1308, or installed from the ROM 1302. The computer program, when executed by the processing apparatus 1301, performs the functions defined in the methods of the embodiments of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: determining whether to test the target API calling code based on at least one predetermined first URL and a second URL corresponding to the target API calling code, wherein the target API calling code is an API calling code executed in response to a first trigger operation; in response to determining to test the target API call code, sending a network request to a test electronic device, wherein the network request is generated by executing the target API call code, the test electronic device returning test data in response to receiving the network request; and determining the test result of the target API call code according to the interaction result with the electronic equipment for testing.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: in response to receiving a network request, determining a fourth URL consistent with the second URL in the network request, wherein the network request comprises the second URL corresponding to the target API calling code, the target API calling code is an API calling code executed by the terminal in response to the first trigger operation, and the test data corresponds to the fourth URL; acquiring test data corresponding to the determined fourth URL; and returning the acquired test data.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, a sending unit may also be described as a "unit sending a network request".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method of testing, comprising:

determining whether to test the target API calling code based on at least one predetermined first URL and a second URL corresponding to the target API calling code, wherein the target API calling code is an API calling code executed in response to a first trigger operation;

in response to determining to test the target API call code, sending a network request to a test electronic device, wherein the network request is generated by executing the target API call code, the test electronic device returning test data in response to receiving the network request;

and determining the test result of the target API call code according to the interaction result with the electronic equipment for testing.

2. The method of claim 1, wherein the at least one first URL is determined by:

presenting a configuration interface, wherein the configuration interface comprises at least one third URL;

in response to detecting a predefined selection operation in the configuration interface, at least one first URL is determined in accordance with a third URL to which the selection operation is directed.

3. The method of claim 1, wherein determining whether to test the target API call code based on the predetermined at least one first URL and a second URL corresponding to the target API call code comprises:

in response to detecting the first trigger operation, determining a target API call code according to the first trigger operation;

determining whether there is a first URL that coincides with the second URL among the at least one first URL;

in response to determining that there is, determining to test the target API call code.

4. A method of testing, comprising:

in response to receiving a network request, determining a fourth URL consistent with the second URL in the network request, wherein the network request comprises the second URL corresponding to a target API calling code, the target API calling code is an API calling code executed by the terminal in response to a first trigger operation, and test data corresponds to the fourth URL;

acquiring test data corresponding to the determined fourth URL;

and returning the acquired test data.

5. The method of claim 4, wherein the correspondence between the fourth URL and the test data is generated by:

displaying an input interface, wherein the input interface comprises a first control, a second control and a third control;

and responding to the detection of a second trigger operation on the third control, acquiring the URL received by the first control, acquiring the test data received by the second control, and establishing a corresponding relation between the acquired URL and the acquired test data.

6. The method of claim 4, wherein the network request includes a subscriber identity, and wherein the test data corresponds to the subscriber identity; and

the returning the acquired test data includes:

determining test data corresponding to the user identification in the network request from the acquired test data;

and returning the test data corresponding to the user identification in the network request.

7. The method of claim 6, wherein the input interface further comprises a fourth control; and

the corresponding relation between the test data and the user identification is established in the following way:

and responding to the detection of a second trigger operation on the third control, acquiring the test data received by the first control and the user identification received by the fourth control, and establishing a corresponding relation between the acquired test data and the acquired user identification.

8. A test apparatus, comprising:

a first determining unit, configured to determine whether to test a target API call code based on at least one predetermined first URL and a second URL corresponding to the target API call code, where the target API call code is an API call code executed in response to a first trigger operation;

a sending unit, configured to send, in response to determining to test the target API call code, a network request to a test electronic device, where the network request is generated by executing the target API call code, and the test electronic device returns test data in response to receiving the network request;

and the second determining unit is used for determining the test result of the target API call code according to the interaction result with the electronic equipment for test.

9. A test apparatus, comprising:

the first determining module is used for determining a fourth URL consistent with the second URL in the network request in response to the network request, wherein the network request comprises the second URL corresponding to a target API calling code, the target API calling code is an API calling code executed by the terminal in response to the first trigger operation, and the test data corresponds to the fourth URL;

the acquisition module is used for acquiring the test data corresponding to the determined fourth URL;

and the return module is used for returning the acquired data for the test.

10. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-3 or any one of claims 4-7.

11. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 3 or according to any one of claims 4 to 7.