Hardware test method and device, electronic equipment, storage medium and product
Determine the target fault test item and generate the corresponding test packets through the user interface, solve the problem that the existing hardware test method is not flexible, and realize the flexibility and convenience of the test.
Patent Information
- Application Number
- CN202411525503.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-01-28
AI Technical Summary
The existing hardware testing methods are not flexible enough and it is difficult to respond to users' fault testing needs in real time.
Determine the target fault test item through the user interface, and generate the target fault test packet based on these items, and send it to the hardware to be tested for fault testing.
The convenient input of faults has been achieved, the flexibility and convenience of testing can be improved, and it can respond to the user's test needs in real time.
Smart Images
Figure CN119377025A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of testing technology, and in particular to a hardware testing method, device, electronic device, storage medium and product. Background Art
[0002] Hardware testing, such as E2E (End to End) testing, usually uses pre-set test cases and standardized configurations to test the hardware under test, which is not flexible enough. Summary of the invention
[0003] In order to overcome the problems existing in the related art, the present disclosure provides a hardware testing method, device, electronic device, storage medium and product, so as to realize flexible and fast injection of test faults during the testing process, and improve the flexibility and convenience of the test.
[0004] According to a first aspect of an embodiment of the present disclosure, there is provided a hardware testing method, comprising: Determine the target fault test item through the user interface; Based on the target fault test item, generating a target fault test message; The target fault test message is sent to the hardware to be tested to perform a fault test on the hardware to be tested.
[0005] Optionally, the method further comprises: Obtaining a fault identification result of the hardware under test for the target fault test message; According to the fault identification result, a test result corresponding to the target fault test item is obtained.
[0006] Optionally, the method further comprises: The test result corresponding to the target fault test item is displayed through the user interface.
[0007] Optionally, determining the target fault test item through the user interface includes: In response to a fault input operation of a user on the user interface, the target fault test item is determined.
[0008] Optionally, before determining the target fault test item in response to a fault input operation of the user on the user interface, the method further includes: Displaying test controls corresponding to a plurality of candidate fault test items through the user interface, where one candidate fault test item corresponds to one test control; The step of determining the target fault test item in response to a fault input operation by a user on the user interface includes: In response to a user's selection operation on the test control on the user interface, a candidate fault test item corresponding to the test control selected by the user is determined as the target fault test item.
[0009] Optionally, the generating a target fault test message based on the target fault test item includes: Acquire a target simulation message, wherein the target simulation message includes at least one frame message; The target simulation message is processed through the fault injection strategy corresponding to the target fault test item to obtain the target fault test message.
[0010] Optionally, the method further comprises: Acquire a message to be tested sent by the hardware to be tested, so as to perform a sending test on the hardware to be tested; Verifying the message to be tested to obtain a test result corresponding to the sending test; The test result corresponding to the sending test is displayed through the user interface.
[0011] According to a second aspect of an embodiment of the present disclosure, there is provided a hardware testing device, including: A determination module, configured to determine a target fault test item through a user interface; A generating module, configured to generate a target fault test message based on the target fault test item; The testing module is configured to send the target fault test message to the hardware to be tested, so as to perform a fault test on the hardware to be tested.
[0012] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including: processor; a memory for storing processor-executable instructions; Among them, the processor is configured to implement the steps of the hardware testing method provided by the first aspect of the present disclosure when executing.
[0013] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the steps of the hardware testing method provided in the first aspect of the present disclosure are implemented.
[0014] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, which, when executed by a processor, implements the steps of the hardware testing method provided in the first aspect of the present disclosure.
[0015] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects: The target fault test item is determined through the user interface, and based on the target fault test item, a target fault test message is generated, and then the target fault test message is sent to the hardware to be tested to perform a fault test on the hardware to be tested. By setting the user interface, the fault test that the user currently expects to perform can be determined in real time, thereby determining the corresponding target fault test item, and then the target fault test message can be generated in real time based on the target fault test item to perform the corresponding fault test on the hardware to be tested, thereby realizing the convenient input of the fault, so as to improve the flexibility and convenience of the test.
[0016] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0018] Figure 1 The diagram is a schematic diagram of a scenario of a hardware testing method according to an exemplary embodiment.
[0019] Figure 2 The figure is a flowchart of a hardware testing method according to an exemplary embodiment.
[0020] Figure 3 The figure is a schematic diagram showing a structure of a fault test according to an exemplary embodiment.
[0021] Figure 4 The figure is a schematic diagram of a structure of a sending test according to an exemplary embodiment.
[0022] Figure 5 The invention is a block diagram of a hardware testing device according to an exemplary embodiment.
[0023] Figure 6 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION
[0024] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0025] It should be noted that all actions of acquiring signals, information or data in the present disclosure are carried out in compliance with the relevant data protection laws and policies of the country where the device is located and with the authorization given by the owner of the corresponding device.
[0026] In the related art, hardware testing usually uses pre-set test cases and standardized configurations to test the hardware to be tested, and the testing method is not flexible enough.
[0027] In response to the above technical problems, the embodiments of the present disclosure provide a hardware testing method, device, electronic device, storage medium and product. By setting a user interface, it is possible to determine in real time the fault test that the user currently expects to perform, thereby determining the corresponding target fault test item, and then based on the target fault test item, it is possible to generate a target fault test message in real time to perform a corresponding fault test on the hardware to be tested, thereby achieving convenient input of faults, so as to improve the flexibility and convenience of testing.
[0028] Figure 1 is a schematic diagram of a scenario of a hardware testing method according to an exemplary embodiment. Figure 1 As shown, it includes hardware to be tested and a hardware testing device, and the hardware testing device includes a user interface for human-computer interaction. The hardware to be tested may be an ECU (Electronic Control Unit).
[0029] Figure 2 is a flowchart of a hardware testing method according to an exemplary embodiment. Figure 2 As shown, it can be applied to the above hardware testing device and may include the following steps.
[0030] In step S201, a target fault test item is determined through a user interface.
[0031] In this embodiment, the user interface may be an interface capable of human-computer interaction with the user, and capable of realizing information input and output. The user can input information in real time through the user interface to determine the fault test that the user currently expects to perform, thereby obtaining the target fault test item. Among them, the target fault test item may include at least one of timeout, repetition, frame skipping, and disorder of the message.
[0032] In step S202, a target fault test message is generated based on the target fault test item.
[0033] In this embodiment, different fault test items may correspond to different fault injection strategies, and corresponding target fault test messages may be generated based on the fault injection strategies corresponding to the target fault test items, so as to perform corresponding fault tests on the hardware under test. The target fault test message may include at least one frame message. Different fault test items may have different frame numbers of corresponding fault test messages.
[0034] In step S203, a target fault test message is sent to the hardware to be tested, so as to perform a fault test on the hardware to be tested.
[0035] In this embodiment, after obtaining the target fault test message, the target fault test message can be sent to the hardware under test according to the sending strategy corresponding to the target fault test item, so as to determine the corresponding test result according to the identification result corresponding to the hardware under test, wherein the test result can be a pass or a fail.
[0036] In a possible implementation, before performing a fault test, or while performing a fault test, a normal reception test of the hardware under test may be performed to determine whether the hardware under test has the ability to verify messages. Specifically, a simulated message may be sent normally to the hardware under test, and the simulated message is a message with correct content, so as to perform a reception test on the hardware under test. The reception recognition result of the hardware under test for the simulated message is obtained, and the reception test result corresponding to the reception test is determined based on the reception recognition result. The reception test result is displayed through a user interface, so as to determine whether the hardware under test has the ability to verify messages through the reception test. In this way, fault identification errors caused by the lack of message verification capability of the hardware under test can be eliminated during the fault test.
[0037] In a possible implementation, the hardware testing method further includes: Obtain the fault identification result of the hardware under test for the target fault test message; and obtain the test result corresponding to the target fault test item based on the fault identification result.
[0038] In this embodiment, the fault identification result may include a test fault code obtained after the hardware under test identifies the target fault test message, and different faults may correspond to different fault codes. For example, a message timeout corresponds to fault code 1, a message repetition corresponds to fault code 2, a message frame skipping corresponds to fault code 3, a message disorder corresponds to fault code 4, and a message normal corresponds to fault code 0. The test fault code obtained by the hardware under test can be verified by the actual fault code corresponding to the target fault test item to obtain a test result corresponding to the target fault test item. Specifically, when the test fault code is the same as the actual test code, the test result corresponding to the target fault test item is determined to be a passed test. When the test fault code is different from the actual test code, the test result corresponding to the target fault test item is determined to be a failed test.
[0039] Figure 3 is a structural diagram of a fault test according to an exemplary embodiment. Figure 3 As shown, in a possible implementation manner, the hardware testing method further includes: The test results corresponding to the target fault test items are displayed through the user interface.
[0040] In this embodiment, the user interface can display the target fault test item, and the indicator control corresponding to each test item can be set on the user interface. Each test item is also provided with a corresponding test interface, and the test interface corresponding to each test item is coupled with the indicator control corresponding to the test item, and the indicator control is used to display the test result of the corresponding test item. The test item may include a fault test item, a receiving test, and a sending test. After obtaining the test result corresponding to the target fault test item, the test result corresponding to the target fault test item can be transmitted to the test interface corresponding to the target fault test item so as to be displayed by the indicator control corresponding to the target fault test item. Among them, the indicator control can be a text box or an indicator light. For example, if the indicator control is a text box, the text "passed the test" or "failed the test" can be directly output. If the indicator control is an indicator light, different test results can be represented by different colors, for example, the indicator light shows green to represent the passed test, and the indicator light shows red to represent the failed test. The Panel editor in the Vector tool chain can be used, or the win32 interface library can be called to realize the control and observation of the test interface through Windows.
[0041] In a possible implementation, determining a target fault test item through a user interface includes: In response to a fault input operation by a user on a user interface, a target fault test item is determined.
[0042] In this embodiment, the user interface can input the fault test item through the fault injection interface, so that the target fault test item can be determined through the fault test item input by the user. Among them, a fault input plug-in can be set on the user interface, and the fault input plug-in is connected to the fault injection interface, so that the user can inject the fault test item through the fault injection interface through the fault input plug-in.
[0043] In a possible implementation manner, before determining the target fault test item in response to the fault input operation of the user on the user interface, the method further includes: The test controls corresponding to the multiple candidate fault test items are displayed through the user interface, and one candidate fault test item corresponds to one test control.
[0044] In response to a fault input operation of a user on a user interface, determining a target fault test item includes: In response to a user's selection operation on the test control on the user interface, a candidate fault test item corresponding to the test control selected by the user is determined as a target fault test item.
[0045] In this embodiment, the target fault test item may include a fault injection strategy, and the fault input plug-in may be a plurality of test controls, each test control corresponding to a fault test item. For a plurality of candidate fault test items, a test control and a fault injection strategy corresponding to each candidate fault test item may be generated respectively, and a fault injection interface corresponding to each candidate fault test item may be set. For any candidate fault test item, the test control corresponding to the candidate fault test item is connected to the fault injection interface corresponding to the candidate fault test item. The test controls corresponding to a plurality of candidate fault test items may be displayed through a user interface so that the user can select the fault test item currently desired to be performed. The user may select the test control on the user interface, such as a click operation. In response to the user's selection operation for the test control on the user interface, the candidate fault test item corresponding to the test control selected by the user is determined as the target fault test item. Then the target fault test item may be injected through the corresponding fault injection interface. The Panel editor in the Vector tool chain may be used, or the win32 interface library may be called to realize control and observation of the fault injection interface through Windows.
[0046] In a possible implementation, generating a target fault test message based on a target fault test item includes: A target simulation message is obtained, wherein the target simulation message includes at least one frame of message; and the target simulation message is processed according to a fault injection strategy corresponding to a target fault test item to obtain a target fault test message.
[0047] In this embodiment, the verification algorithm function in the E2E detection algorithm, such as the CRC (Cyclic Redundancy Check) algorithm function, can be developed based on the target standard using Vector's tool-specific programming language. The local simulation function can be used to simulate the message simulation to obtain a multi-frame simulation message. The target simulation message can be obtained based on the multi-frame simulation message, and the target simulation message includes at least one frame message. The fault injection strategy corresponding to the target fault test item can be called to process the target simulation message.
[0048] Specifically, for any frame simulation message in the target simulation message, the verification algorithm function is used to calculate the verification value of the frame simulation message to obtain the accurate verification value corresponding to the frame simulation message, and based on the fault injection strategy, the accurate verification value corresponding to the frame simulation message is modified, for example, adding or subtracting a preset value to obtain a fault verification value different from the accurate verification value corresponding to the frame simulation message. And through the fault injection strategy, based on the RollingCounter mechanism, the target simulation message is adjusted, and the target simulation text after the adjustment and carrying the fault verification value is determined as the target fault test message. So that the target fault test message can be sent to the hardware to be tested for testing. The hardware to be tested can verify the verification value of the target fault test message and identify it based on the RollingCounter mechanism to obtain the corresponding fault identification result.
[0049] Among them, for the verification of the check value, the hardware under test can calculate the check value of the received target fault test message based on the verification algorithm function, obtain the identification check value, and compare it with the fault check value carried by the target fault test message to determine whether the two are the same, and combine with the RollingCounter mechanism to obtain a specific fault identification result.
[0050] For normal reception test, the local simulation function can be used to simulate the message simulation to obtain a multi-frame simulation message. And for any frame simulation message in the multi-frame simulation message, the verification algorithm function is used to calculate the verification value of the frame simulation message to obtain the accurate verification value corresponding to the frame simulation message, and the multi-frame simulation message carrying the accurate verification value is sent normally to the hardware under test for reception test. Based on the verification algorithm function, the hardware under test can calculate the verification value of the received multi-frame simulation message carrying the accurate verification value to obtain the predicted verification value, and compare it with the accurate verification value to determine whether the two are the same. Thus, the recognition result corresponding to the reception test is obtained, and the test result corresponding to the reception test is determined based on the recognition result corresponding to the reception test.
[0051] Figure 4 is a schematic diagram of a structure of a sending test according to an exemplary embodiment. Figure 4 As shown, in a possible implementation, the fault input plug-in may be a text input plug-in, so that the user can input the fault injection strategy in real time through the fault input plug-in, and then obtain the target fault test message through the fault injection strategy input by the user.
[0052] In a possible implementation manner, the fault testing method further includes: Obtain the message to be tested sent by the hardware to be tested to perform a sending test on the hardware to be tested; verify the message to be tested to obtain a test result corresponding to the sending test; and display the test result corresponding to the sending test through a user interface.
[0053] In this embodiment, for the sending test, the test message sent by the hardware under test can be obtained, and the test message carries the corresponding accurate verification value, and the predicted verification value of the received message under test can be calculated based on the verification algorithm function, so as to obtain the corresponding test result by calculating the predicted verification value of the message under test and the corresponding accurate verification value carried by the message under test.
[0054] Specifically, it can be determined whether the calculated predicted check value of the message to be tested is the same as the accurate check value corresponding to the message to be tested. If the calculated predicted check value of the message to be tested is the same as the accurate check value corresponding to the message to be tested, the test result corresponding to the sending test is determined to be a passed test. If the calculated predicted check value of the message to be tested is not the same as the accurate check value corresponding to the message to be tested, the test result corresponding to the sending test is determined to be a failed test. An indication control corresponding to the sending test can be set on the user interface, and a test interface corresponding to the sending test can be set. The test interface corresponding to the sending test is connected to the indication control corresponding to the sending test, so that after obtaining the test result corresponding to the sending test, the test result corresponding to the sending test is transmitted to the test interface corresponding to the sending test, and then the test result corresponding to the sending test is displayed through the indication control corresponding to the sending test on the user interface. When performing a fault test, a receiving test and a sending test can also be performed simultaneously, and the corresponding test results are displayed to the user to eliminate the influence of accidental receiving errors or sending errors on the fault test results and improve the accuracy of the test results.
[0055] Figure 5 is a block diagram of a hardware testing device according to an exemplary embodiment. Figure 5 The hardware testing device 500 includes a determination module 501, a generation module 502 and a testing module 503.
[0056] The determination module 501 is configured to determine a target fault test item through a user interface; The generating module 502 is configured to generate a target fault test message based on the target fault test item; The testing module 503 is configured to send the target fault test message to the hardware under test to perform a fault test on the hardware under test.
[0057] Optionally, the hardware testing device 500 further includes: A first acquisition module is configured to obtain a fault identification result of the hardware under test for the target fault test message; The obtaining module is configured to obtain the test result corresponding to the target fault test item according to the fault identification result.
[0058] Optionally, the hardware testing device 500 further includes: The first display module is configured to display the test result corresponding to the target fault test item through the user interface.
[0059] Optionally, the determining module 501 includes: The determination submodule is configured to determine the target fault test item in response to a fault input operation of the user on the user interface.
[0060] Optionally, the hardware testing device 500 further includes: A second display module is configured to display test controls corresponding to a plurality of candidate fault test items through the user interface, where one candidate fault test item corresponds to one test control; The determination submodule comprises: The determining unit is configured to determine, in response to a user's selection operation on the test control on the user interface, a candidate fault test item corresponding to the test control selected by the user as the target fault test item.
[0061] Optionally, the generating module 502 includes: An acquisition submodule is configured to acquire a target simulated message, wherein the target simulated message includes at least one frame message; The obtaining submodule is configured to process the target simulation message through the fault injection strategy corresponding to the target fault test item to obtain the target fault test message.
[0062] Optionally, the hardware testing device 500 further includes: A second acquisition module is configured to acquire a message to be tested sent by the hardware to be tested, so as to perform a sending test on the hardware to be tested; A verification module is configured to verify the message to be tested and obtain a test result corresponding to the sending test; The third display module is configured to display the test result corresponding to the sending test through the user interface.
[0063] Regarding the hardware testing device 500 in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0064] The present disclosure also provides a computer-readable storage medium on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the hardware testing method provided by the present disclosure are implemented.
[0065] Figure 6 6 is a block diagram of an electronic device according to an exemplary embodiment. For example, the electronic device 600 may be a hardware testing device.
[0066] Reference Figure 6 The electronic device 600 may include one or more of the following components: a processing component 602 , a first memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output interface 612 , a sensor component 614 , and a communication component 616 .
[0067] The processing component 602 generally controls the overall operation of the electronic device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more first processors 620 to execute instructions to complete all or part of the steps of the hardware testing method described above. In addition, the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.
[0068] The first memory 604 is configured to store various types of data to support operations on the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phone book data, messages, pictures, videos, etc. The first memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, 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 disk or optical disk.
[0069] The power supply component 606 provides power to the various components of the electronic device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 600.
[0070] The multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and the user. 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 the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the electronic device 600 is in an operating 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 a focal length and optical zoom capability.
[0071] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), and when the electronic device 600 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the first memory 604 or sent via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.
[0072] The input / output interface 612 provides an interface between the processing component 602 and the peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
[0073] The sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the electronic device 600. For example, the sensor assembly 614 can detect the open / closed state of the electronic device 600, the relative positioning of the components, such as the display and keypad of the electronic device 600, and the sensor assembly 614 can also detect the position change of the electronic device 600 or a component of the electronic device 600, the presence or absence of contact between the user and the electronic device 600, the orientation or acceleration / deceleration of the electronic device 600, and the temperature change of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
[0074] The communication component 616 is configured to facilitate wired or wireless communication between the electronic device 600 and other devices. The electronic device 600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0075] In an exemplary embodiment, the electronic device 600 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 components to perform the above-mentioned hardware testing method.
[0076] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a first memory 604 including instructions, and the instructions can be executed by a first processor 620 of the electronic device 600 to complete the above hardware testing method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0077] In another exemplary embodiment, a computer program product is further provided. The computer program product includes a computer program executable by a programmable device. The computer program has a code portion for executing the above hardware testing method when executed by the programmable device.
[0078] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.
[0079] It should be understood that the features of some embodiments of the various present disclosures described herein may be combined with each other, unless specifically stated otherwise.
[0080] Although terms such as "first", "second" and "third" can be used herein to describe various components, parts, regions, layers or sections, these components, parts, regions, layers or sections are not limited to these terms. On the contrary, these terms are only used to distinguish one component, component, region, layer or section from another component, component, region, layer or section. Therefore, without departing from the teachings of each example, the first component, component, region, layer or section mentioned in the examples described herein may also be referred to as the second component, component, region, layer or section. In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first" and "second" may expressly or implicitly include at least one of the features. In the description herein, the meaning of "multiple" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0081] In addition, the word "exemplary" is used herein to indicate serving as an example, instance, or diagram. Any aspect or design described as "exemplary" in this article is not necessarily understood to be advantageous compared to other aspects or designs. On the contrary, the use of the word exemplary is intended to present concepts in a specific way. As used herein, the term "or" is intended to represent an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X applies A or B" is intended to represent any one of the natural inclusive arrangements. That is, if X applies A; X applies B; or X applies both A and B, "X applies A or B" is satisfied under any of the aforementioned examples. In addition, unless otherwise specified or clearly pointed to a singular form from the context, the articles "one" and "an" as used in this application and the appended claims are generally understood to mean "one or more".
[0082] Likewise, although the present disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art after reading and understanding the specification and drawings. The present disclosure includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components (e.g., elements, resources, etc.) described above, unless otherwise indicated, the terms used to describe such components are intended to correspond to any component (functionally equivalent) that performs the specific functions of the described components, even if the structure is not equivalent to the disclosed structure. In addition, although specific features of the present disclosure may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations as may be desired and beneficial to any given or specific application. In addition, with respect to "including", "having", "having", "having", or variations thereof used in a specific embodiment or claim, such terms are intended to be inclusive in a manner similar to the term "comprising".
[0083] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.
[0084] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A hardware testing method, characterized in that: include: Determine the target fault test item through the user interface; Based on the target fault test item, generating a target fault test message; The target fault test message is sent to the hardware to be tested to perform a fault test on the hardware to be tested.
2. The hardware testing method according to claim 1, characterized in that: The method further comprises: Obtaining a fault identification result of the hardware under test for the target fault test message; According to the fault identification result, a test result corresponding to the target fault test item is obtained.
3. The hardware testing method according to claim 2, characterized in that: The method further comprises: The test result corresponding to the target fault test item is displayed through the user interface.
4. The hardware testing method according to claim 1, characterized in that: Determining the target fault test item through the user interface includes: In response to a fault input operation of a user on the user interface, the target fault test item is determined.
5. The hardware testing method according to claim 4, characterized in that: Before determining the target fault test item in response to a fault input operation of the user on the user interface, the method further includes: Displaying test controls corresponding to a plurality of candidate fault test items through the user interface, where one candidate fault test item corresponds to one test control; The step of determining the target fault test item in response to a fault input operation by a user on the user interface includes: In response to a user's selection operation on the test control on the user interface, a candidate fault test item corresponding to the test control selected by the user is determined as the target fault test item.
6. The hardware testing method according to claim 1, characterized in that: The generating a target fault test message based on the target fault test item includes: Acquire a target simulation message, wherein the target simulation message includes at least one frame message; The target simulation message is processed through the fault injection strategy corresponding to the target fault test item to obtain the target fault test message.
7. The hardware testing method according to any one of claims 1 to 6, characterized in that: The method further comprises: Acquire a message to be tested sent by the hardware to be tested, so as to perform a sending test on the hardware to be tested; Verifying the message to be tested to obtain a test result corresponding to the sending test; The test result corresponding to the sending test is displayed through the user interface.
8. A hardware testing device, characterized in that: include: A determination module, configured to determine a target fault test item through a user interface; A generating module, configured to generate a target fault test message based on the target fault test item; The testing module is configured to send the target fault test message to the hardware to be tested, so as to perform a fault test on the hardware to be tested.
9. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to implement the steps of the hardware testing method described in any one of claims 1 to 7 when executed.
10. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the steps of the hardware testing method described in any one of claims 1 to 7 are implemented.
11. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the steps of the hardware testing method according to any one of claims 1 to 7.