CN111651366A - SDK test method, device, equipment and storage medium - Google Patents

SDK test method, device, equipment and storage medium Download PDF

Info

Publication number
CN111651366A
CN111651366A CN202010641547.5A CN202010641547A CN111651366A CN 111651366 A CN111651366 A CN 111651366A CN 202010641547 A CN202010641547 A CN 202010641547A CN 111651366 A CN111651366 A CN 111651366A
Authority
CN
China
Prior art keywords
sdk
test
target
test case
running
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010641547.5A
Other languages
Chinese (zh)
Other versions
CN111651366B (en
Inventor
蒋燚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202010641547.5A priority Critical patent/CN111651366B/en
Publication of CN111651366A publication Critical patent/CN111651366A/en
Application granted granted Critical
Publication of CN111651366B publication Critical patent/CN111651366B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • 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/3692—Test management for test results analysis
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

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

Abstract

The embodiment of the application discloses an SDK testing method, device, equipment and storage medium, and belongs to the technical field of SDK testing. The method comprises the following steps: the method comprises the steps of obtaining SDK test case codes, wherein the SDK test case codes are generated according to interface test cases corresponding to target Application Program Interfaces (APIs), wherein different APIs in the SDK correspond to different interface test cases, and the target APIs are APIs called by the target application programs in the running process; responding to the received test operation of the SDK, automatically running SDK test case codes to obtain a first running result, wherein the SDK test case codes call a target API in the SDK in the running process; and generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API. The automatic test of the SDK can be realized, the test flow is simplified, and the test efficiency of the SDK is further improved.

Description

SDK test method, device, equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of SDK testing, in particular to an SDK testing method, device, equipment and storage medium.
Background
A Software Development Kit (SDK) generally refers to a set of Development tools used by a Software engineer to build application Software for a specific Software package, a Software framework, a hardware platform, an operating system, and the like, and developers generally develop application programs using the SDK to quickly build the application Software. In order to detect whether the SDK meets the requirements of the application program established by the developer, an SDK test is required to analyze the quality of the SDK, thereby ensuring the quality and efficiency of the application program development.
In the related art, in the process of testing the SDK, a user is required to manually execute interface operations in an Application program (APP) interface, for example, when logging in an account and a password, the user is required to manually input the account, the password, and other related data in the login interface, so as to test a function of an Application Programming Interface (API) corresponding to a target Application program in the SDK.
Obviously, the manual testing mode in the related art is adopted, and the testing efficiency is low due to the fact that the number of the APIs in the SDK is large.
Disclosure of Invention
The embodiment of the application provides an SDK test method, device, equipment and storage medium. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides an SDK testing method, where the method includes:
the method comprises the steps of obtaining SDK test case codes, wherein the SDK test case codes are generated according to interface test cases corresponding to target Application Program Interfaces (APIs), different APIs in the SDK correspond to different interface test cases, and the target APIs are called APIs in the running process of a target application program;
responding to the received test operation of the SDK, automatically running the SDK test case code to obtain a first running result, wherein the SDK test case code calls the target API in the SDK in the running process;
and generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API.
On the other hand, an embodiment of the present application provides an SDK testing apparatus, including:
the system comprises a first acquisition module, a first test module and a second test module, wherein the first acquisition module is used for acquiring SDK test case codes, and the SDK test case codes are generated according to interface test cases corresponding to target Application Program Interfaces (APIs), different APIs in the SDK correspond to different interface test cases, and the target APIs are the APIs called by the target application programs in the running process;
the operation module is used for responding to the received test operation of the SDK and automatically operating the SDK test case code to obtain a first operation result, wherein the SDK test case code calls the target API in the SDK in the operation process;
and the generating module is used for generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API.
In another aspect, embodiments of the present application provide a computer device, which includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the SDK testing method according to the above aspect.
In another aspect, embodiments of the present application provide a computer-readable storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which is loaded and executed by a processor to implement the SDK testing method according to the above aspect.
In another aspect, an embodiment of the present application further provides a computer program product, where the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the SDK testing method according to the above aspect.
The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:
the interface test case codes corresponding to the APIs in the SDK are coded to obtain the SDK test case codes, and the interface test cases are realized according to the service functions corresponding to the APIs, so that when the computer equipment automatically runs the SDK test case codes, the process that the application program calls the target APIs can be simulated, and corresponding running data are obtained and fed back to testing personnel. In addition, because the SDK test in the embodiment can be refined to the interface logic layer, if the test result is not in accordance with the expectation, the reason of the operation error can be accurately positioned.
Drawings
FIG. 1 illustrates an architecture diagram of a test system shown in an exemplary embodiment of the present application;
FIG. 2 illustrates a flow chart of a method for testing an SDK according to an exemplary embodiment of the present application;
FIG. 3 illustrates a design framework diagram of an interface test case shown in an exemplary embodiment of the present application;
FIG. 4 illustrates a flow chart of a method of testing an SDK as illustrated in another exemplary embodiment of the present application;
FIG. 5 illustrates a flow chart of a method of testing an SDK as illustrated in another exemplary embodiment of the present application;
FIG. 6 illustrates a flow chart of a method of testing an SDK as illustrated in another exemplary embodiment of the present application;
FIG. 7 illustrates a flow chart of a method of testing an SDK as illustrated in another exemplary embodiment of the present application;
FIG. 8 illustrates a flow chart of a method of testing an SDK as illustrated in another exemplary embodiment of the present application;
FIG. 9 is a diagram illustrating an SDK test performed by a test terminal according to an exemplary embodiment of the present application;
fig. 10 is a block diagram illustrating an SDK testing apparatus according to an exemplary embodiment of the present application;
fig. 11 shows a block diagram of a computer device provided in an exemplary embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Reference herein to "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
Referring to FIG. 1, an architecture diagram of a test system including a computer device 101 and a test terminal 102 is shown in accordance with an exemplary embodiment of the present application.
The computer apparatus 101 is an apparatus provided with an SDK development environment or an SDK test environment. The computer device 101 may be a desktop, a all-in-one machine, a notebook computer, a tablet computer, and the like, which is not limited in this embodiment of the application. In this embodiment, the computer device 101 is provided with a development environment of SDK test code, a running environment, and a development environment of APP. The development environment provided by the computer device 101 is related to the operating system of the test terminal 102, for example, if the operating system of the terminal 102 is an android system, the corresponding development and test environments are both android environments. Optionally, if the SDK test needs to be performed on a specific processor platform, the APP needs to be developed in the computer device 101, an Application Package (APK) corresponding to the APP is obtained, and both the APP and the SDK test case code are sent to the test terminal 102.
The computer device 101 is connected to the test terminal 102 directly or indirectly by wired or wireless communication.
The test terminal 102 is a device provided with an SDK test environment. It can be smart mobile phone, smart watch, AR glasses, panel computer etc. this embodiment is not limited to this. In this embodiment, the test terminal 102 may install an application program according to the received APK, and automatically run the SDK test case code, so as to feed back, to the computer device 101, running data of the target application program when the target API is called on the target processor platform.
It should be noted that the test system shown in the embodiment of the present application may also only include the computer device 101, without the terminal 102, and by developing the SDK test case codes in the computer device 101 and automatically running the SDK test case codes, a process of calling each target API by the APP is simulated, so as to obtain running data when the target API is called by the application program, and feed the running data back to the tester.
In a possible application scenario, before performing the SDK test, steps such as SDK test case code development and APP development need to be performed, so that the computer device needs to configure corresponding development environments and test environments, and since different operating systems correspond to different development environments and test environments, the development environment and the test environment shown in the embodiment of the present application are exemplarily described below by taking only an operating system of a test terminal as an android system as an example.
(1) Android development environment (Android Studio)
The Android Studio is an Android integrated development tool, based on IntelliJ IDEA, the Android development tool is integrated for development and debugging, and the SDK is integrated inside, so that convenience is brought to development of testers.
(2) Android test frame (Android JUnit)
The Android JUnit is a developed resource framework which is used for compiling and running tests and is a white box test framework, namely, developers perform functional tests on the developed method. In this embodiment, a tester develops and runs SDK test case codes based on the android unit.
(3) APP development framework
The APP development framework used in the embodiment of the application uses Java as a programming language to realize APP code development, so that the APK corresponding to the APP is obtained for subsequent SDK testing.
It should be noted that, the above embodiment is only described by taking the android system as an example, and if the operating system corresponding to the test terminal is an IOS system, the corresponding test framework and the development framework both adopt a development framework corresponding to the IOS system.
Referring to fig. 2, a flowchart of an SDK testing method according to an exemplary embodiment of the present application is shown, where the present application is illustrated by applying the method to the computer device shown in fig. 1, and the method includes:
step 201, obtaining an SDK test case code, where the SDK test case code is generated according to an interface test case corresponding to a target application program interface API, and the target API is an API called by the target application program in an operation process.
The interface test cases indicate that testers write according to the service functions of each interface, or write according to an SDK configuration file provided by an application program developer, and if the SDK configuration file is defined for the functions corresponding to each interface in the SDK, different APIs in the SDK correspond to different interface test cases.
In a possible implementation manner, a tester may write a corresponding interface test case from the aspects of business logic, interface logic, parameter logic, and the like, and write an SDK test case code corresponding to the interface test case in a corresponding case code framework.
Wherein, the service logic indicates the logic corresponding to the interface function; for example, if the application needs to implement a login account function, the corresponding interface needs to implement a function of receiving the login account and the password input by the interface and sending the login account and the password to the server.
Optionally, in order to perform an interface test more comprehensively, when the interface test case is compiled, in addition to the service logic in the normal scene corresponding to the API, the service logic in the abnormal scene needs to be compiled, so as to accurately locate the reason for the abnormal function of the interface according to the corresponding interface test result.
The interface logic indicates that an application program needs to call at least two APIs when realizing a target service function, and the calling sequence corresponding to the at least two APIs is in the calling process; for example, in the process of implementing the service function a, the application program needs to call the interface 1, the interface 2, and the interface 3, but in the implementation process, the corresponding call sequence when calling the three interfaces is interface 1-interface 3-interface 2.
Optionally, similar to the service logic, except that the interface logic in the normal sequence needs to be written, the interface logic in the abnormal sequence needs to be written, for example, the normal sequence is interface 1-interface 3-interface 2, and the abnormal sequence may be: when the test result indicates that the interface logic is abnormal, the interface 1-interface 2-interface 3, the interface 2-interface 3-interface 1, the interface 2-interface 1-interface 3 and the like can accurately position which interface logic is abnormal, and the analysis of the test result by a tester is facilitated.
The parameter logic indicates that, in the process of calling the API, the API transmits (receives or sends) parameter characteristics corresponding to the parameters, such as parameter value size, parameter type, parameter range, parameter order, parameter number, and the like. For example, the data type transmitted by the API is binary data.
Optionally, when the interface test case is compiled, the parameter logic corresponding to the abnormal parameter feature also needs to be compiled, so as to accurately locate the reason of the transmission parameter error.
In an illustrative example, as shown in fig. 3, a design framework diagram of an interface test case shown in an illustrative embodiment of the present application is shown. As shown in fig. 3, the interface test case may be compiled based on business logic, interface logic, parameter logic, and other aspects in the compiling process, where the business logic may include business logic in a normal scenario and business logic in an abnormal scenario; the interface logic may include interface logic in a normal order and service logic in an abnormal scenario; the parameter logic may include: the method comprises the steps of transmitting null parameters, selecting required parameters, combining selectable parameters, parameter sequence, parameter number, parameter type, parameter data size, parameter range, special characters and the like.
In a possible implementation manner, after a tester writes an interface test case according to the interface test case design, the tester can correspondingly develop the SDK test case codes according to the interface test case and based on a case code development framework.
The application case code development framework is related to the operating system corresponding to the SDK, for example, if the operating system is an Android system, the corresponding application case code development framework is an Android unit, and if the operating system is an IOS system, the corresponding application case code development framework is the application case code development framework corresponding to the IOS system.
Step 202, in response to receiving the test operation on the SDK, automatically running the SDK test case code to obtain a first running result.
In a possible implementation manner, after a tester writes a corresponding SDK test case code, the SDK test case code can be run in the computer device, and in the running process of the SDK test case code, the computer device simulates a process in which an application program calls a target API in the SDK, and returns a corresponding running result.
Optionally, a test control or an operation control is provided in an SDK test interface in the computer device, and when a tester writes a corresponding SDK test case code, the tester clicks the test control (operation control), and the SDK test case code can be automatically operated.
Step 203, generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API.
In order to facilitate analysis of the running result of the API, for example, whether the target API can implement an expected function, or occupation of system resources when the target API is called, the computer device generates a corresponding test report according to the returned running result, so that a tester can conveniently confirm whether the SDK can achieve an expected development quality.
In the embodiment of the application, the interface test case codes corresponding to the APIs in the SDK are coded to obtain the SDK test case codes, and the interface test cases are realized according to the service functions corresponding to the APIs, so that when the computer equipment automatically runs the SDK test case codes, the process that an application program calls a target API can be simulated, and corresponding running data are obtained and fed back to a tester. Because the SDK test case codes can automatically run and the test cases of the API are all written in the test case codes, the test of each interface function in the SDK can be realized without interface operation in an application program interface manually by a user, the test flow is simplified, the test efficiency of the SDK is further improved, and in addition, the SDK test in the embodiment can be refined to an interface logic layer, so that the reason of running errors can be accurately positioned if the test result is not in accordance with expectation.
In order to more accurately test whether the API service function is realized, in one possible implementation mode, two test modes are provided, wherein one test mode is a single interface test mode, namely, only an SDK test case code corresponding to a single interface is operated each time, and the process of calling the single interface is correspondingly simulated; the method is a process for testing a plurality of interfaces, namely, SDK test case codes corresponding to the plurality of interfaces can be simultaneously operated each time of operation, and the plurality of interfaces are correspondingly simulated and simultaneously called or are called in sequence.
Referring to fig. 4, a flowchart of an SDK testing method according to another exemplary embodiment of the present application is shown, where the present application is illustrated by applying the method to the computer device shown in fig. 1, and the method includes: the method comprises the following steps:
step 401, obtaining an SDK test case code, where the SDK test case code is generated according to an interface test case corresponding to a target application program interface API, and the target API is an API called by the target application program in the running process.
Step 201 may be referred to in the implementation manner of this step, and this embodiment is not described herein again.
Step 402, in response to receiving the first test operation on the SDK, automatically running the SDK test case code corresponding to the single target API to obtain a first running result.
Because the SDK includes a plurality of interfaces, and the service functions corresponding to each interface are different, in order to more accurately obtain the running data corresponding to each interface when being called, so as to analyze the test condition corresponding to each interface, in a possible implementation, a selection of multiple test modes is provided, for example, a single interface test mode and multiple interface test modes.
For the single interface test mode, because the test cases of each interface are written when the SDK test case codes are written, the single test can be performed for a single interface when the SDK test is performed, that is, only the SDK test case codes corresponding to the single interface are operated every time, so that the operation result corresponding to the single interface is returned.
Step 403, in response to receiving the second test operation on the SDK, automatically running the SDK test case codes corresponding to the at least two target APIs to obtain a first running result.
Because the application program may need to call multiple interfaces simultaneously when implementing a certain service function, during the SDK test, if it is necessary to test whether the interfaces implement the corresponding service function, multiple interfaces need to be called simultaneously, or multiple interfaces are called in sequence, so that multiple interface test modes are provided, that is, SDK interface test case codes corresponding to multiple interfaces need to be run simultaneously each time, so as to return the running results corresponding to multiple interfaces.
Optionally, how to select a plurality of interfaces operating simultaneously may be to randomly select at least two interfaces for interface testing, for example, to test three interfaces simultaneously, or to test more than three interfaces simultaneously; or, an interface test may be selected according to a function combination, for example, if the interface combination can realize a certain service function, the interface combination is selected for testing. The examples of the present application are not intended to be limiting.
Step 404, generating a first test report according to the first operation result, wherein the first test report includes operation data when the target application program calls the target API.
In a possible implementation manner, for a single interface test mode, the obtained operation result is the operation data corresponding to the application program calling a single target API, and the operation data is generated into a test report and fed back to the tester.
In another possible implementation manner, for a plurality of interface test modes, the obtained operation result is the operation data corresponding to the application program calling a plurality of target APIs, and the operation data is generated into a test report and fed back to the tester.
In the embodiment, a single interface test mode and a plurality of interface test modes are provided, a tester can select any interface test mode according to self requirements, and if the single interface test mode is selected, only the SDK test case code corresponding to a single target API is operated in a single test process; and if a plurality of interface test modes are selected, correspondingly, the SDK test case codes corresponding to a plurality of target APIs are simultaneously operated in a single test process.
In a possible application scenario, testing the SDK through a single interface test mode, and obtaining the operation data to determine whether the parameter characteristics corresponding to the target API are in accordance with expectations or not; and if the SDK is tested through a plurality of interface test modes, whether the calling sequence of the plurality of APIs is in accordance with expectation can be obtained.
In an illustrative example, step 402 and step 403 may be replaced with step 501 and step 502 on the basis of fig. 4, as shown in fig. 5.
Step 501, in response to receiving a first test operation on the SDK, automatically verifying a parameter logic corresponding to a target API by running the SDK test case code corresponding to a single target API, so as to obtain a first running result.
Wherein the parameter logic includes at least one of a parameter type, a parameter range, a parameter order, and a parameter value. Optionally, the parameter logic may further include: the parameters include optional parameters, required parameters, and null parameters, which are not limited in this embodiment.
Since the parameter logic mainly relates to the parameter characteristics transmitted by each interface when being called, and is basically independent of other interfaces, each target API can be tested through a single interface test mode, so as to judge whether the transmission parameters of the interface are accurate (or meet expectations) according to the operation result.
In a possible implementation manner, a tester may select a target API in a test interface and click a test control, and then the corresponding computer device receives a first test operation on the SDK, runs an SDK test case code corresponding to the target API, so as to verify a parameter logic corresponding to the target API, thereby obtaining a running result corresponding to the target API.
Optionally, in another possible implementation, when the tester selects the single interface test mode, the corresponding computer device receives the first test operation on the SDK, and tests each API in the SDK according to a preset sequence (or a default sequence), that is, automatically runs the SDK test case code corresponding to the first API, and returns a running result corresponding to the first API; automatically running the SDK test case code corresponding to the second API, and returning a running result corresponding to the second API; and automatically running the SDK test case codes corresponding to the third API, and returning a running result corresponding to the third API until all the SDK test case codes are run, namely, completing the test of each API in the SDK.
Step 502, in response to receiving the second test operation on the SDK, automatically verifying an interface logic between the at least two target APIs by running the SDK test case codes corresponding to the at least two target APIs to obtain a first running result, where the interface logic indicates a calling sequence between the at least two target APIs.
Because the interface logic generally relates to the interface calling sequence corresponding to at least two interfaces, when the SDK test is performed, if the interface logic among a plurality of interfaces needs to be tested, each target API can be tested by using a plurality of interface test modes.
In a possible implementation manner, a tester may select at least two interfaces that need to be verified in each test according to its own requirements in a test interface, and correspondingly, the computer device may automatically run SDK interface test codes corresponding to the at least two target APIs, and feed back corresponding running results.
In this embodiment, the parameter logic of each interface is verified through a single interface test mode, so as to test whether the transmission parameter corresponding to each interface is in accordance with the expectation; and checking the interface logic corresponding to each interface through a plurality of interface test modes so as to test whether the calling sequence among the related interfaces is in accordance with expectation.
In a possible implementation manner, a tester generally analyzes the performance of each API in the SDK from both the functional and performance aspects, and therefore, when the test case code of the SDK interface is run, the fed-back running data may also include at least one of functional data and performance data.
In an illustrative example, step 202 may be replaced with step 601 or step 602 on the basis of fig. 2, as shown in fig. 6.
Step 601, responding to the received test operation of the SDK, automatically running an SDK test case code, and obtaining an implementation situation of a target service function when a target API is called, where the target service function is an interface function corresponding to the target API.
The function implementation condition indicates whether the target API can implement its corresponding service function, for example, whether data transmission can be implemented, whether the transmitted data is accurate (i.e., consistent with an expectation), and the like.
In a possible implementation manner, a tester writes an interface function corresponding to a target API into an SDK test case code corresponding to the interface, and when the test case code runs, simulates an application program to call the target API, and monitors a service implementation situation corresponding to the calling of the target API in real time, for example, taking transmission data as an example, whether a data transmission function is implemented, whether transmission data is consistent with expectations, and the like, if it is monitored that the target API can implement the interface function, a running result returned is that the target API passes a function test; otherwise, the returned operation result is that the target API fails the functional test.
Step 602, in response to receiving the test operation on the SDK, automatically running an SDK test case code, and obtaining a use condition of a system resource when the target API is called.
The system resources may include Central Processing Unit (CPU) resources, Graphics Processing Unit (GPU) resources, memory resources, network resources, disk resources, and the like, which is not limited in this embodiment.
Because when testing each interface in the SDK, there are requirements not only for the function of the interface, but also for the performance of the interface, and if the interface occupies more system resources during the invocation process, it will obviously affect the operation performance of the interface under the condition of insufficient system resources, thereby affecting the operation performance of the application program.
In an illustrative example, when the target API is called, the corresponding performance data may be: the CPU resource occupancy rate is 12%, and the memory resource occupancy rate is 0.7 GB.
Optionally, in the running process of the application program, there may be a case of simultaneously calling a single interface, or a case of simultaneously calling multiple interfaces, or when the same service function is implemented, it is necessary to sequentially call multiple target APIs, and for the above three cases, the use cases of the system resources when the interfaces are called are obviously different, so in order to more comprehensively simulate the case of calling the interfaces when the application program runs, in another possible implementation manner, the interface performance data is tested in a single interface test mode and multiple interface test modes, respectively.
When the interface test case corresponding to the API is written, the service logic and the parameter logic in the API are defined, so that the SDK test case code written according to the interface test case can relate to each interface logic layer of the API, and the occupation conditions of different resource layers in the interface on system resources can be monitored when the SDK interface test case code is operated.
It should be noted that, when the SDK test is performed, only the function of each target API in the SDK may be selected for testing, and corresponding functional data is fed back; or only selecting the performance of each target API in the SDK to be tested, and feeding back the corresponding performance data; and simultaneously testing the function and the performance, and correspondingly feeding back the function data and the performance data.
In the embodiment, in the SDK test process, whether the target API meets the expected development purpose is measured from two aspects of function and performance, that is, when the SDK test case code is run, whether the target API can realize the corresponding target service function is obtained by obtaining the implementation condition of the target service function when the target API is called; the performance data of the target API is obtained by obtaining the service condition of the system resource when the target API is called, so that the test of the target API in the SDK is realized.
In a possible application scenario, because the interface test case is converted into the SDK test case code in this embodiment, in a possible implementation manner, if the test case of the target API needs to be added or deleted or modified subsequently, only part of the SDK test code corresponding to the target API needs to be added or deleted or modified, and it is not necessary to rewrite all the interface test cases or test case codes corresponding to the target API.
In an exemplary example, on the basis of fig. 2, as shown in fig. 7, a flowchart of an SDK testing method shown in another exemplary embodiment of the present application is shown, and this embodiment is illustrated by applying the method to the computer device shown in fig. 1, where the method includes:
step 701, receiving the add/delete operation of the test case of the target API.
Because the SDK test case codes are written according to the interface test cases corresponding to the target APIs, if a subsequent tester needs to modify the test case corresponding to the target API, only partial modification needs to be carried out on the SDK test case codes corresponding to the target API, and the SDK test case codes corresponding to other APIs do not need to be concerned. For example, if a test case of the target API needs to be added, the tester only needs to write a corresponding SDK test case code according to the newly added test case, and store the SDK test case code in association with the original SDK test case code.
In a possible implementation manner, on the basis of the original SDK test case code corresponding to the target API, a tester develops an SDK test case code corresponding to a newly added test case, or deletes an SDK test case code corresponding to a certain test case, or modifies an SDK test case code corresponding to a certain test case, and then, correspondingly, the computer device receives a test case add/delete operation on the target API.
And 702, modifying the SDK test case code corresponding to the target API according to the test case adding and deleting operation.
In a possible implementation manner, when the computer device receives the add/delete operation of the test case, the SDK test case code corresponding to the target API is modified correspondingly, for example, if a test case needs to be added newly on the original test case, the input newly added SDK test case code is correspondingly added to the original SDK test case code; if the test case needs to be deleted, deleting the SDK test case code corresponding to the test case correspondingly; and if the test case needs to be modified, storing the modified SDK test case code.
It should be noted that if an interface needs to be added or deleted, only the SDK test case code corresponding to the added API needs to be written or deleted, and all SDK test case codes do not need to be modified, so that the development cost of the SDK test case codes can be obviously reduced.
Step 703, obtaining an SDK test case code, where the SDK test case code is generated according to an interface test case corresponding to a target application program interface API, and the target API is an API called by the target application program in the running process.
Step 704, in response to receiving the test operation on the SDK, automatically running the SDK test case code to obtain a first running result.
Step 705, generating a first test report according to the first operation result, where the first test report includes operation data when the target application program calls the target API.
The embodiments of step 703 to step 705 may refer to the above embodiments, which are not described herein.
In the embodiment, because the test case codes of the SDK are written aiming at the single interface test case, if the test case corresponding to the target API needs to be modified, only the test case codes corresponding to the target API need to be modified; if the API needs to be added or deleted, only the SDK test case code corresponding to the added API needs to be developed or the SDK test case code corresponding to the API needs to be deleted, and all the SDK test case codes do not need to be modified, so that the reusability of the SDK test case codes can be improved, the development cost of the SDK test case codes can be reduced, and the development efficiency of the SDK test case codes can be improved.
In order to better determine the operation performance of the application program on different processor platforms, in a possible implementation manner, during the SDK testing process, a computer device needs to be connected to a testing terminal, and an SDK test case code is run in the testing terminal, so as to obtain the corresponding operation data of the application program on different processor platforms.
Referring to fig. 8, a flowchart of an SDK testing method according to another exemplary embodiment of the present application is shown, where the present embodiment exemplifies that the method is applied to the testing system shown in fig. 1, and the method includes:
step 801, a computer device obtains an SDK test case code, where the SDK test case code is generated according to an interface test case corresponding to a target application program interface API, and the target API is an API called by a target application program in an operation process.
The implementation manner of this step may refer to the above embodiments, which are not described herein.
In step 802, a computer device obtains an APK, which is an installation data packet of a target application.
In a possible implementation manner, if an SDK test needs to be performed in a test terminal and the application needs to be run in the test terminal, a corresponding application needs to be developed according to an APP development framework, an application development code is implemented, and an installation data package corresponding to the application is obtained, so that a corresponding APP is installed in the test terminal.
The APP development framework that is adopted is determined by the operating system that the terminal corresponds, namely if the terminal is an android operating system, the corresponding APP development framework also adopts the android development framework, and if the terminal is an IOS operating system, the corresponding APP development framework also should adopt the IOS development framework.
And step 803, the computer equipment sends the APK and SDK test case codes to the test terminal.
In one possible implementation, the computer device sends the developed APK and SDK test case codes to the test terminal through the data line (connecting the computer device and the test terminal) so that the test terminal runs the SDK test case codes.
And step 804, the test terminal automatically runs the SDK test case code under the scene of installing the target application program to obtain a second running result.
In a possible implementation manner, the test terminal receives the APK and the SDK test case code sent by the computer device through the data line, installs the target application program according to the APK, and automatically runs the SDK test case code when receiving the test operation on the SDK, so as to obtain a corresponding running result when the target application program calls the target API.
Optionally, the test terminal is connected to the computer device through a data line, so that the corresponding operation result can be directly fed back to the computer device and fed back to the tester by the computer device.
Step 805, the test terminal generates a second test report according to the second operation result, where the second test report includes operation data of the target application program when the target application program calls the target API on the target processor platform, and the target processor platform is a processor platform corresponding to the test terminal.
In a possible implementation manner, in the process of running the SDK test case code, the test terminal monitors the running data corresponding to the function and performance of the target application program when the target application program calls each target API on the target processor platform, and generates a test report according to the result and feeds the test report back to the tester.
In an exemplary example, as shown in fig. 9, a schematic diagram of a test terminal performing an SDK test according to an exemplary embodiment of the present application is shown. Taking a computer device as a Personal Computer (PC) for explanation, when a tester completes development of APK and SDK test case codes at the PC terminal 901, the tester can send the APK and SDK test case codes to the test terminal 902, and the test terminal 902 installs a target application program according to the APK and automatically runs the SDK test case codes, so that an obtained running result is fed back to the PC terminal 901.
At step 806, the test terminal sends the second test report to the computer device.
In one possible implementation, the test terminal may send the generated test report to the computer device, so that the tester may view and analyze the function or performance data of each target API to determine the development quality of the SDK.
Optionally, the computer device may directly monitor the calling condition of the application program to each API, that is, the computer device may directly obtain the operation result of the SDK test case code, generate a corresponding test report according to the operation result, and feed the test report back to the tester, without generating the test report by the test terminal.
In this embodiment, the computer device and the test terminal are connected by a data line, and the computer device sends the developed SDK test case code and the APK to the test terminal, so that the test terminal can perform an SDK test on a target processor platform on the basis of installing a target application program, so as to obtain running data of the SDK on different processor platforms, and analyze the development quality of the SDK according to the running data.
Referring to fig. 10, a block diagram of an SDK testing apparatus according to an exemplary embodiment of the present application is shown. The apparatus may be implemented as all or part of a computer device in software, hardware, or a combination of both. The device includes:
the first obtaining module 1001 is configured to obtain an SDK test case code, where the SDK test case code is generated according to an interface test case corresponding to a target application program interface API, where different APIs in the SDK correspond to different interface test cases, and the target API is an API called by the target application program in an operation process;
the running module 1002 is configured to, in response to receiving a test operation on the SDK, automatically run the SDK test case code to obtain a first running result, where the SDK test case code calls the target API in the SDK in a running process;
a generating module 1003, configured to generate a first test report according to the first operation result, where the first test report includes operation data when the target application program calls the target API.
Optionally, the running module 1002 includes:
the first running unit is used for responding to the received first test operation on the SDK and automatically running the SDK test case code corresponding to the single target API to obtain a first running result;
and the second running unit is used for responding to the received second test operation on the SDK and automatically running the SDK test case codes corresponding to at least two target APIs to obtain a first running result.
Optionally, the first operation unit is further configured to:
and automatically checking parameter logic corresponding to the target API by operating the SDK test case code corresponding to the single target API to obtain the first operation result, wherein the parameter logic comprises at least one of parameter type, parameter range, parameter sequence and parameter value.
Optionally, the second operation unit is further configured to:
and automatically checking interface logic between the at least two target APIs by operating the SDK test case codes corresponding to the at least two target APIs to obtain a first operation result, wherein the interface logic indicates a calling sequence between the at least two target APIs.
Optionally, the apparatus further comprises:
a second obtaining module, configured to obtain an application package APK, where the APK is an installation data package of the target application;
and the sending module is used for sending the APK and the SDK test case code to a test terminal, the test terminal is used for automatically running the SDK test case code under a scene of installing the target application program to obtain a second running result, and generating a second test report according to the second running result, the second test report comprises running data of the target application program when the target application program calls the target API on a target processor platform, and the target processor platform is a processor platform corresponding to the test terminal.
Optionally, the operation data includes at least one of functional data and performance data.
Optionally, the operation data includes the function data;
the operation module 1002 further includes:
and the third operation unit is used for automatically operating the SDK test case code and acquiring the realization condition of a target service function when the target API is called, wherein the target service function is an interface function corresponding to the target API.
Optionally, the operating data includes the performance data;
the operation module 1002 further includes:
and the fourth running unit is used for automatically running the SDK test case code and acquiring the use condition of system resources when the target API is called, wherein the system resources comprise at least one of Central Processing Unit (CPU) resources, Graphic Processing Unit (GPU) resources, memory resources and network resources.
Optionally, the apparatus further comprises:
the receiving module is used for receiving the test case adding and deleting operation of the target API;
and the modification module is used for modifying the SDK test case codes corresponding to the target API according to the test case adding and deleting operation.
In the embodiment of the application, the interface test case codes corresponding to each API in the SDK are coded to obtain the SDK test case codes, and the interface test cases are realized according to the service functions corresponding to each API, so that when the computer equipment automatically runs the SDK test case codes, the process that an application program calls a target API can be simulated, and corresponding running data are obtained and fed back to testers. Because the SDK test case codes can automatically run and the test cases of the API are all written in the test case codes, the test of each interface function in the SDK can be realized without interface operation in an application program interface manually by a user, the test flow is simplified, the test efficiency of the SDK is further improved, and in addition, the SDK test in the embodiment can be refined to an interface logic layer, so that the reason of running errors can be accurately positioned if the test result is not in accordance with expectation.
Referring to fig. 11, a block diagram of a computer device according to an exemplary embodiment of the present application is shown. The computer device may be used to implement the SDK test method provided in the above embodiments, in particular:
the computer device 1100 includes a CPU, a system Memory 1104 including a Random Access Memory (RAM) 1102 and a Read-Only Memory (ROM) 1103, and a system bus 1105 connecting the system Memory 1104 and the central processing unit 1101. The computer device 1100 also includes a basic Input/Output system (I/O system) 1106, which facilitates transfer of information between devices within the computer device, and a mass storage device 1107 for storing an operating system 1113, application programs 1114, and other program modules 1115.
The basic input/output system 1106 includes a display 1108 for displaying information and an input device 1109 such as a mouse, keyboard, etc. for user input of information. Wherein the display 1108 and input device 1109 are connected to the central processing unit 1101 through an input output controller 1110 connected to the system bus 1105. The basic input/output system 1106 may also include an input/output controller 1110 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 1110 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 1107 is connected to the central processing unit 1101 through a mass storage controller (not shown) that is connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable storage media provide non-volatile storage for the computer device 1100. That is, the mass storage device 1107 may include a computer-readable storage medium (not shown) such as a hard disk or Compact disk-Only Memory (CD-ROM) drive.
Without loss of generality, the computer-readable storage media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable storage instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other solid state Memory technology, CD-ROM, Digital Versatile Disks (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1104 and mass storage device 1107 described above may be collectively referred to as memory.
The memory stores one or more programs configured to be executed by the one or more central processing units 1101, the one or more programs containing instructions for implementing the method embodiments described above, the central processing unit 1101 executing the one or more programs implementing the methods provided by the various method embodiments described above.
The memory also includes one or more programs, stored in the memory, that include instructions for performing the steps performed by the computer device in the methods provided by the embodiments of the present application.
The embodiment of the present application further provides a computer-readable medium, where at least one instruction is stored, and the at least one instruction is loaded and executed by the processor to implement the SDK testing method according to the above embodiments.
Embodiments of the present application also provide a computer program product including computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the SDK testing method provided in the various alternative implementations of the above aspects.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (12)

1. A Software Development Kit (SDK) testing method is characterized by comprising the following steps:
the method comprises the steps of obtaining SDK test case codes, wherein the SDK test case codes are generated according to interface test cases corresponding to target Application Program Interfaces (APIs), different APIs in the SDK correspond to different interface test cases, and the target APIs are called APIs in the running process of a target application program;
responding to the received test operation of the SDK, automatically running the SDK test case code to obtain a first running result, wherein the SDK test case code calls the target API in the SDK in the running process;
and generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API.
2. The method of claim 1, wherein automatically running the SDK test case code in response to receiving the test operation on the SDK, resulting in a first run result, comprises:
responding to the received first test operation on the SDK, automatically running the SDK test case code corresponding to the single target API to obtain a first running result;
and responding to the received second test operation on the SDK, and automatically running the SDK test case codes corresponding to at least two target APIs to obtain a first running result.
3. The method of claim 2, wherein automatically running the SDK test case code corresponding to a single target API to obtain the first running result comprises:
and automatically checking parameter logic corresponding to the target API by operating the SDK test case code corresponding to the single target API to obtain the first operation result, wherein the parameter logic comprises at least one of parameter type, parameter range, parameter sequence and parameter value.
4. The method of claim 2, wherein automatically running the SDK test case code corresponding to at least two of the target APIs to obtain the first running result comprises:
and automatically checking interface logic between the at least two target APIs by operating the SDK test case codes corresponding to the at least two target APIs to obtain a first operation result, wherein the interface logic indicates a calling sequence between the at least two target APIs.
5. The method of any of claims 1 to 4, further comprising:
acquiring an application program package (APK), wherein the APK is an installation data package of the target application program;
and sending the APK and the SDK test case code to a test terminal, wherein the test terminal is used for automatically operating the SDK test case code under a scene of installing the target application program to obtain a second operation result, and generating a second test report according to the second operation result, the second test report comprises operation data of the target application program when the target application program calls the target API on a target processor platform, and the target processor platform is a processor platform corresponding to the test terminal.
6. The method of any of claims 1 to 4, wherein the operational data comprises at least one of functional data and performance data.
7. The method of claim 6, wherein the operational data comprises the functional data;
the automatically running the SDK test case code to obtain a first running result, further comprising:
and automatically running the SDK test case code, and acquiring the realization condition of a target service function when the target API is called, wherein the target service function is an interface function corresponding to the target API.
8. The method of claim 6, wherein the operational data comprises the performance data;
the automatically running the SDK test case code to obtain a first running result, further comprising:
and automatically running the SDK test case code, and acquiring the use condition of system resources when the target API is called, wherein the system resources comprise at least one of Central Processing Unit (CPU) resources, Graphic Processing Unit (GPU) resources, memory resources and network resources.
9. The method of any of claims 1 to 4, wherein before the obtaining the SDK test case code, the method further comprises:
receiving the test case adding and deleting operation of the target API;
and modifying the SDK test case code corresponding to the target API according to the test case adding and deleting operation.
10. An SDK testing apparatus, comprising:
the system comprises a first acquisition module, a first test module and a second test module, wherein the first acquisition module is used for acquiring SDK test case codes, and the SDK test case codes are generated according to interface test cases corresponding to target Application Program Interfaces (APIs), different APIs in the SDK correspond to different interface test cases, and the target APIs are the APIs called by the target application programs in the running process;
the operation module is used for responding to the received test operation of the SDK and automatically operating the SDK test case code to obtain a first operation result, wherein the SDK test case code calls the target API in the SDK in the operation process;
and the generating module is used for generating a first test report according to the first operation result, wherein the first test report comprises operation data when the target application program calls the target API.
11. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, the at least one instruction, the at least one program, the set of codes, or the set of instructions being loaded and executed by the processor to implement the SDK testing method of any of claims 1 to 9.
12. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the SDK testing method of any of claims 1 to 9.
CN202010641547.5A 2020-07-06 2020-07-06 SDK test method, device, equipment and storage medium Active CN111651366B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010641547.5A CN111651366B (en) 2020-07-06 2020-07-06 SDK test method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010641547.5A CN111651366B (en) 2020-07-06 2020-07-06 SDK test method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111651366A true CN111651366A (en) 2020-09-11
CN111651366B CN111651366B (en) 2023-08-08

Family

ID=72342716

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010641547.5A Active CN111651366B (en) 2020-07-06 2020-07-06 SDK test method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111651366B (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667509A (en) * 2020-12-28 2021-04-16 郑州阿帕斯数云信息科技有限公司 SDK access test method and device
CN112860356A (en) * 2021-02-10 2021-05-28 北京百度网讯科技有限公司 API call control method and device, electronic equipment and storage medium
CN113032246A (en) * 2021-03-04 2021-06-25 成都佰维存储科技有限公司 SSD (solid State disk) firmware operation method and device, readable storage medium and electronic equipment
CN113157607A (en) * 2021-05-20 2021-07-23 中国第一汽车股份有限公司 Equipment adaptation method, device, storage medium and computer equipment
CN113434389A (en) * 2021-06-11 2021-09-24 青岛海尔科技有限公司 Data verification method and device, storage medium and electronic device
CN113485914A (en) * 2021-06-09 2021-10-08 镁佳(北京)科技有限公司 Vehicle-mounted voice SDK testing method, device and system
CN113590465A (en) * 2021-06-28 2021-11-02 四川新网银行股份有限公司 Method for automatically generating mock service based on SDK
CN114157891A (en) * 2021-11-26 2022-03-08 瑞森网安(福建)信息科技有限公司 Screen projection terminal self-adaptive docking method, system and storage medium
CN114915565A (en) * 2022-05-06 2022-08-16 上海哔哩哔哩科技有限公司 Method and system for debugging network
CN117215966A (en) * 2023-11-09 2023-12-12 成都爱旗科技有限公司 Test method and test device for chip SDK interface and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101930400A (en) * 2010-08-20 2010-12-29 北京神州泰岳软件股份有限公司 SDK (Software Development Kit) automatic test system and method
CN105718251A (en) * 2014-12-03 2016-06-29 苏宁云商集团股份有限公司 Multilanguage SDK (software development kit) automatic implementation method and system
CN109376088A (en) * 2018-10-24 2019-02-22 网宿科技股份有限公司 A kind of automatization test system and automated testing method
CN109960644A (en) * 2017-12-22 2019-07-02 北京奇虎科技有限公司 A kind of test method and system of SDK

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101930400A (en) * 2010-08-20 2010-12-29 北京神州泰岳软件股份有限公司 SDK (Software Development Kit) automatic test system and method
CN105718251A (en) * 2014-12-03 2016-06-29 苏宁云商集团股份有限公司 Multilanguage SDK (software development kit) automatic implementation method and system
CN109960644A (en) * 2017-12-22 2019-07-02 北京奇虎科技有限公司 A kind of test method and system of SDK
CN109376088A (en) * 2018-10-24 2019-02-22 网宿科技股份有限公司 A kind of automatization test system and automated testing method

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667509A (en) * 2020-12-28 2021-04-16 郑州阿帕斯数云信息科技有限公司 SDK access test method and device
CN112667509B (en) * 2020-12-28 2023-04-07 郑州阿帕斯数云信息科技有限公司 SDK access test method and device
CN112860356A (en) * 2021-02-10 2021-05-28 北京百度网讯科技有限公司 API call control method and device, electronic equipment and storage medium
CN112860356B (en) * 2021-02-10 2023-08-15 北京百度网讯科技有限公司 API call control method and device, electronic equipment and storage medium
CN113032246A (en) * 2021-03-04 2021-06-25 成都佰维存储科技有限公司 SSD (solid State disk) firmware operation method and device, readable storage medium and electronic equipment
CN113032246B (en) * 2021-03-04 2023-10-03 成都佰维存储科技有限公司 SSD firmware operation method and device, readable storage medium and electronic equipment
CN113157607B (en) * 2021-05-20 2023-03-21 中国第一汽车股份有限公司 Equipment adaptation method, device, storage medium and computer equipment
CN113157607A (en) * 2021-05-20 2021-07-23 中国第一汽车股份有限公司 Equipment adaptation method, device, storage medium and computer equipment
CN113485914A (en) * 2021-06-09 2021-10-08 镁佳(北京)科技有限公司 Vehicle-mounted voice SDK testing method, device and system
CN113485914B (en) * 2021-06-09 2022-03-08 镁佳(北京)科技有限公司 Vehicle-mounted voice SDK testing method, device and system
CN113434389A (en) * 2021-06-11 2021-09-24 青岛海尔科技有限公司 Data verification method and device, storage medium and electronic device
CN113590465B (en) * 2021-06-28 2023-06-06 四川新网银行股份有限公司 Method for automatically generating mock service based on SDK
CN113590465A (en) * 2021-06-28 2021-11-02 四川新网银行股份有限公司 Method for automatically generating mock service based on SDK
CN114157891A (en) * 2021-11-26 2022-03-08 瑞森网安(福建)信息科技有限公司 Screen projection terminal self-adaptive docking method, system and storage medium
CN114157891B (en) * 2021-11-26 2024-03-22 瑞森网安(福建)信息科技有限公司 Self-adaptive docking method, system and storage medium for screen-throwing terminal
CN114915565A (en) * 2022-05-06 2022-08-16 上海哔哩哔哩科技有限公司 Method and system for debugging network
CN114915565B (en) * 2022-05-06 2023-09-19 上海哔哩哔哩科技有限公司 Network debugging method and system
CN117215966A (en) * 2023-11-09 2023-12-12 成都爱旗科技有限公司 Test method and test device for chip SDK interface and electronic equipment
CN117215966B (en) * 2023-11-09 2024-02-02 成都爱旗科技有限公司 Test method and test device for chip SDK interface and electronic equipment

Also Published As

Publication number Publication date
CN111651366B (en) 2023-08-08

Similar Documents

Publication Publication Date Title
CN111651366B (en) SDK test method, device, equipment and storage medium
CN109302522B (en) Test method, test device, computer system, and computer medium
WO2020140820A1 (en) Software testing method, system, apparatus, device, medium, and computer program product
CN105094783B (en) method and device for testing stability of android application
US7895565B1 (en) Integrated system and method for validating the functionality and performance of software applications
US20150100829A1 (en) Method and system for selecting and executing test scripts
US20150100832A1 (en) Method and system for selecting and executing test scripts
US20100146340A1 (en) Analyzing Coverage of Code Changes
CN111124919A (en) User interface testing method, device, equipment and storage medium
CN105159833A (en) Automatic testing device and method
CN105426298A (en) ADB (Android debug bridge)-based software test method and system
US20150100830A1 (en) Method and system for selecting and executing test scripts
CN109388569B (en) Method for remotely detecting environmental anomaly of client, test server and storage medium
US20150100831A1 (en) Method and system for selecting and executing test scripts
CN106126423A (en) The method of testing of game application, Apparatus and system
CN104424093A (en) Compatibility testing method and system
CN111338943A (en) Test method, test device, electronic equipment and readable storage medium
CN111258913A (en) Automatic algorithm testing method and device, computer system and readable storage medium
KR20080052341A (en) Automatic-testing system and method for embedded system software and test scenario composing method
CN112241360A (en) Test case generation method, device, equipment and storage medium
CN107608873B (en) Software testing method and system and testing platform
CN112231206A (en) Script editing method for application program test, computer readable storage medium and test platform
CN111767209A (en) Code testing method, device, storage medium and terminal
CN112527312B (en) Test method and test device for embedded system
CN116627850B (en) Function debugging method and device, storage medium and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant