WO2019200721A1 - Sdk 兼容性检测方法、装置、设备及可读存储介质 - Google Patents
Sdk 兼容性检测方法、装置、设备及可读存储介质 Download PDFInfo
- Publication number
- WO2019200721A1 WO2019200721A1 PCT/CN2018/094105 CN2018094105W WO2019200721A1 WO 2019200721 A1 WO2019200721 A1 WO 2019200721A1 CN 2018094105 W CN2018094105 W CN 2018094105W WO 2019200721 A1 WO2019200721 A1 WO 2019200721A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- sdk
- detected
- sdks
- application software
- compatibility
- Prior art date
Links
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
Definitions
- the present application relates to the field of SDK compatibility detection technologies, and in particular, to an SDK compatibility detection method, apparatus, device, and readable storage medium.
- SDKs are used in mobile terminals such as mobile phones and tablets (Software Development). Kit, software development kit) to achieve a variety of application software (Application, APP) multiple functional requirements, and in the implementation of functional requirements may be due to compatibility issues between the various SDKs used in the APP, APP function failure, such as Compatibility issues with different third-party SDKs have made it impossible to implement certain features of the APP.
- APP application software
- the main purpose of the present application is to provide an SDK compatibility detection method, apparatus, device, and readable storage medium, which is intended to solve the problem of SDK compatibility detection by deleting the SDK and the corresponding service code in the prior art, which may be accidentally deleted and complicated in operation. Trivial problems.
- the present application provides an SDK compatibility detection method, where the SDK compatibility detection method includes the following steps:
- Reading a configuration file of the application software determining a feature element of the application software according to the information in the configuration file, comparing the feature element with a feature value of each SDK, and The SDK having the feature value consistent with the feature element is determined as the SDK to be detected of the application software;
- the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with a corresponding pseudo-SDK, and the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK is obtained, and is determined according to the detection result.
- the present application further provides an SDK compatibility detecting apparatus, where the SDK compatibility detecting apparatus includes:
- a determining module configured to read a configuration file of the application software when the application software is abnormal, and determine a feature element of the application software according to the information in the configuration file, and compare the feature element with a feature value of each SDK And determining, by the SDK having the feature value consistent with the feature element, the SDK to be detected of the application software;
- a reading module configured to read a header file of each of the to-be-detected SDKs, and generate a pseudo-SDK corresponding to each of the to-be-detected SDKs according to information in each of the header files;
- a detecting module configured to replace the target to-be-detected SDK in each of the to-be-detected SDKs with a corresponding pseudo-SDK, and obtain a detection result of the application software function detection when the target to-be-detected SDK is replaced with a corresponding pseudo-SDK, and according to The detection result determines the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.
- the present application further provides an SDK compatibility detecting device, where the SDK compatibility detecting device includes: a memory, a processor, a communication bus, and an SDK compatibility detecting program stored on the memory;
- the communication bus is used to implement connection communication between a processor and a memory
- the processor is configured to execute the SDK compatibility detection program to implement the following steps:
- Reading a configuration file of the application software determining a feature element of the application software according to the information in the configuration file, comparing the feature element with a feature value of each SDK, and The SDK having the feature value consistent with the feature element is determined as the SDK to be detected of the application software;
- the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with a corresponding pseudo-SDK, and the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK is obtained, and is determined according to the detection result.
- the present application also provides a readable storage medium storing one or more programs, the one or more programs being executable by one or more processors Used for:
- Reading a configuration file of the application software determining a feature element of the application software according to the information in the configuration file, comparing the feature element with a feature value of each SDK, and The SDK having the feature value consistent with the feature element is determined as the SDK to be detected of the application software;
- the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with a corresponding pseudo-SDK, and the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK is obtained, and is determined according to the detection result.
- the SDK compatibility detection method, device, device, and readable storage medium of the embodiment when the application software is abnormal, reads the configuration file of the application software, determines the feature element of the application software according to the information in the configuration file, and sets the feature Comparing the element and the characteristic value of each SDK, determining the SDK having the feature value consistent with the feature element as the SDK to be detected of the application software; reading the header file of each SDK to be detected, and generating and waiting according to the information in each header file Detecting the pseudo-SDK corresponding to the SDK; replacing the target to-be-detected SDK in each of the to-be-detected SDKs with the corresponding pseudo-SDK, and obtaining the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK, and according to The detection result is the compatibility of the target to-be-detected SDK in the SDK to be detected with other SDKs to be detected.
- the solution generates a pseudo-SDK corresponding to the SDK to be detected in the application software, and replaces the target to be detected SDK of the to-be-detected SDK in the original application software with the pseudo-SDK, and obtains the detection result of detecting the application software function after the replacement;
- the detection result of the application software function is used to determine the compatibility between the target to-be-detected SDK and the other to-be-detected SDKs in each SDK to be detected, so as to avoid deleting the SDK and the corresponding service code one by one, and the operation is simple and convenient.
- FIG. 1 is a schematic flowchart of a first embodiment of an SDK compatibility detecting method according to the present application
- FIG. 2 is a schematic flow chart of a second embodiment of the SDK compatibility detecting method of the present application.
- FIG. 3 is a schematic diagram of functional modules of a first embodiment of the SDK compatibility detecting apparatus of the present application
- FIG. 4 is a schematic structural diagram of a device in a hardware operating environment involved in a method according to an embodiment of the present application.
- the application provides an SDK compatibility detection method.
- FIG. 1 is a schematic flowchart diagram of a first embodiment of an SDK compatibility detecting method according to the present application.
- the SDK compatibility detection method includes:
- Step S10 when the application software is abnormal, reading a configuration file of the application software, determining a feature element of the application software according to the information in the configuration file, comparing the feature element with a feature value of each SDK, and Determining the SDK having the feature value consistent with the feature element as the SDK to be tested of the application software;
- the SDK compatibility detection of the present application is applicable to compatibility detection between multiple SDKs involved in various application software installed in the IOS system, and the application software is installed on mobile terminals such as mobile phones and tablet computers, such as WeChat and Taobao.
- a variety of APPs of the class which are essentially third-party applications.
- the SDK is used to assist in the development of a collection of documentation, examples, and tools for application software.
- many functions in the APP are implemented by accessing various SDKs.
- the SDK provides an interface for implementing various functions. When the APP needs to implement a certain function, the interface for implementing the function SDK is called. By calling the SDK to implement various functions of the APP, the development efficiency of the application software can be greatly improved.
- Different SDKs are developed by different developers.
- SDKs with different sources may be incompatible with each other, resulting in abnormal function of the application software.
- the application software is abnormal, it needs to be detected whether it is caused by incompatibility between the accessed SDKs.
- the configuration file of the application software is read, where the configuration file is configured with each SDK feature element accessed by the application software. .
- there are eigenvalues that characterize the SDK For example, for the three SDKs A, B, and C, the eigenvalues of the three are a1, a2, b1, b2, b3, and c1, c2, respectively. C3.
- each feature element involved in the application software can be determined, and the feature values of each feature element and each SDK are compared, and when each feature element exists with an SDK A feature element with the same eigenvalue indicates that the SDK is accessed in the application software. If the feature elements of the application software are determined according to the information in the configuration file are a1, a2, c1, c2, c3, d1, and d2, the feature elements c1, c2 are consistent because the feature values of the feature elements a1, a2, and A are identical. C3 and C have the same eigenvalues, so that the application software can access the two SDKs A and C.
- the SDKs connected to the SDK need to be tested for compatibility, so that the SDK with the feature value consistent with the feature element, that is, the SDK accessed in the application software is determined as an application.
- the software's SDK to be tested in order to detect it.
- Step S20 reading a header file of each of the to-be-detected SDKs, and generating a pseudo-SDK corresponding to each of the to-be-detected SDKs according to information in each of the header files;
- the SDK includes a header file and a code body.
- the header file is used to define and declare macros, structures, and functions used in the code body, and describes an interface opened in the SDK; the code body is used to implement the SDK function.
- the header files of the respective to-be-detected SDKs are read, and a pseudo-SDK corresponding to each of the to-be-detected SDKs is generated according to the information included in the header file.
- This pseudo SDK only has the header file content of the SDK to be detected, and does not include its code body part, which is generated by a preset basic script program.
- the preset basic script program is preset code for generating a header file, and provides a basic framework for generating a header file, which is a common content of each SDK header file, and a variable for each SDK characteristic information.
- the form is embedded in the underlying framework.
- the function a needs to be declared in the header file of the SDK to implement the A interface function by calling the function a through the code body in the SDK to be detected.
- a header file containing the function a can be generated using a preset base script, but does not include the pseudo SDK of the code body that calls the function a.
- the generated pseudo SDK includes a header file for declaring an interface in the to-be-detected SDK
- the pseudo SDK is consistent with the function of the to-be-detected SDK from the perspective of application calling; however, the interface function is not involved in the pseudo SDK.
- the code body which can not really realize the functional functions of the SDK to be tested.
- Step S30 replacing the target to-be-detected SDK in each of the to-be-detected SDKs with a corresponding pseudo-SDK, and acquiring a detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK, and according to the The detection result determines the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.
- each of the to-be-detected SDKs is detected by the pseudo-SDK, and a mechanism for detecting each of the to-be-detected SDKs is adopted.
- the to-be-detected SDK is used as the target to be detected SDK in each of the to-be-detected SDKs, and is replaced by a pseudo-SDK corresponding to the target to be detected SDK, and is performed once every replacement. Whether the application software function is detected normally.
- the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with its corresponding pseudo-SDK, and the function of the application software after replacing the target to-be-detected SDK with the corresponding pseudo-SDK is detected to determine whether the function of the application software returns to normal.
- Obtain the detection result of the application software function detection after the replacement operation and determine whether the function of the replaced application software returns to normal according to the detection result. According to whether the application software returns to the normal detection result, the compatibility of the replaced target to-be-detected SDK with other unreplaced SDKs to be detected can be determined. If it returns to normal, it indicates that the function abnormality of the application software is caused by the compatibility of the replacement target to be tested SDK.
- the step of determining, according to the detection result, the compatibility between the target to-be-detected SDK in each of the to-be-detected SDKs and other to-be-detected SDKs includes:
- step S31 when the detection result is that the application software function is normal, it is determined that the target to-be-detected SDK of the to-be-detected SDK is incompatible with other to-be-detected SDKs, and the target to be detected SDK in the to-be-detected SDK has The feature value is added to the prompt information to output the display;
- the function of the application software returns to normal, indicating that the function abnormality of the application software is caused by the compatibility of the replacement target to be detected SDK, that is, the replacement target to be detected SDK and other unreplaced There is an incompatibility between the SDKs to be detected, which causes the application software to be abnormal.
- the feature value of the currently-replaced target to-be-detected SDK is added to the prompt information, and the prompt information is output and displayed, so that the detecting personnel can quickly determine the to-be-detected SDK that causes the application software to be abnormal according to the feature value in the prompt information.
- step S32 when the detection result is that the application software function is abnormal, the next to-be-detected SDK is obtained as the target to-be-detected SDK in the to-be-detected SDK, and the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with The corresponding pseudo SDK step.
- the function of the application software is still not restored, indicating that the function abnormality of the application software is not caused by the compatibility of the currently-replaced target to be detected SDK, that is, the currently-replaced target to be detected SDK. Compatible with other SD cards to be tested that have not been replaced.
- the target to be tested SDK is compatible with other SDKs to be tested.
- the next SDK to be tested can randomly select each SDK to be detected, or can sort the SDKs to be detected and sort them according to the sort order.
- the pseudo SDKs corresponding to p1, p2, and p3 are q1, q2, and q3, respectively, and replace p1 with q1, so that the SDK of the application software to be tested is Q1, p2, and p3, check whether the function of the application software returns to normal at this time. If it returns to normal, it indicates that there is an incompatibility between the target to be detected SDKp1 and p1 and p2; if it is not restored, replace p2 with q2 to make the application
- the software to be tested SDKs are p1, q2, and p3. It is detected whether the function of the application software returns to normal at this time.
- the SDK compatibility detection method of the embodiment when the application software is abnormal, reads the configuration file of the application software, determines the feature element of the application software according to the information in the configuration file, and compares the feature element with the feature value of each SDK. Determining an SDK having a feature value consistent with the feature element as the SDK to be detected of the application software; reading a header file of each SDK to be detected, and generating a pseudo SDK corresponding to each SDK to be detected according to the information in each header file; The target to-be-detected SDK in the to-be-detected SDK is replaced with a corresponding pseudo-SDK, and the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK is acquired, and the target in the SDK is to be detected according to the detection result.
- the compatibility of the SDK to be tested with other SDKs to be tested The solution generates a pseudo-SDK corresponding to the SDK to be detected in the application software, and replaces the target to be detected SDK of the to-be-detected SDK in the original application software with the pseudo-SDK, and obtains the detection result of detecting the application software function after the replacement;
- the detection result of the application software function is used to determine the compatibility between the target to-be-detected SDK and the other to-be-detected SDKs in each SDK to be detected, so as to avoid deleting the SDK and the corresponding service code one by one, and the operation is simple and convenient.
- the detection result is that the application software function is abnormal
- Step S321 When the detection result is that the application software function is abnormal, determine, according to the result log file corresponding to the function abnormality, whether the type of the function abnormality changes;
- the function of the application software is not restored, and when the application software is still abnormal, the function abnormality may be different from the functional abnormality before the target to be detected by the SDK replacement.
- the function m1 of the application software is abnormal
- the function m2 of the application software is abnormal after the replacement.
- the function abnormality of the application software is not restored after the replacement operation, the type of the abnormal function changes. It can be explained that the currently replaced target to be detected SDK has an impact on the functional abnormality of the application software.
- the implementation determines whether the type of the functional abnormality changes according to the result log file corresponding to the functional abnormality when the application software function is still abnormal.
- the log file is a file that records the events that occur during the running of the application software.
- the function exceptions of the application software are also recorded.
- the recorded content includes abnormal time, abnormal process, abnormal parameters and other information.
- the result log file in this embodiment is a log file generated by detecting that the application software is still abnormal after performing the replacement operation on the target to be detected SDK, reading the result log file, and performing the target abnormality according to the function abnormal information embodied therein
- the functional abnormality information before the SDK replacement operation is detected for comparison, and whether the two are consistent to determine whether the type of the functional abnormality has changed is determined to determine whether the target pending detection SDK has an influence on the functional abnormality of the application software.
- Step S322 if the type of the function abnormality changes, the target to-be-detected SDK in the to-be-detected SDK is set as the to-be-confirmed SDK;
- the information in the result log file determines that the type of the function abnormality changes, it indicates that the target to be detected SDK has an impact on the function abnormality of the application software.
- the n1 and n3 are incompatible
- n2 is incompatible with n3 and n4
- the incompatibility caused by n1 and n2 together causes the application software function.
- the function of the application software is still abnormal, but the type of the exception changes, that is, the currently replaced n1 has an impact on the function abnormality of the application software, and is set as the SDK to be confirmed.
- the prompting information needs to be output to the detecting personnel, so that the detecting personnel further detects the SDK to be confirmed, and confirms whether it is an abnormal function of the application software.
- step S323 if the type of the abnormality of the function is not changed, the next to-be-detected SDK is obtained as the target to-be-detected SDK in the to-be-detected SDK, and the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with a corresponding one.
- the steps of the pseudo SDK if the type of the abnormality of the function is not changed, the next to-be-detected SDK is obtained as the target to-be-detected SDK in the to-be-detected SDK, and the target to-be-detected SDK in each of the to-be-detected SDKs is replaced with a corresponding one.
- the information in the result log file determines that the type of the function abnormality has not changed, it indicates that the target to be detected SDK is not the cause of the application software abnormality, and the next to-be-tested SDK is obtained as a new target to be detected in the to-be-detected SDK.
- the SDK replaces the new target to-be-detected SDK with its corresponding pseudo-SDK to determine the compatibility of the new target to-be-detected SDK with other to-be-detected SDKs.
- a second embodiment of the SDK compatibility detection method of the present application is proposed.
- the method will have a feature value consistent with a feature element.
- the steps of the SDK being determined as the SDK of the application to be tested include:
- Step S11 determining an SDK having a feature value consistent with the feature element as an initial to-be-detected SDK of the application software, and acquiring an abnormality log file generated by the application function abnormality application software;
- the cause of the abnormality should also be related to the SDK related to the function, and the correlation with other SDKs is more weak. Therefore, when detecting an application software function abnormality caused by SDK compatibility, the primary detection of the to-be-detected SDK related to the type may be performed for the type of the application function abnormality, so as to improve the detection efficiency.
- the SDK having the feature value consistent with the feature element is determined as the initial to-be-detected SDK of the application software, that is, all the SDKs accessed by the application software are set as the initial to-be-tested SDK of the application software, and need to be determined from all the initial to-be-tested SDKs.
- the application software is abnormally related to the SDK to be detected. Further, the abnormality log file generated by the application software for the abnormal function is obtained.
- the abnormal log file records the event information of the application software that is abnormal before the SDK is replaced, including the abnormal process, the abnormal thread, the abnormal parameter, etc., so as to be Each event information in this abnormal log file determines the SDK to be detected related to the functional abnormality.
- Step S12 Determine, according to the information in the abnormal log file, the type of the abnormal function that is generated by the application software, and determine the SD to be detected from the initial to-be-detected SDK according to the corresponding relationship between the abnormal function type and the SDK.
- the type of the abnormal function that occurs in the application software is determined according to the function abnormality information embodied in the abnormal log file, such as a function Z of the application software, and The function is related to the thread k.
- the application software is abnormal, and the exception thread included in the information of the abnormal log file involves k, it can be determined that the type of the abnormal function is Z.
- the various functions in the application software are related to multiple SDKs, after determining the type of the abnormal function, according to the corresponding relationship between the abnormal function type and the SDK, that is, multiple SDKs related to the function, the SDK to be detected is determined from the preliminary to-be-tested SDK. .
- the initial to-be-detected SDK includes f1, f2, f3, f4, and f5.
- the SDK associated with it includes f2, f3, and f4.
- the corresponding function Z is matched with f2, f3, and f4.
- the relationship is determined from the initial to-be-detected SDKs F1, f2, f3, f4, and f5 to detect the SDKs k2, f3, and f4, and the primary detection of the SDKs, f3, and f4 to be detected is performed to improve the detection efficiency.
- a third embodiment of the SDK compatibility detection method of the present application is proposed.
- the determining is performed according to the detection result.
- the step of compatibility between the target to-be-detected SDK and the other to-be-detected SDKs in each of the to-be-detected SDKs includes:
- step S40 after the detection result is that the application software function is abnormal, it is determined whether the SD to be detected is all performing compatibility detection. If the to-be-detected SDK performs compatibility detection, the initial to-be-detected SDK is invoked. The other to-be-detected SDKs other than the to-be-detected SDK perform compatibility detection.
- the detection result is still abnormal in the application software function, it is determined whether each of the to-be-detected SDKs is carried.
- There is a detection completion identifier that is, it is judged that all the to-be-tested SDKs are subjected to compatibility detection.
- the other to-be-detected SDKs other than the to-be-detected SDK in the initial to-be-detected SDK are called for compatibility detection to determine whether the other is detected by the other.
- the incompatibility of the SDK to be detected causes the function of the application software to be abnormal.
- the method includes:
- step S50 it is determined whether the other to-be-detected SDKs are all performing compatibility detection. If the other to-be-detected SDKs are all performing compatibility detection, the information that the SDK compatibility is normal in the application software is output.
- the function of the application software is still abnormal, it is determined whether the other SDKs to be detected are abnormal.
- the compatibility check is performed, that is, the other to-be-tested SDKs carry the detection completion identifier.
- the function abnormality of the application software is not caused by the compatibility between the docked SDKs, and the SDK compatibility information in the output application software is normal.
- the compatibility between the SDKs in the characterization application software is good.
- a fourth embodiment of the SDK compatibility detection method of the present application is proposed.
- the reading is performed.
- the step of generating a header file of the SDK and generating a pseudo SDK corresponding to each of the to-be-detected SDKs according to the information in each of the header files includes:
- Step S21 Determine, according to the SDK and the preset identifier comparison table, a target preset identifier corresponding to the to-be-detected SDK, and determine, according to the target preset identifier, whether there is a pseudo SDK corresponding to the to-be-detected SDK. ;
- each application software may have a functional abnormality, and the same SDK may be used between different application software.
- the application software with the first dysfunction will generate a pseudo-SDK containing the header file for the SDK
- the application software with the dysfunction will also generate a pseudo-SDK containing the header file for the SDK.
- a SDK and a preset identifier comparison table are set, and different SDKs are used to represent different SDKs, and the preset identifiers in the comparison table have a one-to-one correspondence with the SDK.
- Such as the SDK in the comparison table S1 corresponds to the preset identifier e1, and S2 corresponds to the preset identifier e2.
- the corresponding target preset identifier is e1.
- a pseudo SDK is generated, and the pseudo SDK carries a preset identifier corresponding to the SDK to be detected. Therefore, for the current to-be-detected SDK, it is determined whether the pseudo-SDK corresponding to the current to-be-detected SDK already exists according to the target preset identifier, that is, whether the application software having the abnormal function first has generated the corresponding SDK corresponding to the current to-be-detected SDK. Pseudo SDK.
- Step S22 when there is a pseudo SDK corresponding to the to-be-detected SDK, the corresponding pseudo SDK is invoked;
- Step S23 when there is no SDK corresponding to the to-be-detected SDK, the header file of the to-be-detected SDK is read, and the information is generated according to the information in the header file and the target preset identifier.
- the pseudo SDK corresponding to the detection SDK is mentioned.
- the target preset identifier When it is determined that there is no pseudo SDK corresponding to the to-be-detected SDK according to the target preset identifier, it indicates that the application software having the abnormal function first does not have the SDK to be detected, and the pseudo SDK including the header file is not generated for the to-be-detected SDK. Thereby, the header file of the SDK to be detected is read, and a pseudo SDK corresponding to the SDK to be detected is generated according to the information in the header file and the target preset identifier.
- the pseudo SDK is identified by the target preset identifier, so that it is convenient to determine whether a pseudo SDK exists in the to-be-detected SDK corresponding to the subsequent abnormal function.
- the present application provides an SDK compatibility detecting apparatus.
- the SDK compatibility detecting apparatus includes:
- the determining module 10 is configured to read a configuration file of the application software when the application software is abnormal in function, determine a feature element of the application software according to the information in the configuration file, and set the feature element and the feature value of each SDK Comparing, and determining an SDK having a feature value consistent with the feature element as the SDK to be detected of the application software;
- a reading module 20 configured to read a header file of each of the to-be-detected SDKs, and generate a pseudo-SDK corresponding to each of the to-be-detected SDKs according to information in each of the header files;
- the detecting module 30 is configured to replace the target to-be-detected SDK in each of the to-be-detected SDKs with a corresponding pseudo-SDK, and obtain a detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK, and Determining the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs according to the detection result.
- the determining module 10 reads the configuration file of the application software, determines the characteristic element of the application software according to the information in the configuration file, and sets the feature element and the characteristics of each SDK. For comparison, the SDK having the feature value consistent with the feature element is determined as the SDK to be detected of the application software; the reading module 20 reads the header file of each SDK to be detected, and generates and processes the SDK to be detected according to the information in each header file.
- the detecting module 30 replaces the target to-be-detected SDK in each of the to-be-detected SDKs with the corresponding pseudo-SDK, and obtains the detection result of the application software function detection when the target to-be-detected SDK is replaced with the corresponding pseudo-SDK, and According to the detection result, the compatibility of the target to-be-detected SDK in the SDK to be tested and other SDKs to be detected is detected.
- the solution generates a pseudo-SDK corresponding to the SDK to be detected in the application software, and replaces the target to be detected SDK of the to-be-detected SDK in the original application software with the pseudo-SDK, and obtains the detection result of detecting the application software function after the replacement;
- the detection result of the application software function is used to determine the compatibility between the target to-be-detected SDK and the other to-be-detected SDKs in each SDK to be detected, so as to avoid deleting the SDK and the corresponding service code one by one, and the operation is simple and convenient.
- the virtual function modules of the SDK compatibility detecting device are stored in the memory 1005 of the SDK compatibility detecting device shown in FIG. 4, and when the processor 1001 executes the SDK compatibility detecting program, each module in the embodiment shown in FIG. 3 is implemented. The function.
- the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
- FIG. 4 is a schematic structural diagram of a device in a hardware operating environment involved in a method according to an embodiment of the present application.
- the SDK compatibility detecting device in this embodiment may be a PC (personal computer) ), it can also be terminal devices such as smartphones, tablets, e-book readers, and portable computers.
- the SDK compatibility detecting device may include: a processor 1001, such as a CPU (Central Processing) Unit, central processing unit, memory 1005, communication bus 1002.
- the communication bus 1002 is used to implement connection communication between the processor 1001 and the memory 1005.
- the memory 1005 can be a high speed RAM (random Access memory, random access memory, or stable memory (non-volatile Memory), such as disk storage.
- the memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.
- the SDK compatibility detecting device may further include a user interface, a network interface, a camera, and an RF (Radio). Frequency, RF) circuit, sensor, audio circuit, WiFi (Wireless Fidelity, wireless broadband) modules and more.
- the user interface may include a display, an input unit such as a keyboard, and the optional user interface may also include a standard wired interface, a wireless interface.
- the network interface can optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).
- the SDK compatibility detecting device structure shown in FIG. 4 does not constitute a limitation of the SDK compatibility detecting device, and may include more or less components than those illustrated, or may combine some components. Or different parts arrangement.
- an operating system As shown in FIG. 4, an operating system, a network communication module, and an SDK compatibility detecting program may be included in the memory 1005 as a computer storage medium.
- the operating system is a program that manages and controls the SDK compatibility detection device hardware and software resources, and supports the SDK compatibility test program and other software and/or programs.
- the network communication module is used to implement communication between components within the memory 1005 and to communicate with other hardware and software in the SDK compatibility detection device.
- the processor 1001 is configured to execute the SDK compatibility detecting program stored in the memory 1005, and implement the steps in the foregoing embodiments of the SDK compatibility detecting method.
- the application provides a readable storage medium storing one or more programs, the one or more programs being further executable by one or more processors for implementing the SDK compatibility described above
- the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the present application.
- a terminal device which may be a mobile phone, a computer, a server, or a network device, etc.
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)
- Stored Programmes (AREA)
Abstract
本申请公开一种SDK兼容性检测方法、装置、设备及可读存储介质,所述方法包括:当应用软件出现功能异常时,读取应用软件的配置文件,根据配置文件中的信息确定应用软件的特征元素,将具有与特征元素一致特征值的SDK 确定为应用软件的待检测 SDK;读取各待检测 SDK 的头文件,并根据各头文件中的信息生成与各待检测 SDK 对应的伪 SDK;将各待检测 SDK 中的目标待检测 SDK 替换为对应的伪 SDK,获取将目标待检测 SDK替换为对应的伪 SDK 时应用软件功能检测的检测结果,并根据检测结果确定目标待检测 SDK 与其他待检测 SDK 的兼容性。用伪 SDK 替换原有待检测 SDK 进行 SDK 兼容性检测,避免逐个删除 SDK,操作简便。
Description
本申请要求于2018年04月20日提交中国专利局、申请号为201810364741.6、发明名称为“SDK兼容性检测方法、装置、设备及可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在申请中。
技术领域
本申请主要涉及SDK兼容性检测技术领域,具体地说,涉及一种SDK兼容性检测方法、装置、设备及可读存储介质。
背景技术
目前手机、平板等移动终端中使用越来越多的SDK(Software Development
Kit,软件开发工具包)来实现各种应用软件(Application,APP)的多种功能需求,而在实现功能需求时可能因APP中所使用各SDK之间兼容性问题而出现APP功能故障,如来自不同第三方SDK所存在的兼容性问题,导致不能实现APP的某些功能。目前对于SDK之间的兼容性检测,需要逐个将SDK及相应的业务代码删除来进行检测,但删除时可能出现误删、且操作复杂繁琐。
发明内容
本申请的主要目的是提供一种SDK兼容性检测方法、装置、设备及可读存储介质,旨在解决现有技术中通过删除SDK及相应业务代码进行SDK兼容性检测,可能误删且操作复杂繁琐的问题。
为实现上述目的,本申请提供一种SDK兼容性检测方法,所述SDK兼容性检测方法包括以下步骤:
当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;
读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;
将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
此外,为实现上述目的,本申请还提出一种SDK兼容性检测装置,所述SDK兼容性检测装置包括:
确定模块,用于当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;
读取模块,用于读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;
检测模块,用于将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
此外,为实现上述目的,本申请还提出一种SDK兼容性检测设备,所述SDK兼容性检测设备包括:存储器、处理器、通信总线以及存储在所述存储器上的SDK兼容性检测程序;
所述通信总线用于实现处理器和存储器之间的连接通信;
所述处理器用于执行所述SDK兼容性检测程序,以实现以下步骤:
当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;
读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;
将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
此外,为实现上述目的,本申请还提供一种可读存储介质,所述可读存储介质存储有一个或者一个以上程序,所述一个或者一个以上程序可被一个或者一个以上的处理器执行以用于:
当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;
读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;
将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
本实施例的SDK兼容性检测方法、装置、设备及可读存储介质,当应用软件出现功能异常时,读取应用软件的配置文件,根据配置文件中的信息确定应用软件的特征元素,将特征元素和各SDK的特征值对比,将具有与特征元素一致特征值的SDK确定为应用软件的待检测SDK;读取各待检测SDK的头文件,并根据各头文件中的信息生成与各待检测SDK对应的伪SDK;将各待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据检测结果各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。本方案通过生成与应用软件中待检测SDK对应的伪SDK,使用伪SDK替换原有应用软件中各待检测SDK的目标待检测SDK,并获取替换后对应用软件功能进行检测的检测结果;通过应用软件功能检测的检测结果来判定各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性,避免逐个删除SDK及相应的业务代码,操作简单方便。
附图说明
图1是本申请的SDK兼容性检测方法第一实施例的流程示意图;
图2是本申请的SDK兼容性检测方法第二实施例的流程示意图;
图3是本申请的SDK兼容性检测装置第一实施例的功能模块示意图;
图4是本申请实施例方法涉及的硬件运行环境的设备结构示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请提供一种SDK兼容性检测方法。
请参照图1,图1为本申请SDK兼容性检测方法第一实施例的流程示意图。在本实施例中,所述SDK兼容性检测方法包括:
步骤S10,当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为应用软件的待检测SDK;
本申请的SDK兼容性检测适用于对IOS***所安装的各类应用软件中涉及的多个SDK之间的兼容性检测,应用软件为手机、平板电脑等移动终端上安装的诸如微信、淘宝此类的各种APP,其实质为第三方应用程序。SDK用于辅助开发应用软件的相关文档、范例和工具的集合。目前APP中的很多功能都是通过接入各种SDK实现,SDK向外提供用于实现各功能的接口,当APP需要实现某一功能时,则调用用于实现此功能SDK的接口。通过调用SDK来实现APP各种功能的方式,可在很大程度上提高应用软件的开发效率。不同的SDK由不同的开发者开发,当应用软件接入多个来自不同开发者开发的SDK时,此来源不同的SDK可能互相不兼容,而导致应用软件的功能异常。当应用软件出现功能异常时,需要检测是否因所接入SDK之间不兼容而引起,具体地,读取应用软件的配置文件,其中配置文件中配置有应用软件所接入的各个SDK特征元素。而对于开发者开发的SDK,则具有表征此SDK特征的特征值,如对于A、B、C三个SDK,三者的特征值分别为a1、a2,b1、b2、b3和c1、c2、c3。在读取应用软件的配置文件后,根据配置文件中的信息即可确定应用软件所涉及的各个特征元素,将各个特征元素和各个SDK的特征值对比,当各个特征元素中存在与某个SDK特征值一致的特征元素,则说明应用软件中接入了此SDK。如根据配置文件中的信息所确定应用软件的特征元素为a1、a2、c1、c2、c3、d1和d2,因特征元素a1、a2与A所具有的特征值一致,特征元素c1、c2、c3与C所具有的特征值一致,从而可确定应用软件接入了A和C两个SDK。为了确定应用软件中各SDK的兼容性,对其所接入的SDK均需要进行兼容性检测,从而将此具有与特征元素一致特征值的SDK,即应用软件中所接入的SDK确定为应用软件的待检测SDK,以便对其进行检测。
步骤S20,读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;
进一步地,SDK包括头文件和代码主体,头文件用于对代码主体中所使用的宏、结构体、函数进行定义和声明,说明SDK中所开放的接口;代码主体用于实现SDK功能。在确定应用软件的各待检测SDK之后,读取此各待检测SDK的头文件,并根据头文件中所包括的信息生成与各待检测SDK对应的伪SDK。此伪SDK仅具有待检测SDK的头文件内容,而不包括其代码主体部分,生成时通过预设的基础脚本程序进行。此预设的基础脚本程序为预先设置用于生成头文件的代码,其提供生成头文件的基础框架,此基础框架为各个SDK头文件所共同具有的内容,对于各个SDK的特征信息,以变量的形式嵌入在基础框架中。当读取到各待检测SDK头文件时,将头文件中表征待检测SDK特征的信息输入到基础框架中,替换其中相应的变量,所得到的基础框架为用于生成与待检测SDK相同头文件的代码。将此生成的具有与待检测SDK相同头文件,但不具有代码主体的SDK作为与待检测SDK对应的伪SDK。如某待检测SDK用于实现A接口功能,而实现A接口功能需要在此SDK的头文件中对函数a进行声明,以通过待检测SDK中的代码主体对函数a进行调用实现A接口功能。从而通过读取待检测SDK头文件中的函数a,使用预设的基础脚本程序即可生成包含函数a的头文件,但不包含对函数a进行调用的代码主体的伪SDK。因所生成的伪SDK包括待检测SDK中对接口进行声明的头文件,从应用程序调用的角度来说,此伪SDK和待检测SDK的功能一致;但因伪SDK中没有涉及到实现接口功能的代码主体,其不能真正实现待检测SDK所具有的功能功能。
步骤S30,将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
更进一步地,在生成与各待检测SDK所对应的伪SDK后,通过伪SDK对各待检测SDK进行检测,且对各待检测SDK采用逐一检测的机制。每次针对一个待检测SDK进行检测,将此待检测SDK作为各个待检测SDK中的目标待检测SDK,并用与此目标待检测SDK对应的伪SDK对其进行替换操作,且每替换一次进行一次应用软件功能是否正常的检测。即将各待检测SDK中的目标待检测SDK替换为其对应的伪SDK,并对将目标待检测SDK替换为对应伪SDK后应用软件的功能进行检测,以判断应用软件的功能是否恢复正常。获取此替换操作后对应用软件功能检测的检测结果,以根据检测结果确定经过替换后应用软件的功能是否恢复正常。根据此应用软件是否恢复正常的检测结果,可确定替换的目标待检测SDK与其他尚未替换的待检测SDK的兼容性。若恢复正常则说明应用软件的功能异常由替换的目标待检测SDK的兼容性引起,若未恢复正常则说明不是由替换的目标待检测SDK的兼容性引起。具体地,根据检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤包括:
步骤S31,当所述检测结果为应用软件功能正常时,则判定所述待检测SDK的目标待检测SDK与其他待检测SDK不兼容,将所述待检测SDK中的目标待检测SDK所具有的特征值添加到提示信息中输出显示;
当将目标待检测SDK替换为伪SDK后,应用软件的功能恢复正常,则说明应用软件的功能异常由替换的目标待检测SDK的兼容性引起,即替换的目标待检测SDK与其他尚未替换的待检测SDK之间存在不兼容,而导致应用软件的功能异常。将此当前替换的目标待检测SDK所具有的特征值添加到提示信息中,并将提示信息输出显示,以便检测人员根据提示信息中的特征值快速确定引起应用软件功能异常的待检测SDK。
步骤S32,当所述检测结果为应用软件功能异常时,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
而当将目标待检测SDK替换为伪SDK后,应用软件的功能仍然没有恢复,则说明应用软件的功能异常不是由当前替换的目标待检测SDK的兼容性引起,即当前替换的目标待检测SDK与其他尚未替换的待检测SDK之间兼容。需要检测其他待检测SDK的兼容性,获取下一项待检测SDK作为待检测SDK中新的目标待检测SDK,并将此新的目标待检测SDK替换为与其对应的伪SDK,以判断此新的目标待检测SDK与其他待检测SDK的兼容性,其中下一项待检测SDK可对各待检测SDK进行随机选取,也可在对各待检测SDK进行排序后,按照排序顺序进行选取。如应用软件包括p1、p2和p3三项待检测SDK,与p1、p2和p3所对应的伪SDK分别为q1、q2和q3,替换时先用q1替换p1,使应用软件的待检测SDK为q1、p2和p3,检测此时应用软件的功能是否恢复正常,若恢复正常则说明目标待检测SDKp1与p1、p2之间存在不兼容的问题;若未恢复正常则用q2替换p2,使应用软件的待检测SDK为p1、q2和p3,检测此时应用软件的功能是否恢复正常,若恢复正常则说明目标待检测SDKp2与p1、p3之间存在不兼容的问题;若未恢复正常则进一步用q3替换p3,使应用软件的待检测SDK为p1、p2和q3,检测此时应用软件的功能是否恢复正常,若恢复正常则说明目标待检测SDKp3与p1、p2之间存在不兼容的问题;若未恢复正常则说明目标待检测SDKp1、p2和p3之间不存在兼容性问题。通过逐一替换,确定各个待检测SDK之间的兼容性,使应用软件中SDK兼容性检测更为准确简便。
本实施例的SDK兼容性检测方法,当应用软件出现功能异常时,读取应用软件的配置文件,根据配置文件中的信息确定应用软件的特征元素,将特征元素和各SDK的特征值对比,将具有与特征元素一致特征值的SDK确定为应用软件的待检测SDK;读取各待检测SDK的头文件,并根据各头文件中的信息生成与各待检测SDK对应的伪SDK;将各待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据检测结果各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。本方案通过生成与应用软件中待检测SDK对应的伪SDK,使用伪SDK替换原有应用软件中各待检测SDK的目标待检测SDK,并获取替换后对应用软件功能进行检测的检测结果;通过应用软件功能检测的检测结果来判定各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性,避免逐个删除SDK及相应的业务代码,操作简单方便。
进一步地,在本申请SDK兼容性检测方法另一实施例中,所述当检测结果为应用软件功能异常,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤包括:
步骤S321,当所述检测结果为应用软件功能异常时,根据所述功能异常所对应的结果日志文件判断所述功能异常的类型是否发生变化;
可理解地,在将目标待检测SDK替换为伪SDK后,应用软件的功能没有恢复,应用软件仍然功能异常时,此功能异常可能与目标待检测SDK替换之前的功能异常不一样。如替换之前应用软件的功能m1异常,而替换之后应用软件的功能m2异常,虽然经替换操作,应用软件的功能异常没有恢复,但功能异常的类型发生变化。由此可说明,当前替换的目标待检测SDK对应用软件的功能异常产生影响。为了确定当前替换的目标待检测SDK是否对应用软件的功能异常产生影响,本实施在应用软件功能仍然异常时,根据功能异常所对应的结果日志文件判断功能异常的类型是否发生变化。日志文件为对应用软件在运行过程中所发生事件进行记录的文件,对于应用软件的功能异常相应的也会进行记录,记录的内容包括异常的时间,异常的进程,异常的参数等信息。本实施例中的结果日志文件为在对目标待检测SDK进行替换操作后,检测应用软件仍然异常而生成的日志文件,读取此结果日志文件,根据其中所体现的功能异常信息与进行目标待检测SDK替换操作之前的功能异常信息进行对比,判断两者是否一致来确定功能异常的类型是否发生变化,以确定目标待检测SDK是否对应用软件的功能异常产生影响。
步骤S322,若所述功能异常的类型发生变化,则将所述待检测SDK中的目标待检测SDK设定为待确认SDK;
如果经结果日志文件中的信息确定功能异常的类型发生变化,则说明目标待检测SDK对应用软件的功能异常产生影响。如在包括n1、n2、n3和n4四个待检测SDK功能的应用软件中,其中n1与n3不兼容,n2与n3、n4不兼容,由n1和n2所引起的不兼容共同导致应用软件功能异常,当将n1替换后,应用软件的功能仍然异常,但异常的类型发生变化,即说明当前替换的n1对应用软件的功能异常产生影响,将其设定为待确认SDK。在将当前替换的目标待检测SDK设定为待确认SDK后,还需要向检测人员输出提示信息,以便检测人员对此待确认SDK进一步检测,确认其是否为影响应用软件功能异常。
步骤S323,若所述功能异常的类型未发生变化,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
而当经结果日志文件中的信息确定功能异常的类型未发生变化,则说明目标待检测SDK不是引起应用软件功能异常的原因,获取下一项待检测SDK作为待检测SDK中新的目标待检测SDK,并将此新的目标待检测SDK替换为与其对应的伪SDK,以判断此新的目标待检测SDK与其他待检测SDK的兼容性。
进一步地,在本申请SDK兼容性检测方法第一实施例的基础上,提出本申请SDK兼容性检测方法第二实施例,在第二实施例中,所述将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK的步骤包括:
步骤S11,将具有与特征元素一致特征值的SDK确定为所述应用软件的初始待检测SDK,并获取出现功能异常应用软件所生成的异常日志文件;
可理解地,因应用软件的不同功能与多个不同的SDK相关,当应用软件出现某一功能异常时,引起异常的原因也应该与此功能相关的SDK有关,而与其他SDK的关联性较弱。从而在检测SDK兼容性导致的应用软件功能异常时,可针对应用功能异常的类型,将与此类型相关的待检测SDK进行首要检测,以提高检测的效率。将具有与特征元素一致特征值的SDK确定为应用软件的初始待检测SDK,即将应用软件所接入的所有SDK设为应用软件的初始待检测SDK,需要从此所有的初始待检测SDK中确定与应用软件功能异常相关性较强的待检测SDK。进一步地,获取出现功能异常应用软件所生成的异常日志文件,此异常日志文件中记录有待检测SDK替换之前,应用软件出现功能异常的事件信息,包括异常进程、异常线程、异常参数等,以便根据此异常日志文件中的各事件信息确定与功能异常相关的待检测SDK。
步骤S12,根据所述异常日志文件中的信息确定所述应用软件所出现异常功能的类型,并根据所述异常功能类型与SDK对应关系,从所述初始待检测SDK中确定待检测SDK。
进一步地,在获取出现功能异常应用软件所生成的日常日志文件后,根据此异常日志文件中所体现的功能异常信息确定应用软件所出现异常功能的类型,如应用软件某一功能Z,而此功能与线程k相关,当应用软件出现功能异常,且异常日志文件的信息中包括的异常线程中涉及k时,则可确定此异常功能的类型为Z。因应用软件中各种功能与多个SDK相关,从而在确定异常功能的类型后,根据异常功能类型与SDK对应关系,即与功能相关的多个SDK,从初步待检测SDK中确定待检测SDK。如初始待检测SDK包括f1、f2、f3、f4和f5,对于功能Z,与其相关的SDK包括f2、f3和f4,当功能Z出现异常时,根据异常功能Z与f2、f3和f4的对应关系,从初始待检测SDKf1、f2、f3、f4和f5中确定待检测SDKf2、f3和f4,以对待检测SDKf2、f3和f4进行首要检测,提高检测效率。
进一步地,请参照图2,在本申请SDK兼容性检测方法第二实施例的基础上,提出本申请SDK兼容性检测方法第三实施例,在第三实施例中,所述根据检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤之后包括:
步骤S40,在所述检测结果为应用软件功能异常后,判断所述待检测SDK是否均进行兼容性检测,若所述待检测SDK均进行兼容性检测,则调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测。
可理解地,在对从初始待检测SDK中所确定的待检测SDK进行检测后,可能待检测SDK不存在不兼容的问题,即将各待检测SDK逐一替换为与待检测SDK对应的伪SDK后,应用软件功能仍然异常,此时则需要对初始待检测SDK中的其他待检测SDK进行检测。在对其他待检测SDK进行检测之前需要确保待检测SDK均检测完成,对于经过检测的待检测SDK分配检测完成标识符,在检测结果仍然为应用软件功能异常后,判断各个待检测SDK是否均携带有检测完成标识符,即判断所有待检测SDK均进行兼容性检测。当所有待检测SDK均携带有检测完成标识符,待检测SDK均进行兼容性检测,则调用初始待检测SDK中除待检测SDK之外的其他待检测SDK进行兼容性检测,以确定是否由其他待检测SDK的不兼容性而导致应用软件的功能异常。在对其他待检测SDK进行兼容性检测后,也可能存在其他待检测SDK也不存在不兼容的问题,即说明应用软件的功能异常不是由其对接的SDK之间的兼容性引起,需要输出兼容性正常的信息。具体地,在调用初始待检测SDK中除待检测SDK之外的其他待检测SDK进行兼容性检测的步骤之后包括:
步骤S50,判断所述其他待检测SDK是否均进行兼容性检测,若所述其他待检测SDK均进行兼容性检测,则输出应用软件中SDK兼容性正常的信息。
进一步地,在调用其他待检测SDK进行兼容性检测,将各其他待检测SDK逐一替换为与其他待检测SDK对应的伪SDK后,若应用软件的功能仍然不正常,则判断其他待检测SDK是否均进行兼容性检测,即此其他待检测SDK均携带有检测完成标识符。当均携带有检测完成标识符,其他待检测SDK均进行兼容性检测时,则说明应用软件的功能异常不是其对接的SDK之间的兼容性引起,输出应用软件中SDK兼容性正常的信息,表征应用软件中各SDK之间的兼容性良好。
进一步地,在本申请SDK兼容性检测方法第一、第二或第三实施例的基础上,提出本申请SDK兼容性检测方法第四实施例,在第四实施例中,所述读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK的步骤包括:
步骤S21,根据SDK与预设标识符对照表,确定与所述待检测SDK对应的目标预设标识符,并根据所述目标预设标识符判断是否存在与所述待检测SDK对应的伪SDK;
可理解地,因移动终端中安装有多个应用软件,各个应用软件均可能出现功能异常,而不同应用软件之间可能使用同样的SDK。对于具有同样SDK的应用软件,在先出现功能异常的应用软件会针对此SDK生成包含头文件的伪SDK,在后出现功能异常的应用软件同样也会针对此SDK生成包含头文件的伪SDK,而出现两个具有同样头文件的伪SDK,生成伪SDK的工作重复,浪费***资源且降低检测效率。为了避免重复生成伪SDK,设置有SDK与预设标识符对照表,用不同的预设标识符表征不同的SDK,对照表中预设标识符与SDK具有一一对应性。在确定应用软件中的待检测SDK后,根据此SDK与预设标识符对照表,确定与待检测SDK对应的目标预设标识符,并根据目标预设标识符中是否存在与待检测SDK对应的伪SDK。如对照表中SDK
S1与预设标识符e1对应,S2与预设标识符e2对应,当待检测SDK为S1时则其对应的目标预设标识符为e1。对于其他应用软件在先所出现的功能异常,均会生成伪SDK,此伪SDK携带有其对应待检测SDK所具有的预设标识符。从而对于当前的待检测SDK,根据其目标预设标识符判断是否已经存在与此当前待检测SDK对应的伪SDK,即判断在先出现功能异常的应用软件是否已经生成与当前待检测SDK对应的伪SDK。
步骤S22,当存在与所述待检测SDK对应的伪SDK时,则调用所述对应的伪SDK;
当根据目标预设标识符确定存在与待检测SDK对应的伪SDK时,则说明在先出现功能异常的应用软件也具有此待检测SDK,且针对此待检测SDK生成了包含头文件的伪SDK,从而调用此对应的伪文件,进行替换检测,避免再次针对待检测SDK生成伪文件。
步骤S23,当不存在与所述待检测SDK对应的为SDK时,则读取所述待检测SDK的头文件,并根据所述头文件中的信息以及所述目标预设标识符生成与所述待检测SDK对应的伪SDK。
当根据目标预设标识确定不存在与待检测SDK对应的伪SDK时,则说明在先出现功能异常的应用软件不具有此待检测SDK,没有针对此待检测SDK生成包含头文件的伪SDK,从而读取待检测SDK的头文件,根据头文件中的信息以及目标预设标识符生成与待检测SDK对应的伪SDK。通过目标预设标识符标识此伪SDK,便于判断后续出现的功能异常对应的待检测SDK是否存在伪SDK。
此外,请参照图3,本申请提供一种SDK兼容性检测装置,在本申请SDK兼容性检测装置第一实施例中,所述SDK兼容性检测装置包括:
确定模块10,用于当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;
读取模块20,用于读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与所述各待检测SDK对应的伪SDK;
检测模块30,用于将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
本实施例的SDK兼容性检测装置,当应用软件出现功能异常时,确定模块10读取应用软件的配置文件,根据配置文件中的信息确定应用软件的特征元素,将特征元素和各SDK的特征值对比,将具有与特征元素一致特征值的SDK确定为应用软件的待检测SDK;读取模块20读取各待检测SDK的头文件,并根据各头文件中的信息生成与各待检测SDK对应的伪SDK;检测模块30将各待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据检测结果各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。本方案通过生成与应用软件中待检测SDK对应的伪SDK,使用伪SDK替换原有应用软件中各待检测SDK的目标待检测SDK,并获取替换后对应用软件功能进行检测的检测结果;通过应用软件功能检测的检测结果来判定各待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性,避免逐个删除SDK及相应的业务代码,操作简单方便。
其中,上述SDK兼容性检测装置的各虚拟功能模块存储于图4所示SDK兼容性检测设备的存储器1005中,处理器1001执行SDK兼容性检测程序时,实现图3所示实施例中各个模块的功能。
需要说明的是,本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成,也可以通过程序来指令相关的硬件完成,所述的程序可以存储于一种计算机可读存储介质中,上述提到的存储介质可以是只读存储器,磁盘或光盘等。
参照图4,图4是本申请实施例方法涉及的硬件运行环境的设备结构示意图。
本申请实施例SDK兼容性检测设备可以是PC( personal computer,个人计算机
),也可以是智能手机、平板电脑、电子书阅读器、便携计算机等终端设备。
如图4所示,该SDK兼容性检测设备可以包括:处理器1001,例如CPU(Central Processing
Unit,中央处理器),存储器1005,通信总线1002。其中,通信总线1002用于实现处理器1001和存储器1005之间的连接通信。存储器1005可以是高速RAM(random
access memory,随机存取存储器),也可以是稳定的存储器(non-volatile
memory),例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地,该SDK兼容性检测设备还可以包括用户接口、网络接口、摄像头、RF(Radio
Frequency,射频)电路,传感器、音频电路、WiFi(Wireless
Fidelity,无线宽带)模块等等。用户接口可以包括显示屏(Display)、输入单元比如键盘(Keyboard),可选用户接口还可以包括标准的有线接口、无线接口。网络接口可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。
本领域技术人员可以理解,图4中示出的SDK兼容性检测设备结构并不构成对SDK兼容性检测设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
如图4所示,作为一种计算机存储介质的存储器1005中可以包括操作***、网络通信模块以及SDK兼容性检测程序。操作***是管理和控制SDK兼容性检测设备硬件和软件资源的程序,支持SDK兼容性检测程序以及其它软件和/或程序的运行。网络通信模块用于实现存储器1005内部各组件之间的通信,以及与SDK兼容性检测设备中其它硬件和软件之间通信。
在图4所示的SDK兼容性检测设备中,处理器1001用于执行存储器1005中存储的SDK兼容性检测程序,实现上述SDK兼容性检测方法各实施例中的步骤。
本申请提供了一种可读存储介质,所述可读存储介质存储有一个或者一个以上程序,所述一个或者一个以上程序还可被一个或者一个以上的处理器执行以用于实现上述SDK兼容性检测方法各实施例中的步骤。
还需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
以上所述仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是在本申请的构思下,利用本申请说明书及附图内容所作的等效结构变换,或直接/间接运用在其他相关的技术领域均包括在本申请的专利保护范围内。
Claims (20)
- 一种SDK兼容性检测方法,其特征在于,所述SDK兼容性检测方法包括以下步骤:当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各软件开发工具包SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
- 如权利要求1所述的SDK兼容性检测方法,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤包括:当所述检测结果为应用软件功能正常时,判定所述待检测SDK中的目标待检测SDK与其他待检测SDK不兼容,将所述待检测SDK中的目标待检测SDK所具有的特征值添加到提示信息中输出显示;当所述检测结果为应用软件功能异常时,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求2所述的SDK兼容性检测方法,其特征在于,所述当所述检测结果为应用软件功能异常,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤包括:当所述检测结果为应用软件功能异常时,根据所述功能异常所对应的结果日志文件判断所述功能异常的类型是否发生变化;若所述功能异常的类型发生变化,则将所述待检测SDK中的目标待检测SDK设定为待确认SDK;若所述功能异常的类型未发生变化,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求1所述的SDK兼容性检测方法,其特征在于,所述将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK的步骤包括:将具有与特征元素一致特征值的SDK确定为所述应用软件的初始待检测SDK,并获取出现功能异常应用软件所生成的异常日志文件;根据所述异常日志文件中的信息确定所述应用软件所出现异常功能的类型,并根据所述异常功能类型与SDK对应关系,从所述初始待检测SDK中确定待检测SDK。
- 如权利要求4所述的SDK兼容性检测方法,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤之后包括:在所述检测结果为应用软件功能异常后,判断所述待检测SDK是否均进行兼容性检测,若所述待检测SDK均进行兼容性检测,则调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测。
- 如权利要求5所述的SDK兼容性检测方法,其特征在于,所述调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测的步骤之后包括:判断所述其他待检测SDK是否均进行兼容性检测,若所述其他待检测SDK均进行兼容性检测,则输出应用软件中SDK兼容性正常的信息。
- 如权利要求1所述的SDK兼容性检测方法,其特征在于,所述读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK的步骤包括:根据SDK与预设标识符对照表,确定与所述待检测SDK对应的目标预设标识符,并根据所述目标预设标识符判断是否存在与所述待检测SDK对应的伪SDK;当存在与所述待检测SDK对应的伪SDK时,则调用所述对应的伪SDK;当不存在与所述待检测SDK对应的为SDK时,则读取所述待检测SDK的头文件,并根据所述头文件中的信息以及所述目标预设标识符生成与所述待检测SDK对应的伪SDK。
- 一种SDK兼容性检测装置,其特征在于,所述SDK兼容性检测装置包括:确定模块,用于当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定应用软件的特征元素,将所述特征元素和各SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;读取模块,用于读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;检测模块,用于将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
- 一种SDK兼容性检测设备,其特征在于,所述SDK兼容性检测设备包括:存储器、处理器、通信总线以及存储在所述存储器上的SDK兼容性检测程序;所述通信总线用于实现处理器和存储器之间的连接通信;所述处理器用于执行所述SDK兼容性检测程序,以实现以下步骤:当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各软件开发工具包SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
- 如权利要求9所述的SDK兼容性检测设备,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤包括:当所述检测结果为应用软件功能正常时,判定所述待检测SDK中的目标待检测SDK与其他待检测SDK不兼容,将所述待检测SDK中的目标待检测SDK所具有的特征值添加到提示信息中输出显示;当所述检测结果为应用软件功能异常时,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求10所述的SDK兼容性检测设备,其特征在于,所述当所述检测结果为应用软件功能异常,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤包括:当所述检测结果为应用软件功能异常时,根据所述功能异常所对应的结果日志文件判断所述功能异常的类型是否发生变化;若所述功能异常的类型发生变化,则将所述待检测SDK中的目标待检测SDK设定为待确认SDK;若所述功能异常的类型未发生变化,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求9所述的SDK兼容性检测设备,其特征在于,所述将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK的步骤包括:将具有与特征元素一致特征值的SDK确定为所述应用软件的初始待检测SDK,并获取出现功能异常应用软件所生成的异常日志文件;根据所述异常日志文件中的信息确定所述应用软件所出现异常功能的类型,并根据所述异常功能类型与SDK对应关系,从所述初始待检测SDK中确定待检测SDK。
- 如权利要求12所述的SDK兼容性检测设备,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤之后包括:在所述检测结果为应用软件功能异常后,判断所述待检测SDK是否均进行兼容性检测,若所述待检测SDK均进行兼容性检测,则调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测。
- 如权利要求13所述的SDK兼容性检测设备,其特征在于,所述调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测的步骤之后包括:判断所述其他待检测SDK是否均进行兼容性检测,若所述其他待检测SDK均进行兼容性检测,则输出应用软件中SDK兼容性正常的信息。
- 一种可读存储介质,其特征在于,所述可读存储介质上存储有SDK兼容性检测程序,所述SDK兼容性检测程序被处理器执行,以实现以下步骤:当应用软件出现功能异常时,读取所述应用软件的配置文件,根据所述配置文件中的信息确定所述应用软件的特征元素,将所述特征元素和各软件开发工具包SDK的特征值对比,并将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK;读取各所述待检测SDK的头文件,并根据各所述头文件中的信息生成与各所述待检测SDK对应的伪SDK;将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK,获取将所述目标待检测SDK替换为对应的伪SDK时应用软件功能检测的检测结果,并根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性。
- 如权利要求15所述的可读存储介质,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤包括:当所述检测结果为应用软件功能正常时,判定所述待检测SDK中的目标待检测SDK与其他待检测SDK不兼容,将所述待检测SDK中的目标待检测SDK所具有的特征值添加到提示信息中输出显示;当所述检测结果为应用软件功能异常时,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求16所述的可读存储介质,其特征在于,所述当所述检测结果为应用软件功能异常,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤包括:当所述检测结果为应用软件功能异常时,根据所述功能异常所对应的结果日志文件判断所述功能异常的类型是否发生变化;若所述功能异常的类型发生变化,则将所述待检测SDK中的目标待检测SDK设定为待确认SDK;若所述功能异常的类型未发生变化,则获取下一项待检测SDK作为待检测SDK中的目标待检测SDK,执行将各所述待检测SDK中的目标待检测SDK替换为对应的伪SDK的步骤。
- 如权利要求15所述的可读存储介质,其特征在于,所述将具有与特征元素一致特征值的SDK确定为所述应用软件的待检测SDK的步骤包括:将具有与特征元素一致特征值的SDK确定为所述应用软件的初始待检测SDK,并获取出现功能异常应用软件所生成的异常日志文件;根据所述异常日志文件中的信息确定所述应用软件所出现异常功能的类型,并根据所述异常功能类型与SDK对应关系,从所述初始待检测SDK中确定待检测SDK。
- 如权利要求18所述的可读存储介质,其特征在于,所述根据所述检测结果确定各所述待检测SDK中的目标待检测SDK与其他待检测SDK的兼容性的步骤之后包括:在所述检测结果为应用软件功能异常后,判断所述待检测SDK是否均进行兼容性检测,若所述待检测SDK均进行兼容性检测,则调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测。
- 如权利要求19所述的可读存储介质,其特征在于,所述调用所述初始待检测SDK中除所述待检测SDK之外的其他待检测SDK进行兼容性检测的步骤之后包括:判断所述其他待检测SDK是否均进行兼容性检测,若所述其他待检测SDK均进行兼容性检测,则输出应用软件中SDK兼容性正常的信息。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810364741.6 | 2018-04-20 | ||
CN201810364741.6A CN108563578B (zh) | 2018-04-20 | 2018-04-20 | Sdk兼容性检测方法、装置、设备及可读存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019200721A1 true WO2019200721A1 (zh) | 2019-10-24 |
Family
ID=63536337
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/094105 WO2019200721A1 (zh) | 2018-04-20 | 2018-07-02 | Sdk 兼容性检测方法、装置、设备及可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN108563578B (zh) |
WO (1) | WO2019200721A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116860597A (zh) * | 2023-05-11 | 2023-10-10 | 钉钉(中国)信息技术有限公司 | 应用程序的检测方法、计算设备及计算机存储介质 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112328824B (zh) * | 2020-07-21 | 2024-06-18 | 北京沃东天骏信息技术有限公司 | 图片检测方法及其***、计算机***和计算机可读介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103440337A (zh) * | 2013-09-09 | 2013-12-11 | 百度在线网络技术(北京)有限公司 | Api兼容性扫描方法和api兼容性扫描装置 |
CN104932973A (zh) * | 2014-03-21 | 2015-09-23 | 腾讯科技(深圳)有限公司 | 一种版本兼容测试方法和装置 |
CN106506851A (zh) * | 2016-11-28 | 2017-03-15 | 努比亚技术有限公司 | 移动终端的数据统计适配方法与装置 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102622211B (zh) * | 2011-01-27 | 2016-05-25 | 腾讯科技(深圳)有限公司 | 一种应用程序开发的方法和装置 |
US9218269B2 (en) * | 2012-09-07 | 2015-12-22 | Red Hat Israel, Ltd. | Testing multiple target platforms |
CN106155900B (zh) * | 2015-04-17 | 2020-12-04 | 腾讯科技(深圳)有限公司 | 一种代码测试监测方法、装置及设备 |
CN106294108B (zh) * | 2015-05-27 | 2020-04-28 | 腾讯科技(深圳)有限公司 | 应用程序测试方法及装置 |
US9892019B2 (en) * | 2015-10-16 | 2018-02-13 | Successfactors Inc. | Use case driven stepping component automation framework |
CN105468525A (zh) * | 2015-11-27 | 2016-04-06 | 苏州同元软控信息技术有限公司 | 基于c代码模型的构件接口单元测试方法 |
CN106951361A (zh) * | 2016-01-06 | 2017-07-14 | 联发科技(新加坡)私人有限公司 | 软件开发工具包测试方法及其装置、测试*** |
CN107122292A (zh) * | 2016-10-21 | 2017-09-01 | 北京小度信息科技有限公司 | 一种模拟服务的方法及*** |
CN106528421B (zh) * | 2016-11-09 | 2019-07-26 | 国网浙江省电力公司电力科学研究院 | 一种Android应用中SDK处理方法 |
CN106919511B (zh) * | 2017-03-10 | 2021-03-26 | 携程计算机技术(上海)有限公司 | 应用的模拟方法、模拟应用及其运作方法以及模拟*** |
CN107357728A (zh) * | 2017-07-07 | 2017-11-17 | 广东中星电子有限公司 | 测试软件的方法和电子设备 |
-
2018
- 2018-04-20 CN CN201810364741.6A patent/CN108563578B/zh active Active
- 2018-07-02 WO PCT/CN2018/094105 patent/WO2019200721A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103440337A (zh) * | 2013-09-09 | 2013-12-11 | 百度在线网络技术(北京)有限公司 | Api兼容性扫描方法和api兼容性扫描装置 |
CN104932973A (zh) * | 2014-03-21 | 2015-09-23 | 腾讯科技(深圳)有限公司 | 一种版本兼容测试方法和装置 |
CN106506851A (zh) * | 2016-11-28 | 2017-03-15 | 努比亚技术有限公司 | 移动终端的数据统计适配方法与装置 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116860597A (zh) * | 2023-05-11 | 2023-10-10 | 钉钉(中国)信息技术有限公司 | 应用程序的检测方法、计算设备及计算机存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN108563578A (zh) | 2018-09-21 |
CN108563578B (zh) | 2021-09-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015135443A1 (en) | Method and apparatus for simulating sound in virtual scenario, and terminal | |
WO2018199537A1 (en) | Electronic device and method of controlling the electronic device based on touch input | |
WO2017142293A1 (en) | Electronic device and method of application data display therefor | |
WO2018107610A1 (zh) | 业务数据处理方法、***、设备及计算机可读存储介质 | |
WO2017142256A1 (en) | Electronic device for authenticating based on biometric data and operating method thereof | |
WO2013143334A1 (zh) | 一种更新移动终端nfc固件的方法及其移动终端 | |
WO2019223070A1 (zh) | 应用测试方法、装置、设备及可读存储介质 | |
WO2019119624A1 (zh) | 基于Excel表的计算方法、装置、设备及存储介质 | |
WO2020171427A1 (ko) | 어플리케이션을 프리페치하는 전자 장치 및 방법 | |
WO2016080761A1 (en) | Method and electronic device for driving fingerprint sensor | |
WO2015156640A1 (en) | Method and device for controlling security screen in electronic device | |
WO2016027983A1 (en) | Method and electronic device for classifying contents | |
WO2020027413A1 (ko) | 팩토리 데이터 리셋 기능에 의해 제거된 어플리케이션을 복원하는 장치 및 방법 | |
WO2018098881A1 (zh) | 应用程序的访问处理方法及装置 | |
WO2019200721A1 (zh) | Sdk 兼容性检测方法、装置、设备及可读存储介质 | |
WO2019235793A1 (en) | Electronic device and method for providing information related to image to application through input unit | |
WO2018044065A1 (en) | Method for displaying time information in low power state and electronic device including the same | |
WO2019090981A1 (zh) | 保险应用***的监控方法及装置 | |
WO2020171571A1 (en) | Electronic device and method for managing database | |
WO2018188342A1 (zh) | 脚本文件生成方法、装置、设备和计算机可读存储介质 | |
EP3580752A1 (en) | Electronic device and method for controlling application thereof | |
WO2018026164A1 (en) | Method of processing touch events and electronic device adapted thereto | |
WO2017023040A1 (en) | Screen controlling method and electronic device for supporting the same | |
WO2019080401A1 (zh) | 脚本语句转换方法、装置及计算机可读存储介质 | |
WO2018034493A1 (en) | Electronic device and control method therefor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18915205 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.01.2021) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18915205 Country of ref document: EP Kind code of ref document: A1 |