WO2019200721A1

WO2019200721A1 - Sdk compatibility detection method, apparatus and device, and readable storage medium

Info

Publication number: WO2019200721A1
Application number: PCT/CN2018/094105
Authority: WO
Inventors: 俞伟山
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-04-20
Filing date: 2018-07-02
Publication date: 2019-10-24
Also published as: CN108563578B; CN108563578A

Abstract

Disclosed are an SDK compability detection method, apparatus and device, and a readable storage medium. The method comprises: when a dysfunction occurs in application software, reading a configuration file of the application software, determining a feature element of the application software according to information in the configuration file, and determining SDKs having a feature value consistent with the feature element as SDKs to be detected of the application software; reading a header file of each SDK to be detected, and generating, according to information in each header file, a pseudo SDK corresponding to each SDK to be detected; replacing a target SDK to be detected of the SDKs to be detected with a corresponding pseudo SDK, acquiring a detection result of application software function detection when replacing the target SDK to be detected with the corresponding pseudo SDK, and determining, according to the detection result, the compatibility of the target SDK to be detected with the other SDKs to be detected. Conducting SDK compatibility detection by replacing a pseudo SDK with an original SDK to be detected avoids deleting SDKs one by one, and is convenient to operate.

Description

SDK compatibility detection method, device, device and readable storage medium

The present application claims priority to Chinese Patent Application No. 201810364741.6, entitled "SDK Compatibility Test Method, Apparatus, Apparatus, and Readable Storage Medium", filed on April 20, 2018, the entire contents of which is incorporated herein by reference. It is incorporated in the application by reference.

Technical field

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.

Background technique

At present, more and more 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. At present, for the compatibility check between SDKs, it is necessary to delete the SDK and the corresponding service code one by one for detection, but the deletion may be accidentally deleted, and the operation is complicated and cumbersome.

Summary of the invention

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.

To achieve the above objective, 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;

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 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 compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.

In addition, in order to achieve the above object, 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.

In addition, to achieve the above object, 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:

Moreover, to achieve the above objects, 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:

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.

DRAWINGS

1 is a schematic flowchart of a first embodiment of an SDK compatibility detecting method according to the present application;

2 is a schematic flow chart of a second embodiment of the SDK compatibility detecting method of the present application;

3 is a schematic diagram of functional modules of a first embodiment of the SDK compatibility detecting apparatus of the present application;

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 implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

detailed description

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

The application provides an SDK compatibility detection method.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart diagram of a first embodiment of an SDK compatibility detecting method according to the present application. In this embodiment, 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. At present, 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. When the application software accesses multiple SDKs developed by different developers, SDKs with different sources may be incompatible with each other, resulting in abnormal function of the application software. When the application software is abnormal, it needs to be detected whether it is caused by incompatibility between the accessed SDKs. Specifically, 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. . For the SDK developed by the developer, 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. After reading the configuration file of the application software, according to the information in the configuration file, 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. In order to determine the compatibility of each SDK in the application software, 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;

Further, 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. After determining the to-be-detected SDKs of the application software, 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. When the SDK header file to be detected is read, the information indicating the SDK feature to be detected in the header file is input into the basic frame, and the corresponding variable is replaced, and the obtained basic frame is used to generate the same header as the SDK to be detected. The code for the file. The generated SDK having the same header file as the SDK to be detected but having no code body is used as the pseudo SDK corresponding to the SDK to be detected. For example, if the SDK to be detected is used to implement the A interface function, and the A interface function is implemented, 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. Thus, by reading the function a in the SDK header file 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. Since 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.

Further, after the pseudo SDK corresponding to each of the to-be-detected SDKs is generated, 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. Each time the detection of the SDK to be detected is performed, 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. If it is not restored, the description is not caused by the compatibility of the replacement target to be tested SDK. Specifically, 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:

In 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;

When the target to-be-detected SDK is replaced with a pseudo-SDK, 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.

In 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.

When the target to-be-detected SDK is replaced with a pseudo-SDK, 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. It is necessary to detect the compatibility of other to-be-detected SDKs, obtain the next to-be-detected SDK as the new target to-be-detected SDK in the to-be-detected SDK, and replace the new target-to-be-detected SDK with its corresponding pseudo-SDK to determine this new 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. For example, if the application software includes three items to be detected, p1, p2, and p3, 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. If it returns to normal, it indicates that there is an incompatibility between the target to be detected SDKP2 and p1 and p3; if it is not restored, then further Replace p3 with q3, so that the SDK to be tested of the application software is p1, p2, and q3, and 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 SDKP3 and p1 and p2. If it does not return to normal, there is no compatibility problem between the target to be tested SDKp1, p2 and p3. By replacing one by one, the compatibility between each SDK to be tested is determined, so that the SDK compatibility detection in the application software is more accurate and simple.

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.

Further, in another embodiment of the SDK compatibility detection method of the present application, when the detection result is that the application software function is abnormal, acquiring the next to-be-detected SDK as the target to be detected SDK in the to-be-detected SDK, and performing each The step of replacing the target to-be-detected SDK in the to-be-detected SDK with the corresponding pseudo-SDK includes:

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;

Obviously, after the target to-be-detected SDK is replaced with the pseudo-SDK, 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. For example, the function m1 of the application software is abnormal, and the function m2 of the application software is abnormal after the replacement. Although 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. In order to determine whether 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;

If 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. For example, in the application software including n1, n2, n3 and n4, the n1 and n3 are incompatible, n2 is incompatible with n3 and n4, and the incompatibility caused by n1 and n2 together causes the application software function. Abnormally, after replacing n1, 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. After the currently-replaced target to-be-detected SDK is set to 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.

In 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.

When 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.

Further, based on the first embodiment of the SDK compatibility detection method of the present application, a second embodiment of the SDK compatibility detection method of the present application is proposed. In the second embodiment, 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;

Understandably, because different functions of the application software are related to multiple different SDKs, when a certain function abnormality occurs in the 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.

Further, after obtaining the daily log file generated by the dysfunctional application software, determining the type of the abnormal function that occurs in the application software 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. When 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. Because 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. . For example, the initial to-be-detected SDK includes f1, f2, f3, f4, and f5. For function Z, the SDK associated with it includes f2, f3, and f4. When the function Z is abnormal, 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.

Further, referring to FIG. 2, on the basis of the second embodiment of the SDK compatibility detection method of the present application, a third embodiment of the SDK compatibility detection method of the present application is proposed. In the third embodiment, 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:

In 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.

It can be understood that after the detection of the to-be-detected SDK determined in the initial to-be-detected SDK, there may be no problem that the SDK to be detected is incompatible, that is, each of the to-be-detected SDKs is replaced one by one with a pseudo-SDK corresponding to the SDK to be detected. The application software function is still abnormal. In this case, the other to-be-detected SDKs in the initial to-be-detected SDK need to be detected. Before detecting the other to-be-detected SDKs, it is necessary to ensure that the detection of the to-be-detected SDK is completed, and the detection completion identifier is allocated to the detected SDK to be detected. After 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. When all the to-be-detected SDKs carry the detection completion identifier, and the SDK to be tested performs 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. After the compatibility check is performed on other to-be-detected SDKs, there may be other incompatibility problems between the SDKs to be detected, that is, the function abnormality of the application software is not caused by the compatibility between the docked SDKs, and the output compatibility is required. Sexually normal information. Specifically, after the step of calling the to-be-detected SDK other than the to-be-detected SDK for compatibility detection in calling the initial to-be-detected SDK, the method includes:

In 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.

Further, after calling the other to-be-detected SDKs for compatibility detection, and replacing each of the other to-be-detected SDKs with the pseudo-SDK corresponding to the other to-be-detected SDKs, if 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. When both the detection completion identifiers are carried and the other detected SDKs are tested for compatibility, 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.

Further, based on the first, second or third embodiment of the SDK compatibility detection method of the present application, a fourth embodiment of the SDK compatibility detection method of the present application is proposed. In the fourth embodiment, 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. ;

Understandably, due to the installation of multiple application software in the mobile terminal, each application software may have a functional abnormality, and the same SDK may be used between different application software. For applications with the same SDK, the application software with the first dysfunction will generate a pseudo-SDK containing the header file for the SDK, and the application software with the dysfunction will also generate a pseudo-SDK containing the header file for the SDK. The emergence of two pseudo-SDKs with the same header file, the duplication of the work of generating the pseudo-SDK, wasting system resources and reducing the detection efficiency. In order to avoid repeatedly generating a pseudo 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. After determining the to-be-detected SDK in the application software, determining a target preset identifier corresponding to the to-be-detected SDK according to the SDK and the preset identifier comparison table, and according to whether the target preset identifier has a corresponding to the to-be-detected SDK Pseudo SDK. Such as the SDK in the comparison table S1 corresponds to the preset identifier e1, and S2 corresponds to the preset identifier e2. When the SDK to be detected is S1, the corresponding target preset identifier is e1. For other functional exceptions that occur in other applications, 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;

When it is determined that there is a pseudo SDK corresponding to the SD to be detected according to the target preset identifier, it is indicated that the application software having the dysfunction first has the SDK to be detected, and a pseudo SDK including the header file is generated for the to-be-detected SDK. Therefore, the corresponding pseudo file is called, and the replacement detection is performed to avoid generating a pseudo file for the SDK to be detected again.

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.

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.

In addition, referring to FIG. 3, the present application provides an SDK compatibility detecting apparatus. In the first embodiment of the SDK compatibility detecting apparatus of the present application, 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.

In the SDK compatibility detecting apparatus of this embodiment, when the application software has a function abnormality, 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. Corresponding pseudo-SDK; 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.

It should be noted that those skilled in the art can understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable state. In the storage medium, the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Referring to FIG. 4, 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.

As shown in FIG. 4, 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.

Optionally, 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).

It will be understood by those skilled in the art that 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.

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.

In the SDK compatibility detecting device shown in FIG. 4, 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 steps in the various embodiments of the method of detection.

It is also to be understood that the term "comprises", "comprising", or any other variants thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a And includes other elements not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, 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.

The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the patents of the present application, and the equivalent structural transformations made by the contents of the specification and the drawings of the present application, or directly/indirectly Other related technical fields are included in the patent protection scope of the present application.

Claims

An SDK compatibility detecting method, characterized in that the SDK compatibility detecting method comprises the following steps:

When the application software is abnormal in function, reading a configuration file of the application software, determining a feature element of the application software according to the information in the configuration file, and using the feature element and the feature value of each software development kit 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;

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 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 compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.
The SDK compatibility detecting method according to claim 1, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

When the detection result is that the application software function is normal, it is determined that the target to-be-detected SDK in the to-be-detected SDK is incompatible with other to-be-detected SDKs, and the feature value of the target to-be-detected SDK in the to-be-detected SDK is added. Output the display to the prompt information;

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 a corresponding pseudo. The steps of the SDK.
The SDK compatibility detecting method according to claim 2, wherein, when the detection result is that the application software function is abnormal, acquiring the next to-be-detected SDK as the target to-be-detected SDK in the to-be-detected SDK, and executing The step of replacing the target to-be-detected SDK in each of the to-be-detected SDKs with the corresponding pseudo-SDK includes:

When the detection result is that the application software function is abnormal, determining whether the type of the function abnormality changes according to the result log file corresponding to the function abnormality;

If the type of the abnormal function changes, the target to-be-detected SDK in the to-be-detected SDK is set as the to-be-confirmed 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 pseudo-SDK. A step of.
The SDK compatibility detecting method according to claim 1, wherein the step of determining the SDK having the feature value consistent with the feature element as the SDK to be detected of the application software comprises:

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 software having the abnormal function;

And determining, according to the information in the abnormal log file, the type of the abnormal function that is generated by the application software, and determining the to-be-detected SDK from the initial to-be-detected SDK according to the abnormal function type and the SDK correspondence.
The SDK compatibility detecting method according to claim 4, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

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, and if the to-be-detected SDK performs compatibility detection, calling the initial to-be-detected SDK Detect other SDKs to be tested other than the SDK for compatibility detection.
The SDK compatibility detecting method according to claim 5, wherein the step of calling the other to-be-detected SDKs other than the to-be-detected SDK for compatibility detection in the initial to-be-detected SDK includes:

Determining whether the other to-be-detected SDKs are all performing compatibility detection. If the other to-be-detected SDKs are all performing compatibility detection, outputting information that the SDK compatibility is normal in the application software.
The SDK compatibility detecting method according to claim 1, wherein the reading a header file of each of the to-be-detected SDKs, and generating corresponding to each of the to-be-detected SDKs according to information in each of the header files The steps of the pseudo SDK include:

Determining, according to the SDK and the preset identifier comparison table, a target preset identifier corresponding to the to-be-detected SDK, and determining, according to the target preset identifier, whether there is a pseudo SDK corresponding to the to-be-detected SDK;

When there is a pseudo SDK corresponding to the to-be-detected SDK, the corresponding pseudo SDK is invoked;

When the SDK corresponding to the to-be-detected SDK does not exist, the header file of the to-be-detected SDK is read, and the to-be-detected is generated according to the information in the header file and the target preset identifier. The pseudo SDK corresponding to the SDK.
An SDK compatibility detecting apparatus, wherein the SDK compatibility detecting apparatus comprises:

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.
An SDK compatibility detecting device, characterized in that: the SDK compatibility detecting device comprises: 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:

