CN116069575A

CN116069575A - Adapter testing method and device, electronic equipment and storage medium

Info

Publication number: CN116069575A
Application number: CN202211668091.7A
Authority: CN
Inventors: 请求不公布姓名
Original assignee: Moore Threads Technology Co Ltd
Current assignee: Moore Threads Technology Co Ltd
Priority date: 2022-12-23
Filing date: 2022-12-23
Publication date: 2023-05-05
Anticipated expiration: 2042-12-23
Also published as: CN116069575B

Abstract

The disclosure relates to a testing method and device of an adapter, electronic equipment and a storage medium, wherein the testing method of the adapter comprises the following steps: acquiring a test case; converting the test case into a hardware case; and testing the adapter to be detected according to the hardware use case, and obtaining a test result. The embodiment of the disclosure can acquire the test case of the application program interface level before the hardware interface level, and the test case is closer to the application program, so that the developer can obtain the test data highly adapted to the adapter to be detected even if the developer does not know the hardware interface used in the hardware architecture. In addition, the test case is more close to the application program, so that a developer can change the test case conveniently, and the test for the adapter to be detected can be conducted flexibly.

Description

Adapter testing method and device, electronic equipment and storage medium

Technical Field

The disclosure relates to the technical field of information processing, and in particular relates to a testing method and device of an adapter, electronic equipment and a storage medium.

Background

With the continued development of the computer industry, the performance requirements of adapters (e.g., network adapters, display adapters, etc.) have increased. And how the adapter tests when performing version iteration, whether the direct relation adapter can adapt to the actual use environment of a user or not is also directly related to the subsequent maintenance cost of the adapter. Therefore, how to test the adapter better is a technical problem that needs to be solved by the developer.

Disclosure of Invention

The disclosure provides a test technical scheme of an adapter.

According to an aspect of the present disclosure, there is provided a test method of an adapter, the test method including: acquiring a test case; wherein the test case is used to represent the load of the application program interface hierarchy processed by the adapter; converting the test case into a hardware case; wherein the hardware use case is used for representing the load of the hardware interface level of the adapter; and testing the adapter to be detected according to the hardware use case, and obtaining a test result.

In one possible implementation manner, before the obtaining the test case, the method includes: acquiring a universal application program interface sequence; the universal application program interface sequence is used for representing an application program interface sequence which can be shared by different application programs; converting the universal application program interface sequence into an application program interface sequence adapted to the adapter to be detected; and determining the test case according to the application program interface sequence of the adapter to be detected.

In one possible implementation manner, the acquiring a generic application program interface sequence includes: acquiring at least one of at least one preset application program interface sequence and input application program interface sequence corresponding to an adapter before the adapter to be detected in version information, and taking the version information as the universal application program interface sequence; wherein different preset application program interface sequences are used for representing different functions of the adapter to be detected.

In a possible implementation manner, the determining the test case according to the application program interface sequence of the adapter to be detected includes any one of the following: taking the application program interface sequence of the adapter to be detected as the test case; and responding to input completion information of the input application program interface sequence, and taking the input application program interface sequence and the application program interface sequence adapted to the adapter to be detected as the test case.

In one possible implementation manner, the test case includes: the first test case and/or the second test case; the first test case is used for representing the load of an application program interface layer corresponding to the adapter with version information in front of the adapter to be detected; the second test case is used for representing the load of an application program interface level, of which the version information is the same as that of the adapter to be detected or the adapter behind the adapter to be detected; the converting the test case into a hardware case includes: converting the first test case into a first hardware case and/or converting the second test case into a second hardware case; the first hardware use case is used for representing the load of the hardware interface level of the adapter with version information in front of the adapter to be detected; the second hardware use case is used for representing the load of the hardware interface level of the adapter with version information identical to or behind the adapter to be detected.

In a possible implementation manner, the adapter to be tested is tested according to the hardware use case, and the test is obtained

Test results, including at least one of: according to the first hardware use case, testing the adapter to be detected to obtain a first test 5 test result which is used as a part of the test result; wherein the first test result is used for representing the information aiming at the version

