CN111563038A - SDK test method, device, computer equipment and computer readable storage medium - Google Patents
SDK test method, device, computer equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN111563038A CN111563038A CN202010360273.2A CN202010360273A CN111563038A CN 111563038 A CN111563038 A CN 111563038A CN 202010360273 A CN202010360273 A CN 202010360273A CN 111563038 A CN111563038 A CN 111563038A
- Authority
- CN
- China
- Prior art keywords
- sdk
- result
- test
- testing
- integrated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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
- 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
Abstract
The invention discloses an SDK test method, which can improve the test accuracy and save the test resources, and comprises the following steps: testing the SDK to obtain a first test result; under the condition that the first test result represents that the SDK is normal in function, integrating the SDK to a client to obtain an integrated SDK; testing the integrated SDK to obtain a second test result; and determining whether the function of the integrated SDK is normal or not according to the second test result. The invention also provides an SDK testing device, a computer device and a computer readable storage medium.
Description
Technical Field
The invention relates to the technical field of data acquisition, in particular to an SDK testing method, an SDK testing device, computer equipment and a computer readable storage medium.
Background
The SDK (Software Development Kit) can provide a set of external Development interfaces with certain structures and logics, and encapsulate internal business logics. The caller can realize the expected function by using the corresponding external development interface according to the description document, thereby simplifying the development process of the software and ensuring the quality of the software to a certain extent. With the continuous popularization of the SDK in the field of software development, it is more and more important to test the accuracy of data sent by the SDK.
However, the inventors found in the course of studying the present invention that: in the prior art, only the SDK installed on the application program is tested, and the phenomenon that the SDK is incompatible with the application program due to abnormal functions frequently occurs in an actual scene, so that the test scheme in the prior art cannot accurately and effectively realize the purpose of testing the SDK, the test flow is increased, and the test resources are wasted.
Disclosure of Invention
The invention aims to provide an SDK testing method, an SDK testing device, computer equipment and a computer readable storage medium, which can solve the technical problems that the SDK cannot be accurately and effectively tested, the testing process is complex and testing resources are wasted in the prior art.
One aspect of the present invention provides an SDK testing method, including: testing the SDK to obtain a first test result; under the condition that the first test result represents that the SDK is normal in function, integrating the SDK to a client to obtain an integrated SDK; testing the integrated SDK to obtain a second test result; and determining whether the function of the integrated SDK is normal or not according to the second test result.
Optionally, the step of testing the SDK to obtain a first test result includes: acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters; inputting the input parameters into the SDK, and acquiring an output result output by the SDK; comparing the output result with the first expected result to obtain the first test result; when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
Optionally, the input parameters comprise at least one of forward input parameters, reverse input parameters and missing input parameters.
Optionally, the step of testing the integrated SDK to obtain a second test result includes: acquiring a second test case, wherein the second test case comprises a test rule and a second expected result corresponding to the test rule; executing the operation specified in the test rule on the client; obtaining a response result output by the client after the integrated SDK responds to the operation; comparing the response result with the second expected result to obtain a second test result; when the second test result is that the response result is consistent with the second expected result, the integrated SDK is characterized to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, characterizing that the integrated SDK is not functioning normally.
Optionally, integrating the SDK into the client, where the obtaining of the integrated SDK includes: respectively integrating the SDK to each client in a plurality of clients to obtain a plurality of integrated SDKs; correspondingly, the step of testing the integrated SDK to obtain a second test result comprises the following steps: acquiring identification information corresponding to each client; determining a second test case corresponding to each identification information; and testing each integrated SDK according to the determined second test case corresponding to each identification information to obtain a second test result of each integrated SDK.
Optionally, the identification information includes a device identifier of a terminal device on which the client is installed.
Another aspect of the present invention provides an SDK testing apparatus, including: the first testing module is used for testing the SDK to obtain a first testing result; the integration module is used for integrating the SDK to a client side to obtain an integrated SDK under the condition that the first test result represents that the SDK is normal in function; the second testing module is used for testing the integrated SDK to obtain a second testing result; and the determining module is used for determining whether the function of the integrated SDK is normal or not according to the second test result.
Optionally, the first test module is further configured to: acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters; inputting the input parameters into the SDK, and acquiring an output result output by the SDK; comparing the output result with the first expected result to obtain the first test result; when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
Optionally, the input parameters comprise at least one of forward input parameters, reverse input parameters and missing input parameters.
Optionally, the second testing module is further configured to: acquiring a second test case, wherein the second test case comprises a test rule and a second expected result corresponding to the test rule; executing the operation specified in the test rule on the client; obtaining a response result output by the client after the integrated SDK responds to the operation; comparing the response result with the second expected result to obtain a second test result; when the second test result is that the response result is consistent with the second expected result, the integrated SDK is characterized to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, characterizing that the integrated SDK is not functioning normally.
Optionally, the integration module is further configured to: respectively integrating the SDK to each client in a plurality of clients to obtain a plurality of integrated SDKs; correspondingly, the second testing module is further configured to: acquiring identification information corresponding to each client; determining a second test case corresponding to each identification information; and testing each integrated SDK according to the determined second test case corresponding to each identification information to obtain a second test result of each integrated SDK.
Optionally, the identification information includes a device identifier of a terminal device on which the client is installed.
Yet another aspect of the present invention provides a computer apparatus, comprising: the test system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the steps of the SDK test method introduced in any one of the above embodiments.
Yet another aspect of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the SDK testing method described in any of the above embodiments.
The SDK testing method provided by the invention firstly performs function testing on the SDK which is not integrated to the client, integrates the SDK to the client when a testing result represents that the function of the SDK which is not integrated to the client is normal, and then performs function testing on the SDK which is integrated to the client. According to the invention, the SDK is subjected to double testing through two testing processes, and the second testing process is carried out only when the first testing process passes, so that the accuracy of the testing result can be effectively improved, invalid testing is avoided, the overall testing efficiency is improved, and the testing resources are saved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 schematically illustrates a flow chart of a method of testing an SDK according to an embodiment of the present invention;
FIG. 2 schematically illustrates a block diagram of an SDLK testing apparatus according to an embodiment of the present invention;
fig. 3 schematically shows a block diagram of a computer device suitable for implementing the SDK testing method according to an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the 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.
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.
The SDK testing method provided by the invention firstly performs function testing on the SDK which is not integrated to the client, integrates the SDK to the client when a testing result represents that the function of the SDK which is not integrated to the client is normal, and then performs function testing on the SDK which is integrated to the client. According to the invention, the SDK is subjected to double testing through two testing processes, and the second testing process is carried out only when the first testing process passes, so that the accuracy of the testing result can be effectively improved, invalid testing is avoided, the overall testing efficiency is improved, and the testing resources are saved. Specifically, fig. 1 schematically shows a flowchart of an SDK testing method according to an embodiment of the present invention. As shown in fig. 1, the SDK testing method may include steps S101 to S104, where:
step S101, testing the SDK to obtain a first test result.
In this embodiment, the execution subject may be a test server, and after the developer completes development of the SDK and before the SDK is integrated into the client, the test server may implant the SDK first, and then test the function of the SDK, so as to ensure that the function of the SDK itself is normal.
Alternatively, step S101 may include: acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters; inputting the input parameters into the SDK, and acquiring an output result output by the SDK; comparing the output result with the first expected result to obtain the first test result; when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
It should be noted that, the SDK described in this embodiment refers to a jar packet that is developed and is not yet implanted in the client, and in order to verify whether the function of the SDK is normal, the SDK may be tested first, but because the SDK is not yet implanted in the client, the client does not need to be involved in the test. That is, the first test case only includes the test for the basic function of the SDK, and does not include the part of the SDK based on the client usage.
Specifically, a test case of the SDK is preset, which is referred to as a first test case. The first test case may include input parameters of the SDK and a result that the SDK should output after the input parameters are input into the functional SDK, where the input parameters may include information such as specific parameter values, parameter formats, and parameter types, and the result that should be output may be referred to as a first expected result. When testing the SDK integrated before the client, the input parameters in the first test case may be input into the SDK, then the output result of the SDK is obtained, and the output result is further compared with the first expected result to obtain the first test result, that is, the first test result is a conclusion for representing whether the function of the SDK is normal after testing the function of the SDK not implanted in the client. When the first test result is that the output result is consistent with the first expected result, it indicates that the function of the SDK is normal, and step S102 may be further executed; when the first test result is that the output result is inconsistent with the first expected result, the function of the SDK is indicated to be abnormal, and the SDK can be returned to the developer to modify the SDK.
For example, if the SDK is an SDK of a login function, the input parameters included in the first test case may be a correct login account and a login password, and the first expected result may be the successfully logged-in web page 1. When the SDK is tested, the correct login account number and the login password in the first test case can be input into the SDK, then the SDK returns an output result based on the input parameters, if the output result is the webpage 1, the first test result is that the output result is consistent with the first expected result, and at this moment, the function of the part of the SDK is considered to be normal; otherwise, the first test result is that the output result is inconsistent with the first expected result, and the part of the SDK is considered to be not normally functional. At this time, the SDK that is not integrated into the client is tested, so the first test case does not include the test for calling the keyboard part from the SDK.
Further, the input parameters may be classified into forward input parameters (correct input parameters), reverse input parameters (wrong input parameters), and missing input parameters (only a part of input parameters). For example, for the login SDK, the forward input parameter may be a correct login account and a correct login password, the reverse input parameter may be an incorrect login account and/or an incorrect login password, and the missing input parameter may be only a login account or only a login password.
And S102, integrating the SDK to a client side to obtain an integrated SDK under the condition that the first test result represents that the SDK is normal in function.
In this embodiment, if the first test result is that the output result is consistent with the first expected result, it is characterized that the function of the SDK is normal, and the SDK may be integrated into the client, and step S103 is executed.
Step S103, testing the integrated SDK to obtain a second test result.
In this embodiment, since the SDKs with normal functions are already integrated into the client to form an integrated SDK, the integrated SDK may rely on the client to execute its own function, but in order to ensure normal use of the integrated SDK, the integrated SDK needs to be further tested by the client to obtain a second test result. The client can be installed on the terminal device, and the test server is connected with the terminal device so as to test the SDK integrated on the client.
Alternatively, step S103 may include: acquiring a second test case, wherein the second test case comprises a test rule and a second expected result corresponding to the test rule; executing the operation specified in the test rule on the client; obtaining a response result output by the client after the integrated SDK responds to the operation; comparing the response result with the second expected result to obtain a second test result; when the second test result is that the response result is consistent with the second expected result, the integrated SDK is characterized to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, characterizing that the integrated SDK is not functioning normally.
Specifically, a test case of the integrated SDK is preset and referred to as a second test case. The second test case includes a test rule and a correct result output by the integrated SDK after the integrated SDK is tested based on the test rule, where the test rule may include performing a pre-operation on the client, where the pre-operation may be used to trigger the integrated SDK to work, and the correct result may be referred to as a second expected result. When the integrated SDK is tested, the integrated SDK may be automatically executed on the client according to a pre-operation specified in the test rule, and then the integrated SDK on the client may have a corresponding response result by responding to the pre-operation (for example, logging in the SDK may call a system keyboard), and compare the response result with a second expected result to obtain a second test result, that is, the second test result is a conclusion for representing whether the integrated SDK function is normal after the function of the SDK (that is, the integrated SDK) that has been integrated into the client is tested depending on the client. When the second test result is that the response result is consistent with the second expected result, the integrated SDK is indicated to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, indicating that the integrated SDK does not function normally.
For example, with reference to the above example, the integrated SDK is an integrated SDK with login function, the pre-operation in the test rule included in the second test case may be to click a login account entry box or click a login password entry box, and the second expected result may be to call a system keyboard. When the integrated SDK is tested, the pre-operation can be executed on a login interface of the client, then the integrated SDK on the client responds to the pre-operation and returns a response result, if the response result is to call a system keyboard, the second test result is that the response result is consistent with the second expected result, and at this moment, the function of the part of the integrated SDK is considered to be normal; otherwise, the second test result is that the response result is inconsistent with the second expected result, and the integrated SDK is deemed to be not functioning properly. At this time, because the test is performed on the SDK integrated to the client (i.e., the integrated SDK), the second test case may not include the part in the first test case.
Alternatively, a start button for starting the test program may be provided on the client, and the test server may start the test program by recognizing and clicking the start button. For example, a reference button is set as a reference, and the position of the start button on the current screen is determined by acquiring the position of the reference button on the reference screen. Specifically, the current screen resolution of the terminal device where the client is located is obtained, the reference screen resolution and the position of the reference button at the reference screen resolution are obtained, the ratio of the current screen resolution to the reference screen resolution is calculated, and the position of the start button at the current screen resolution is determined according to the ratio and the position of the reference button at the reference screen resolution. Wherein the screen resolution includes a screen width and a screen height.
And step S104, determining whether the function of the integrated SDK is normal or not according to the second test result.
In this embodiment, if the second test result is that the response result is consistent with the second expected result, the function of the integrated SDK is characterized to be normal; if the second test result is that the response result is inconsistent with the second expected result, the integrated function is represented to be abnormal, and further the abnormal reason can be uploaded to a background server for improving the integrated SDK according to the abnormal reason.
It should be noted that, in the prior art, only the integrated SDK on one client can be tested at the same time, and in the case that a plurality of clients need to be tested, the scheme in the prior art may significantly increase the test flow and consume the test time. Based on the above, the invention provides a further improved scheme, which can realize the test of the integrated SDK on a plurality of clients simultaneously. Optionally, in step S102, integrating the SDK into the client, and the step of obtaining an integrated SDK may include: respectively integrating the SDK to each client in a plurality of clients to obtain a plurality of integrated SDKs; in step S103, the step of testing the integrated SDK to obtain a second test result may include: acquiring identification information corresponding to each client; determining a second test case corresponding to each identification information; and testing each integrated SDK according to the determined second test case corresponding to each identification information to obtain a second test result of each integrated SDK.
Each client can be installed on one terminal device, the test server can be simultaneously connected with a plurality of terminal devices so as to test the SDK installed on the clients of the plurality of terminal devices simultaneously, and each client corresponds to one second test case.
In this embodiment, a plurality of second test cases may be preset, where each second test case corresponds to one client, and specifically corresponds to the identification information of the client. The identification information of the client may be unique information of the client, such as an identification number preset for the client, or the identification information of the client may be identification information of a terminal device on which the client is installed, such as a device identifier of the terminal device on which the client is installed. When the integrated SDKs on each client are tested at the same time, the second test case of the client may be determined according to the identification information of each client, and then each integrated SDK is tested at the same time by combining the above method.
It should be noted that if the SDK itself is not normal, the SDK is integrated into the client, and the subsequent testing process is only idle. Therefore, before the SDK is integrated into the client, the function of the SDK is tested in advance, and under the condition that the test shows that the function of the SDK is normal, the SDK is integrated into the client to obtain the integrated SDK, and whether the function of the integrated SDK is normal is further tested. According to the invention, the SDK is subjected to double testing through two testing processes, and the second testing process is carried out only when the first testing process passes, so that the accuracy of the testing result can be effectively improved, invalid testing is avoided, the overall testing efficiency is improved, and the testing resources are saved. In addition, the invention can also test the SDK integrated on each client of a plurality of clients simultaneously, thereby further improving the testing efficiency and saving the human and material resources.
As shown in fig. 2, the SDK testing apparatus 200 may include a first testing module 201, an integrating module 202, a second testing module 203, and a determining module 204, wherein:
the first testing module 201 is configured to test the SDK to obtain a first testing result;
the integration module 202 is configured to integrate the SDK to a client to obtain an integrated SDK when the first test result indicates that the SDK is normal in function;
the second testing module 203 is configured to test the integrated SDK to obtain a second testing result;
a determining module 204, configured to determine whether the function of the integrated SDK is normal according to the second test result.
Optionally, the first test module is further configured to: acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters; inputting the input parameters into the SDK, and acquiring an output result output by the SDK; comparing the output result with the first expected result to obtain the first test result; when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
Optionally, the input parameters comprise at least one of forward input parameters, reverse input parameters and missing input parameters.
Optionally, the second testing module is further configured to: acquiring a second test case, wherein the second test case comprises a test rule and a second expected result corresponding to the test rule; executing the operation specified in the test rule on the client; obtaining a response result output by the client after the integrated SDK responds to the operation; comparing the response result with the second expected result to obtain a second test result; when the second test result is that the response result is consistent with the second expected result, the integrated SDK is characterized to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, characterizing that the integrated SDK is not functioning normally.
Optionally, the integration module is further configured to: respectively integrating the SDK to each client in a plurality of clients to obtain a plurality of integrated SDKs; correspondingly, the second testing module is further configured to: acquiring identification information corresponding to each client; determining a second test case corresponding to each identification information; and testing each integrated SDK according to the determined second test case corresponding to each identification information to obtain a second test result of each integrated SDK.
Optionally, the identification information includes a device identifier of a terminal device on which the client is installed.
Fig. 3 schematically shows a block diagram of a computer device suitable for implementing the SDK testing method according to an embodiment of the invention. In this embodiment, the computer device 300 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of a plurality of servers), and the like that execute programs. As shown in fig. 3, the computer device 300 of the present embodiment includes at least but is not limited to: a memory 301, a processor 302, a network interface 303, which may be communicatively coupled to each other via a system bus. It is noted that FIG. 3 only shows computer device 300 having components 301 and 303, but it is understood that not all of the shown components are required and that more or fewer components may be implemented instead.
In this embodiment, the memory 303 includes at least one type of computer-readable storage medium, which includes flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 301 may be an internal storage unit of the computer device 300, such as a hard disk or a memory of the computer device 300. In other embodiments, the memory 301 may also be an external storage device of the computer device 300, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 300. Of course, the memory 301 may also include both internal and external storage devices for the computer device 300. In the present embodiment, the memory 301 is generally used for storing an operating system and various types of application software installed in the computer device 300, such as program codes of an SDK testing method, and the like, where the SDK testing method includes: testing the SDK to obtain a first test result; under the condition that the first test result represents that the SDK is normal in function, integrating the SDK to a client to obtain an integrated SDK; testing the integrated SDK to obtain a second test result; and determining whether the function of the integrated SDK is normal or not according to the second test result. In addition, the memory 301 may also be used to temporarily store various types of data that have been output or are to be output.
In this embodiment, the SDK testing method stored in the memory 301 may be further divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 302) to complete the present invention.
The network interface 303 may comprise a wireless network interface or a wired network interface, and the network interface 303 is typically used to establish communication links between the computer device 300 and other computer devices. For example, the network interface 303 is used to connect the computer device 300 to an external terminal via a network, establish a data transmission channel and a communication link between the computer device 300 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth (Bluetooth), Wi-Fi, etc.
The present embodiment also provides a computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor, implements the steps of the SDK test method, the SDK test method including: testing the SDK to obtain a first test result; under the condition that the first test result represents that the SDK is normal in function, integrating the SDK to a client to obtain an integrated SDK; testing the integrated SDK to obtain a second test result; and determining whether the function of the integrated SDK is normal or not according to the second test result.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
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.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An SDK testing method, comprising:
testing the SDK to obtain a first test result;
under the condition that the first test result represents that the SDK is normal in function, integrating the SDK to a client to obtain an integrated SDK;
testing the integrated SDK to obtain a second test result;
and determining whether the function of the integrated SDK is normal or not according to the second test result.
2. The method of claim 1, wherein testing the SDK to obtain the first test result comprises:
acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters;
inputting the input parameters into the SDK, and acquiring an output result output by the SDK;
comparing the output result with the first expected result to obtain the first test result;
when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
3. The method of claim 2, wherein the input parameters comprise at least one of forward input parameters, reverse input parameters, and missing input parameters.
4. The method of claim 1, wherein testing the integrated SDK to obtain a second test result comprises:
acquiring a second test case, wherein the second test case comprises a test rule and a second expected result corresponding to the test rule;
executing the operation specified in the test rule on the client;
obtaining a response result output by the client after the integrated SDK responds to the operation;
comparing the response result with the second expected result to obtain a second test result;
when the second test result is that the response result is consistent with the second expected result, the integrated SDK is characterized to be normal in function; and when the second test result is that the response result is inconsistent with the second expected result, characterizing that the integrated SDK is not functioning normally.
5. The method of claim 1,
integrating the SDK to the client to obtain an integrated SDK, wherein the step of obtaining the integrated SDK comprises the following steps: respectively integrating the SDK to each client in a plurality of clients to obtain a plurality of integrated SDKs;
correspondingly, the step of testing the integrated SDK to obtain a second test result comprises the following steps: acquiring identification information corresponding to each client; determining a second test case corresponding to each identification information; and testing each integrated SDK according to the determined second test case corresponding to each identification information to obtain a second test result of each integrated SDK.
6. The method of claim 5, wherein the identification information comprises a device identification of a terminal device on which the client is installed.
7. An SDK testing apparatus, comprising:
the first testing module is used for testing the SDK to obtain a first testing result;
the integration module is used for integrating the SDK to a client side to obtain an integrated SDK under the condition that the first test result represents that the SDK is normal in function;
the second testing module is used for testing the integrated SDK to obtain a second testing result;
and the determining module is used for determining whether the function of the integrated SDK is normal or not according to the second test result.
8. The apparatus of claim 7, wherein the first testing module is further configured to:
acquiring a first test case, wherein the first test case comprises input parameters and a first expected result corresponding to the input parameters;
inputting the input parameters into the SDK, and acquiring an output result output by the SDK;
comparing the output result with the first expected result to obtain the first test result;
when the first test result is that the output result is consistent with the first expected result, the SDK is characterized to be normal in function; and when the first test result is that the output result is inconsistent with the first expected result, the SDK is characterized to be abnormally functional.
9. A computer device, the computer device comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010360273.2A CN111563038A (en) | 2020-04-30 | 2020-04-30 | SDK test method, device, computer equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010360273.2A CN111563038A (en) | 2020-04-30 | 2020-04-30 | SDK test method, device, computer equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111563038A true CN111563038A (en) | 2020-08-21 |
Family
ID=72074530
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010360273.2A Pending CN111563038A (en) | 2020-04-30 | 2020-04-30 | SDK test method, device, computer equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111563038A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116860597A (en) * | 2023-05-11 | 2023-10-10 | 钉钉(中国)信息技术有限公司 | Application program detection method, computing device and computer storage medium |
-
2020
- 2020-04-30 CN CN202010360273.2A patent/CN111563038A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116860597A (en) * | 2023-05-11 | 2023-10-10 | 钉钉(中国)信息技术有限公司 | Application program detection method, computing device and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107896162B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| CN109901881B (en) | Plug-in loading method and device of application program, computer equipment and storage medium | |
| CN110704521A (en) | Interface data access method and system | |
| CN110308880B (en) | Log printing method, system, computer device and computer readable storage medium | |
| CN110647471B (en) | Interface test case generation method, electronic device and storage medium | |
| CN107480117B (en) | Recovery method and device for automatic page table single data | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN108804399B (en) | Form verification method and device | |
| CN110888709A (en) | Intelligent operation method and device of monitoring screen, computer equipment and storage medium | |
| CN108255735B (en) | Associated environment testing method, electronic device and computer readable storage medium | |
| CN105404574B (en) | Smart card and mobile terminal consistency test method and device | |
| CN111563038A (en) | SDK test method, device, computer equipment and computer readable storage medium | |
| CN112818270B (en) | Data cross-domain transfer method and device and computer equipment | |
| CN111338644A (en) | Task script deployment method and system | |
| CN112699027A (en) | Interface testing method, device, equipment and readable storage medium | |
| CN111752789B (en) | Pressure testing method, computer device and computer readable storage medium | |
| CN116450165A (en) | Method, system, terminal and storage medium for quickly building environment and deploying program | |
| CN111159226A (en) | Index query method and system | |
| CN113419814B (en) | Virtual machine creating method, device, equipment and storage medium in cloud platform | |
| CN113722225A (en) | Page testing method and device, computer equipment and storage medium | |
| CN113110982A (en) | Data access layer verification method and device, storage medium and electronic device | |
| CN112559155A (en) | Batch job processing method, system, computer device and readable storage medium | |
| CN111274128A (en) | Test method, test device, computer equipment and computer readable storage medium | |
| CN111381849A (en) | Software updating method and device and electronic equipment | |
| CN112486556B (en) | Method, system, terminal and storage medium for server to be compatible with BMC |
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 |