When the application software is abnormal in function, reading a configuration file of the application software, determining a feature element of the application software according to the information in the configuration file, and using the feature element and the feature value of each software development kit 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;

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 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 compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.
The SDK compatibility testing device according to claim 9, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

When the detection result is that the application software function is normal, it is determined that the target to-be-detected SDK in the to-be-detected SDK is incompatible with other to-be-detected SDKs, and the feature value of the target to-be-detected SDK in the to-be-detected SDK is added. Output the display to the prompt information;

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 a corresponding pseudo. The steps of the SDK.
The SDK compatibility detecting device according to claim 10, wherein, when the detection result is that the application software function is abnormal, acquiring the next to-be-detected SDK as the target to-be-detected SDK in the to-be-detected SDK, and executing The step of replacing the target to-be-detected SDK in each of the to-be-detected SDKs with the corresponding pseudo-SDK includes:

When the detection result is that the application software function is abnormal, determining whether the type of the function abnormality changes according to the result log file corresponding to the function abnormality;

If the type of the abnormal function changes, the target to-be-detected SDK in the to-be-detected SDK is set as the to-be-confirmed 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 pseudo-SDK. A step of.
The SDK compatibility detecting device according to claim 9, wherein the step of determining the SDK having the feature value consistent with the feature element as the SDK to be detected of the application software comprises:

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 software having the abnormal function;

And determining, according to the information in the abnormal log file, the type of the abnormal function that is generated by the application software, and determining the to-be-detected SDK from the initial to-be-detected SDK according to the abnormal function type and the SDK correspondence.
The SDK compatibility detecting device according to claim 12, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

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, and if the to-be-detected SDK performs compatibility detection, calling the initial to-be-detected SDK Detect other SDKs to be tested other than the SDK for compatibility detection.
The SDK compatibility detecting device according to claim 13, wherein the step of calling the other to-be-detected SDKs other than the to-be-detected SDK for compatibility detection in the initial to-be-detected SDK includes:

Determining whether the other to-be-detected SDKs are all performing compatibility detection. If the other to-be-detected SDKs are all performing compatibility detection, outputting information that the SDK compatibility is normal in the application software.
A readable storage medium, characterized in that an SDK compatibility detection program is stored on the readable storage medium, and the SDK compatibility detection program is executed by a processor to implement the following steps:

When the application software is abnormal in function, reading a configuration file of the application software, determining a feature element of the application software according to the information in the configuration file, and using the feature element and the feature value of each software development kit 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;

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 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 compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs.
The readable storage medium according to claim 15, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

When the detection result is that the application software function is normal, it is determined that the target to-be-detected SDK in the to-be-detected SDK is incompatible with other to-be-detected SDKs, and the feature value of the target to-be-detected SDK in the to-be-detected SDK is added. Output the display to the prompt information;

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 a corresponding pseudo. The steps of the SDK.
The readable storage medium according to claim 16, wherein when the detection result is that the application software function is abnormal, acquiring the next to-be-detected SDK as the target to-be-detected SDK in the to-be-detected SDK, and executing The step of replacing the target to-be-detected SDK in each of the to-be-detected SDKs with the corresponding pseudo-SDK includes:

When the detection result is that the application software function is abnormal, determining whether the type of the function abnormality changes according to the result log file corresponding to the function abnormality;

If the type of the abnormal function changes, the target to-be-detected SDK in the to-be-detected SDK is set as the to-be-confirmed 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 pseudo-SDK. A step of.
The readable storage medium according to claim 15, wherein the step of determining an SDK having a feature value consistent with the feature element as the SDK to be detected of the application software comprises:

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 software having the abnormal function;

And determining, according to the information in the abnormal log file, the type of the abnormal function that is generated by the application software, and determining the to-be-detected SDK from the initial to-be-detected SDK according to the abnormal function type and the SDK correspondence.
The readable storage medium according to claim 18, wherein the step of determining, according to the detection result, the compatibility of the target to-be-detected SDK in each of the to-be-detected SDKs with other to-be-detected SDKs comprises:

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, and if the to-be-detected SDK performs compatibility detection, calling the initial to-be-detected SDK Detect other SDKs to be tested other than the SDK for compatibility detection.
The readable storage medium according to claim 19, wherein the step of invoking compatibility detection of the other to-be-detected SDKs other than the to-be-detected SDK in the initial to-be-detected SDK comprises:

Determining whether the other to-be-detected SDKs are all performing compatibility detection. If the other to-be-detected SDKs are all performing compatibility detection, outputting information that the SDK compatibility is normal in the application software.