Testing results of loads corresponding to the adapters before the adapters to be detected are included; according to the second hardware use case, testing the adapter to be detected to obtain a second test result which is used as a part of the test result; the second test result is used for representing a test result aiming at a load corresponding to the adapter with version information identical to or behind the adapter to be detected.

0 in one possible implementation, the adapter to be tested is tested according to the hardware use case, and the test is obtained

The test results include: inputting the first hardware use case to an adapter corresponding to the version information of the first hardware use case, and obtaining a first test result of the adapter corresponding to the version information; and under the condition that a first test result of the adapter corresponding to the version information is higher than a preset threshold value, testing the adapter to be detected according to the first hardware use case and the second hardware use case to obtain a test result.

According to an aspect of the present disclosure, there is provided a test apparatus of an adapter, the test apparatus including: test use

The case acquisition module is used for acquiring test cases; wherein the test case is used to represent the load of the application program interface hierarchy processed by the adapter; the hardware use case conversion module is used for converting the test use case into a hardware use case; wherein, the liquid crystal display device comprises a liquid crystal display device,

the hardware use case is used for representing the load of the hardware interface level of the adapter; and the test result generation module is used for testing the adapter to be detected according to the hardware use case and obtaining a test result.

0 according to an aspect of the present disclosure, there is provided an electronic device including: a processor; for storing processor executables

A memory of row instructions; wherein the processor is configured to invoke the instructions stored by the memory to perform the test method described above.

According to an aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the above-described test method.

In the embodiment of the disclosure, a test case may be obtained, and then the test case is converted into a hardware case, and finally

And testing the adapter to be detected according to the hardware use case, and obtaining a test result. Embodiments of the present disclosure may obtain a test case at the application interface level before the hardware interface level, which, because it is more proximate to the application, may be highly adapted to be used by a developer even without knowing the hardware interface used in the hardware architecture

Test data of the adapter is detected. In addition, the test case is more similar to the application program, so that a developer can change the test case by 0 conveniently, and the test for the adapter to be detected can be flexibly carried out.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the technical aspects of the disclosure.

Fig. 1 shows a flowchart of a method for testing an adapter according to an embodiment of the present disclosure.

Fig. 2 shows a flowchart of a method for testing an adapter according to an embodiment of the present disclosure.

Fig. 3 shows a block diagram of a test apparatus for an adapter provided in accordance with an embodiment of the present disclosure.

Fig. 4 shows a block diagram of an electronic device provided in accordance with an embodiment of the present disclosure.

Detailed Description

Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

Furthermore, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.

In the related art, development of an adapter generally includes: driver development and hardware architecture development. When the adapter is iteratively upgraded, the driver of the adapter is usually required to be developed, the development period of the hardware architecture is usually longer, and the development period is not necessarily adapted to the new characteristic of the adapter, namely, the rupture between the development of the driver and the development of the hardware architecture occurs, which is not beneficial to the test of the adapter to be detected before the adapter is on the market. In general, a development team will develop a model corresponding to the adapter to be tested to simulate the hardware architecture that is not yet installed, but this approach cannot guarantee the accuracy and comprehensiveness of the test.

In view of this, the embodiment of the disclosure provides a method for testing an adapter, which can obtain a test case, then convert the test case into a hardware case, and finally test the adapter to be tested according to the hardware case, and obtain a test result. The embodiment of the disclosure can acquire the test case of the application program interface level before the hardware interface level, and the test case is closer to the application program, so that the developer can obtain the test data highly adapted to the adapter to be detected even if the developer does not know the hardware interface used in the hardware architecture. In addition, the test case is more close to the application program, so that a developer can change the test case conveniently, and the test for the adapter to be detected can be conducted flexibly.

In a possible implementation manner, the testing method may be performed by a terminal device, which may be any device that may be connected to the adapter. The terminal device may be configured with a display screen to interact with a developer, and illustratively, the developer may also adjust a test case used by the adapter to be detected through the display screen, or perform other operations related to adjusting relevant configuration parameters of the adapter to be detected in other related technologies, which embodiments of the disclosure are not limited herein.

Referring to fig. 1, fig. 1 shows a flowchart of a testing method of an adapter according to an embodiment of the disclosure, as shown in fig. 1, where the testing method includes: step S100, obtaining a test case. Wherein the test cases are used to represent the load of the application program interface hierarchy handled by the adapter. For example, taking a display adapter (or simply referred to as a graphics card) as an example, when an application program (such as game software or video processing software) that needs to be processed by the graphics card is run by a host connected to the graphics card, a service API (Application Programming Interface ) that needs to be called by a service flow corresponding to the application program (such as loading a specific object at a specific position of a display screen, performing texture processing on a display screen, etc.) is sent to the graphics card, and then the driver of the graphics card converts the service API into a hardware API that can be identified by hardware to call hardware performance. In this process, the service API may be regarded as the load of the application program interface layer, that is, the load of the application program interface layer is abutted to the application program, and in the whole interface call layer, the visualization of the layer is relatively strong, which is beneficial for the developer to operate on the application program interface sequence.

Referring to fig. 2, fig. 2 is a flowchart illustrating a testing method of an adapter according to an embodiment of the disclosure, as shown in fig. 2, in a possible implementation, before step S100, the testing method may further include: in step S10 of the process of the present invention, a generic application program interface sequence is obtained. The universal application program interface sequence is used for representing an application program interface sequence which can be shared by different application programs. In combination with an actual application scenario, in the graphics card industry, there is usually an API with an open source, where the API with an open source may be used as an interface call standard commonly used in the industry, so as to be used by software or hardware in programming. Different vendors or different versions of graphics cards typically support the open-source API, and in this example, the service call sequence formed by the open-source API may be used as the generic application program interface sequence.

In one possible implementation, step S10 may include: and acquiring at least one of at least one preset application program interface sequence and input application program interface sequence corresponding to the adapter before the adapter to be detected in version information, and taking the at least one preset application program interface sequence and the input application program interface sequence as the universal application program interface sequence. Wherein different preset application program interface sequences are used for representing different functions of the adapter to be detected. For example, the preset application program interface sequence may be represented as a template file, where the template file records the load corresponding to the adapter of the previous version, so as to test whether the adapter to be detected has a performance problem in the previous load. In one example, a developer may, depending on the computing functionality that the adapter may provide, designing the preset application program interface sequence, for example: such computing functions include but are not limited to triangle drawing, computing matrix multiplication, adapter new property testing, multiple output testing, etc., the embodiments of the present disclosure are not limited herein. Illustratively, the file format of the template file is not limited in this disclosure, for example: may appear as a python format file to increase the user-side editing friendliness. In one example, a user may prune an application program interface sequence in a template file through an interaction page to alter a previous version of the application program interface sequence, embodiments of the present disclosure are not limited in this regard. In addition, the user may also manually input the application program interface sequence, for example, the template file may be given incremental modification, so that the template file may store not only the application program interface sequence of the previous version, but also the application program interface sequence corresponding to the new characteristic of the adapter to be detected. It should be understood that the manually input application program interface sequence may be not only an application program interface sequence corresponding to a new characteristic, but also an application program interface sequence corresponding to an adapter of a previous version as a supplemental test, and further, the manually input application program interface sequence may be a general application program interface sequence under industry standards because the step S20 may convert the application program interface sequence of the step S10 stage into an application program interface sequence adapted to the adapter to be detected. The embodiments of the present disclosure are not limited herein. According to the embodiment of the disclosure, the user-friendly test data editing environment can be realized through the preset and input application program interface sequences, so that the application program interface sequences of different version information can be applied to the adapter to be detected, and the comprehensiveness of the test result is improved.

Step S20, converting the universal application program interface sequence into an application program interface sequence adapted to the adapter to be detected. In combination with the actual application scenario, different vendors will also use the vendor's own internal non-open source API, and the adapter to be tested may also use the non-open source API to program to realize the functions that the vendor wants to realize. In view of this, embodiments of the present disclosure may allow conversion of an open-source, industry-standard-use API to a vendor-internal, non-open-source API. For example: the manufacturer can set a comparison relation table and store the comparison relation table in the conversion module, and then input the general application program interface sequence into the conversion module to be converted into the application program interface sequence which corresponds to the sequence and is matched with the adapter to be detected. The embodiment of the disclosure is not limited to a specific conversion process, and can convert a general application program interface sequence into an application program interface sequence adapted to the adapter to be detected. In some examples, filtering criteria (e.g., filtering out a sequence of application program interfaces that are not representative of strong, such as a sequence that is not related to a performance bottleneck, etc.) may also be set in the above-described conversion process to convert a partially generic sequence of application program interfaces into a sequence of application program interfaces that are adapted by the adapter to be detected, and embodiments of the disclosure are not limited herein.

And step S30, finally, determining the test case according to the application program interface sequence of the adapter to be detected.

In one possible implementation, step S30 may include any one of the following: and taking the application program interface sequence adapted to the adapter to be detected as the test case. And responding to input completion information of the input application program interface sequence, and taking the input application program interface sequence and the application program interface sequence adapted to the adapter to be detected as the test case. The developer may also, for example, input a new sequence of application program interfaces after conversion to the sequence of application program interfaces for which adapter adaptation is to be detected. In this case, the application program interface sequence input at this stage is an application program interface sequence to which the adapter to be detected is adaptable. For example, the input application program interface sequence may be an application program interface sequence corresponding to a new characteristic that the adapter to be detected may adapt to.

With continued reference to fig. 1, step S200 converts the test case into a hardware case. Wherein the hardware use case is used to represent the load of the hardware interface hierarchy of the adapter. In connection with the above example, the hardware API may be regarded as a load of the hardware interface layer, that is, the load of the hardware interface layer is in butt joint with the hardware of the adapter, so that the processing function of the hardware may be directly called. For example, the test case may be converted into a hardware case by a crawling script in the related art, which is not described herein in detail in the embodiments of the present disclosure.

In one possible implementation manner, the test case includes: the first test case and/or the second test case. The first test case is used for representing the load of the application program interface level corresponding to the adapter with version information in front of the adapter to be detected. The second test case is used for representing the load of the application program interface level, of which the version information is the same as that of the adapter to be detected or the adapter behind the adapter to be detected. In this case, step S200 may include: and converting the first test case into a first hardware case and/or converting the second test case into a second hardware case. The first hardware use case is used for representing the load of the hardware interface level of the adapter with version information in front of the adapter to be detected; the second hardware use case is used for representing the load of the hardware interface level of the adapter with version information identical to or behind the adapter to be detected. In the embodiment of the disclosure, the hardware use cases are classified according to version information, wherein the first hardware use case can be used for representing an application program interface call sequence used by the adapter to be detected in a previous version so as to test whether the adapter to be detected can normally support the characteristics of the original version under the current version. And the second hardware use case can be used for representing an application program interface call sequence used by the adapter to be detected in the current version or the later version so as to test whether the adapter to be detected can support new characteristics under the current version, thereby being beneficial to the comprehensive detection of the adapter to be detected.

Step S300, testing the adapter to be detected according to the hardware use case, and obtaining a test result.

In one possible implementation manner, the step S300 may include at least one of the following: and testing the adapter to be detected according to the first hardware use case to obtain a first test result which is used as a part of the test result. And testing the adapter to be detected according to the second hardware use case to obtain a second test result which is used as a part of the test result. The first test result is used for representing a test result of a load corresponding to the adapter with version information before the adapter to be detected. The second test result is used for representing a test result aiming at a load corresponding to the adapter with version information identical to or behind the adapter to be detected. In one example, the first hardware use case and the second hardware use case may be read through a program script, so as to obtain a first test result corresponding to the first hardware use case and having a strong correlation with the previous version characteristic, and a second test result corresponding to the second hardware use case and having a strong correlation with the new version characteristic. The program script may test the adapter to be tested according to the first hardware use case and the second hardware use case, and the embodiment of the disclosure is not limited to specific logic instructions related in the program script. For example: the program script can set different test modes, a first test result can be obtained through a first hardware use case in the prior characteristic test mode, and a second test result can be obtained through a second hardware use case in the new characteristic test mode. It should be understood that the first test result and the second test result may be used as a part of the test results, that is, the first test result and the second test result may exist in the test results at the same time, so as to completely embody the overall performance of the adapter to be tested.

In one possible implementation manner, the step S300 may include: and inputting the first hardware use case to an adapter corresponding to the version information of the first hardware use case to obtain a first test result of the adapter corresponding to the version information. And then, under the condition that the first test result of the adapter corresponding to the version information is higher than a preset threshold value, testing the adapter to be detected according to the first hardware use case and the second hardware use case to obtain a test result. For example, the adapter may normally operate in a certain version of load, so that the version information of the first hardware use case may be input to the adapter with the version information matched, and in the case that the test result is relatively reasonable (the developer may limit by adjusting the preset threshold value, the embodiment of the disclosure does not limit the specific value here), the first hardware use case may be submitted to the adapter to be tested to test, so that it may be ensured that the first hardware use case is reasonable data, and the test result of the adapter to be tested based on the first hardware use case is relatively high in representativeness. In addition, whether the conversion process of the test case into the hardware case has higher precision can be determined, if the first hardware case can be applied to the adapter corresponding to the version information, the conversion process of the test case into the hardware case can be regarded as having higher precision, and the adapter to be detected can be tested based on the converted hardware case, so that the test representativeness of the adapter to be detected can be improved.

In combination with an actual application scenario, the test method can be integrated in a terminal device connected with the adapter to be detected, and then an input interface can be provided in the terminal device for a developer to input test cases or to add, delete and check preset test cases, for example, the test cases can be related to the setting of a shader, the buffering of the adapter and the configuration of textures. The terminal device can uniformly convert the edited test cases into private test cases (for example, the private API) in the manufacturer, and then convert the test cases into hardware cases which can be identified by hardware. The hardware use case is assembled in the rendering pipeline of the adapter, and the load is processed by the core state drive of the adapter through the input/output control module so as to complete the test, so that conflicts of architecture teams and hardware teams in development time sequences can be effectively reduced. In addition, the embodiment of the disclosure can test the adapter before the adapter is streamed, which is helpful to determine the defects of the adapter in terms of functions and performances in advance, thereby reducing the cost of the adapter in the actual manufacturing stage.

It will be appreciated that the above-mentioned method embodiments of the present disclosure may be combined with each other to form a combined embodiment without departing from the principle logic, and are limited to the description of the present disclosure. It will be appreciated by those skilled in the art that in the above-described methods of the embodiments, the particular order of execution of the steps should be determined by their function and possible inherent logic.

In addition, the disclosure further provides a testing device for an adapter, an electronic device, a computer readable storage medium, and a program, which can be used to implement any one of the testing methods for an adapter provided in the disclosure, and corresponding technical schemes and descriptions and corresponding descriptions of method parts are omitted.

Referring to fig. 3, fig. 3 shows a block diagram of a testing apparatus of an adapter according to an embodiment of the present disclosure, and as shown in fig. 3, the testing apparatus 100 includes: the test case acquisition module 110 is configured to acquire a test case; wherein the test case is used to represent the load of the application program interface hierarchy processed by the adapter; the hardware use case conversion module 120 is configured to convert the test use case into a hardware use case; wherein the hardware use case is used for representing the load of the hardware interface level of the adapter; and the test result generating module 130 is configured to test the adapter to be tested according to the hardware use case, and obtain a test result.

In one possible embodiment, the test device further comprises: the test case determining module is used for acquiring a universal application program interface sequence; the universal application program interface sequence is used for representing an application program interface sequence which can be shared by different application programs; converting the universal application program interface sequence into an application program interface sequence adapted to the adapter to be detected; and determining the test case according to the application program interface sequence of the adapter to be detected.

In a possible implementation manner, the testing the adapter to be tested according to the hardware use case and obtaining a test result includes at least one of the following: according to the first hardware use case, testing the adapter to be detected to obtain a first test result which is used as a part of the test result; the first test result is used for representing a test result of a load corresponding to the adapter with version information before the adapter to be detected; according to the second hardware use case, testing the adapter to be detected to obtain a second test result which is used as a part of the test result; the second test result is used for representing a test result aiming at a load corresponding to the adapter with version information identical to or behind the adapter to be detected.

In one possible implementation manner, the testing the adapter to be tested according to the hardware use case and obtaining a test result includes: inputting the first hardware use case to an adapter corresponding to the version information of the first hardware use case, and obtaining a first test result of the adapter corresponding to the version information; and under the condition that a first test result of the adapter corresponding to the version information is higher than a preset threshold value, testing the adapter to be detected according to the first hardware use case and the second hardware use case to obtain a test result.

The method has specific technical association with the internal structure of the computer system, and can solve the technical problems of improving the hardware operation efficiency or the execution effect (including reducing the data storage amount, reducing the data transmission amount, improving the hardware processing speed and the like), thereby obtaining the technical effect of improving the internal performance of the computer system which accords with the natural law.

In some embodiments, functions or modules included in an apparatus provided by the embodiments of the present disclosure may be used to perform a method described in the foregoing method embodiments, and specific implementations thereof may refer to descriptions of the foregoing method embodiments, which are not repeated herein for brevity.

The disclosed embodiments also provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the above-described method. The computer readable storage medium may be a volatile or nonvolatile computer readable storage medium.

The embodiment of the disclosure also provides an electronic device, which comprises: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to invoke the instructions stored in the memory to perform the above method.

Embodiments of the present disclosure also provide a computer program product comprising computer readable code, or a non-transitory computer readable storage medium carrying computer readable code, which when run in a processor of an electronic device, performs the above method.

The electronic device may be provided as a terminal device or other form of device.

Fig. 4 shows a block diagram of an electronic device 800 provided in accordance with an embodiment of the present disclosure. For example, the electronic device 800 may be a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device, a computing device, an in-vehicle device, a wearable device, or the like.

Referring to fig. 4, the electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output interface 812, a sensor component 814, and a communication component 816.

The processing component 802 generally controls overall operation of the electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations at the electronic device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply component 806 provides power to the various components of the electronic device 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 800.

The multimedia component 808 includes a screen between the electronic device 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the electronic device 800 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.

Input/output interface 812 provides an interface between processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the electronic device 800. For example, the sensor assembly 814 may detect an on/off state of the electronic device 800, a relative positioning of the components, such as a display and keypad of the electronic device 800, the sensor assembly 814 may also detect a change in position of the electronic device 800 or a component of the electronic device 800, the presence or absence of a user's contact with the electronic device 800, an orientation or acceleration/deceleration of the electronic device 800, and a change in temperature of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a photosensor, such as a Complementary Metal Oxide Semiconductor (CMOS) or Charge Coupled Device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate communication between the electronic device 800 and other devices, either wired or wireless. The electronic device 800 may access a wireless network based on a communication standard, such as a wireless network (Wi-Fi), a second generation mobile communication technology (2G), a third generation mobile communication technology (3G), a fourth generation mobile communication technology (4G), long Term Evolution (LTE) of a universal mobile communication technology, a fifth generation mobile communication technology (5G), or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including computer program instructions executable by processor 820 of electronic device 800 to perform the above-described methods.

The present disclosure may be a system, method, and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.

The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.

Computer program instructions for performing the operations of the present disclosure can be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present disclosure are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information of computer readable program instructions, which can execute the computer readable program instructions.

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The computer program product may be realized in particular by means of hardware, software or a combination thereof. In an alternative implementation

In an example, the computer program product is embodied as a computer storage medium, and in another alternative embodiment, the computer 5 program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), or the like.

The foregoing description of various embodiments is intended to highlight differences between the various embodiments, which may be the same or similar to each other by reference, and is not repeated herein for the sake of brevity.

It will be appreciated by those skilled in the art that in the above-described methods of the embodiments, the order of writing the steps is not

Meaning that the exact order of execution constitutes any limitation on the implementation process and the specific order of execution of the steps should be determined by their function 0 and possibly inherent logic.

If the technical scheme of the application relates to personal information, the product applying the technical scheme of the application clearly informs the personal information processing rule before processing the personal information, and obtains independent consent of the individual. If the technical scheme of the application relates to sensitive personal information, the product applying the technical scheme of the application obtains individual consent before processing the sensitive personal information, and

While meeting the requirements of "explicit consent". For example, at a personal information acquisition device such as a camera, a clear and significant 5 mark is set to inform that the personal information acquisition range is entered, personal information will be acquired, if the personal voluntarily enters the acquisition

The range is regarded as agreeing to collect personal information; or on the device for processing the personal information, under the condition that obvious identification/information is utilized to inform the personal information processing rule, personal authorization is obtained by popup information or a person is requested to upload personal information and the like; the personal information processing rule may include information such as a personal information processor, a personal information processing purpose, a processing mode, and a type of personal information to be processed.

0 having described various embodiments of the present disclosure, the foregoing description is exemplary, not exhaustive, and

not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method of testing an adapter, the method comprising:

acquiring a test case; wherein the test case is used to represent the load of the application program interface hierarchy processed by the adapter;

converting the test case into a hardware case; wherein the hardware use case is used for representing the load of the hardware interface level of the adapter;

and testing the adapter to be detected according to the hardware use case, and obtaining a test result.

2. The test method of claim 1, comprising, prior to the obtaining the test case:

acquiring a universal application program interface sequence; the universal application program interface sequence is used for representing an application program interface sequence which can be shared by different application programs;

converting the universal application program interface sequence into an application program interface sequence adapted to the adapter to be detected;

and determining the test case according to the application program interface sequence of the adapter to be detected.

3. The method of testing of claim 2, wherein the obtaining a generic application program interface sequence comprises:

acquiring at least one of at least one preset application program interface sequence and input application program interface sequence corresponding to an adapter before the adapter to be detected in version information, and taking the version information as the universal application program interface sequence; wherein different preset application program interface sequences are used for representing different functions of the adapter to be detected.

4. The testing method according to claim 2, wherein the determining the test case according to the sequence of application program interfaces adapted to the adapter to be tested includes any one of the following:

taking the application program interface sequence of the adapter to be detected as the test case;

and responding to input completion information of the input application program interface sequence, and taking the input application program interface sequence and the application program interface sequence adapted to the adapter to be detected as the test case.

5. The test method according to any one of claims 1 to 4, wherein the test case includes: the first test case and/or the second test case; the first test case is used for representing the load of an application program interface layer corresponding to the adapter with version information in front of the adapter to be detected; the second test case is used for representing the load of an application program interface level, of which the version information is the same as that of the adapter to be detected or the adapter behind the adapter to be detected;

the converting the test case into a hardware case includes: converting the first test case into a first hardware case and/or converting the second test case into a second hardware case; the first hardware use case is used for representing the load of the hardware interface level of the adapter with version information in front of the adapter to be detected; the second hardware use case is used for representing the load of the hardware interface level of the adapter with version information identical to or behind the adapter to be detected.

6. The testing method of claim 5, wherein the testing the adapter to be tested according to the hardware use case and obtaining the test result comprises at least one of the following:

according to the first hardware use case, testing the adapter to be detected to obtain a first test result which is used as a part of the test result; the first test result is used for representing a test result of a load corresponding to the adapter with version information before the adapter to be detected;

according to the second hardware use case, testing the adapter to be detected to obtain a second test result which is used as a part of the test result; the second test result is used for representing a test result aiming at a load corresponding to the adapter with version information identical to or behind the adapter to be detected.

7. The testing method of claim 5, wherein the testing the adapter to be tested according to the hardware use case and obtaining the test result comprises:

inputting the first hardware use case to an adapter corresponding to the version information of the first hardware use case, and obtaining a first test result of the adapter corresponding to the version information;

And under the condition that a first test result of the adapter corresponding to the version information is higher than a preset threshold value, testing the adapter to be detected according to the first hardware use case and the second hardware use case to obtain a test result.

8. A test device for an adapter, the test device comprising:

the test case acquisition module is used for acquiring test cases; wherein the test case is used to represent the load of the application program interface hierarchy processed by the adapter;

the hardware use case conversion module is used for converting the test use case into a hardware use case; wherein the hardware use case is used for representing the load of the hardware interface level of the adapter;

and the test result generation module is used for testing the adapter to be detected according to the hardware use case and obtaining a test result.

9. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to invoke the instructions stored in the memory to perform the test method of any of claims 1 to 7.

10. A computer readable storage medium having stored thereon computer program instructions, which when executed by a processor implement the test method of any of claims 1 to 7.