WO2019200721A1 - Procédé, appareil et dispositif de détection de compatibilité sdk, et support de stockage lisible - Google Patents

Procédé, appareil et dispositif de détection de compatibilité sdk, et support de stockage lisible Download PDF

Info

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
Application number
PCT/CN2018/094105
Other languages
English (en)
Chinese (zh)
Inventor
俞伟山
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019200721A1 publication Critical patent/WO2019200721A1/fr

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

L'invention concerne un procédé, un appareil et un dispositif de détection de compatibilité SDK, et un support de stockage lisible. Le procédé comprend les étapes suivantes consistant à : lorsqu'un dysfonctionnement se produit dans un logiciel d'application, lire un fichier de configuration du logiciel d'application, déterminer un élément de caractéristique du logiciel d'application en fonction d'informations dans le fichier de configuration, et déterminer les SDK ayant une valeur de caractéristique compatible avec l'élément de caractéristique en tant que SDK à détecter du logiciel d'application ; lire un fichier d'en-tête de chaque SDK à détecter, et générer en fonction d'informations dans chaque fichier d'en-tête, un pseudo SDK correspondant à chaque SDK à détecter ; remplacer un SDK cible à détecter parmi les SDK à détecter par un pseudo SDK correspondant, acquérir un résultat de détection de détection de fonction logicielle d'application lors du remplacement du SDK cible à détecter par le pseudo SDK correspondant, et déterminer, en fonction du résultat de détection, la compatibilité du SDK cible à détecter avec les autres SDK à détecter. Mener une détection de compatibilité de SDK par remplacement d'un pseudo SDK par un SDK d'origine à détecter évite la suppression de SDK un par un, et est pratique à utiliser.
PCT/CN2018/094105 2018-04-20 2018-07-02 Procédé, appareil et dispositif de détection de compatibilité sdk, et support de stockage lisible WO2019200721A1 (fr)

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 (fr) 2019-10-24

Family

ID=63536337

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094105 WO2019200721A1 (fr) 2018-04-20 2018-07-02 Procédé, appareil et dispositif de détection de compatibilité sdk, et support de stockage lisible

Country Status (2)

Country Link
CN (1) CN108563578B (fr)
WO (1) WO2019200721A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860597A (zh) * 2023-05-11 2023-10-10 钉钉(中国)信息技术有限公司 应用程序的检测方法、计算设备及计算机存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112328824A (zh) * 2020-07-21 2021-02-05 北京沃东天骏信息技术有限公司 图片检测方法及其系统、计算机系统和计算机可读介质

Citations (3)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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 广东中星电子有限公司 测试软件的方法和电子设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860597A (zh) * 2023-05-11 2023-10-10 钉钉(中国)信息技术有限公司 应用程序的检测方法、计算设备及计算机存储介质

Also Published As

Publication number Publication date
CN108563578B (zh) 2021-09-21
CN108563578A (zh) 2018-09-21

Similar Documents

Publication Publication Date Title
WO2015135443A1 (fr) Procédé et appareil pour simuler un son dans un scénario virtuel, et terminal
WO2017142293A1 (fr) Dispositif électronique et procédé d'affichage de données d'application associé
WO2018107610A1 (fr) Procédé, système et dispositif de traitement de données de service, et support d'informations lisible par ordinateur
WO2017142256A1 (fr) Dispositif électronique d'authentification basée sur des données biométriques et procédé associé
WO2013143334A1 (fr) Procédé de mise à jour de micrologiciel nfc de terminal mobile et terminal mobile
WO2016129852A1 (fr) Procédé de régulation d'autorisation et dispositif électronique mettant en œuvre ce procédé
WO2018205545A1 (fr) Procédé de génération de données, appareil, terminal, et support d'informations lisible par ordinateur
WO2018227880A1 (fr) Procédé, appareil, et dispositif de comparaison de données, et support d'informations lisible
WO2019039872A1 (fr) Procédé et dispositif électronique pour commander l'autorisation d'un programme d'application
WO2017069489A1 (fr) Procédé d'encodage sélectif et dispositif électronique l'utilisant
WO2019119624A1 (fr) Procédé et appareil de calcul basé sur un tableau excel, dispositif et support de stockage
WO2015156640A1 (fr) Procédé et dispositif de commande d'un écran de sécurité dans un dispositif électronique
WO2016027983A1 (fr) Procédé et dispositif électronique de classement de contenus
WO2020171427A1 (fr) Dispositif électronique à préchargement d'application et procédé associé
WO2016064156A1 (fr) Procédé de commande de la sécurité et dispositif électronique associé
WO2019200721A1 (fr) Procédé, appareil et dispositif de détection de compatibilité sdk, et support de stockage lisible
WO2019235793A1 (fr) Dispositif électronique et procédé permettant de fournir des informations relatives à une application au moyen d'une unité d'entrée
WO2017052216A1 (fr) Procédé de fourniture d'événements correspondant à des attributs tactiles et dispositif électronique associé
WO2018098881A1 (fr) Procédé et dispositif de traitement d'accès pour application
EP3221971A1 (fr) Procédé et dispositif électronique pour piloter un capteur d'empreinte digitale
WO2018164445A1 (fr) Dispositif électronique et procédé associé permettant de commander une application
WO2017092498A1 (fr) Procédé de gestion d'informations et terminal utilisateur
WO2020027413A1 (fr) Dispositif et procédé pour restaurer une application supprimée par une fonction de réinitialisation de données d'usine
WO2018044065A1 (fr) Procédé d'affichage d'informations temporelles dans un état de faible puissance et dispositif électronique correspondant
WO2019090981A1 (fr) Procédé et appareil de surveillance de système d'application d'assurance

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