CN117687853A

CN117687853A - Firmware detection method, device, equipment and medium

Info

Publication number: CN117687853A
Application number: CN202311685765.9A
Authority: CN
Inventors: 王宪臻; 左渠; 张国亮; 展晓洁
Original assignee: Ningchang Information Technology Hangzhou Co ltd
Current assignee: Ningchang Information Technology Hangzhou Co ltd
Priority date: 2023-12-08
Filing date: 2023-12-08
Publication date: 2024-03-12

Abstract

The invention discloses a firmware detection method, a device, equipment and a medium. The method comprises the following steps: in the compiling stage of the target BMC firmware, detecting the code of the target BMC firmware through a code detection script, and determining a compiling stage detection result; in the test stage, performing performance test on the target BMC firmware through a performance test script to determine a performance test result; in the performance test process, monitoring the running state information of the target BMC firmware through an information monitoring script to obtain monitoring data of the target BMC firmware; after the performance test process is finished, determining a test stage detection result according to the monitoring data and the performance test result, and providing a compiling stage detection result and a test stage detection result for a target user. The embodiment of the invention can rapidly and accurately detect the BMC firmware comprehensively in the compiling stage and the testing stage of the BMC firmware and determine whether the BMC firmware has abnormality or not.

Description

Firmware detection method, device, equipment and medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for detecting firmware.

Background

The baseboard management controller (Baseboard Management Controller, BMC) of the server is a control unit that monitors and manages the server. The BMC is mainly used for realizing the functions of managing the hardware state, the operating system, the health state and the power consumption of the server. BMC firmware is a program running in the BMC for implementing BMC functions. In order to ensure stable operation of the server and the BMC of the server, before the BMC firmware is put into use, the BMC firmware needs to be detected to determine whether the BMC firmware has an abnormality.

In the related art, a common firmware detection scheme for BMC firmware is: in the test stage of the BMC firmware, a technician manually performs performance test on the designated performance of the BMC firmware, detects the BMC firmware according to the performance test data, and determines whether the BMC firmware has an abnormality. The firmware detection scheme in the related art detects the BMC firmware through manual operation, has low efficiency and accuracy in the detection process, and cannot rapidly and accurately detect the BMC firmware comprehensively in the compiling stage and the testing stage of the BMC firmware.

Disclosure of Invention

The invention provides a firmware detection method, a device, equipment and a medium, which are used for solving the problem that a firmware detection scheme in the related technology cannot quickly and accurately detect BMC firmware comprehensively in a compiling stage and a testing stage of the BMC firmware.

According to an aspect of the present invention, there is provided a firmware detection method including:

in the compiling stage of the target BMC firmware, detecting the code of the target BMC firmware through a code detection script, and determining the compiling stage detection result of the target BMC firmware;

in the test stage of the target BMC firmware, performing performance test on the target BMC firmware running in a test server through a performance test script, and determining a performance test result of the target BMC firmware;

in the performance test process, monitoring the running state information of a target BMC firmware running in the test server through an information monitoring script to obtain monitoring data of the target BMC firmware;

after the performance test process is finished, determining a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result, and providing the compiling stage detection result and the test stage detection result for a target user.

According to the technical scheme, the BMC firmware can be automatically detected in the compiling stage of the BMC firmware based on the code detection script, whether the BMC firmware is abnormal or not is determined, the BMC firmware can be automatically subjected to performance detection and information monitoring in the compiling stage of the BMC firmware based on the performance test script and the information monitoring script, whether the BMC firmware is abnormal or not is determined, the BMC firmware can be rapidly and accurately comprehensively detected in the compiling stage and the testing stage of the BMC firmware, whether the BMC firmware is abnormal or not is determined, and the efficiency and the accuracy of the detection process are improved.

Optionally, detecting the code of the target BMC firmware by a code detection script, and determining a compilation stage detection result of the target BMC firmware includes:

acquiring codes of the target BMC firmware;

detecting whether the code of the target BMC firmware has static errors or not through a code detection script, and generating a code detection result of the code;

if the code detection result is that static errors exist, determining that the compiling stage detection result of the target BMC firmware is that the errors exist, outputting first alarm information, and stopping the current detection process.

According to the technical scheme, based on the code detection script, the BMC firmware can be automatically detected in the compiling stage of the BMC firmware, whether the BMC firmware is abnormal or not is determined, the abnormal BMC firmware can be conveniently found in time in the compiling stage of the BMC firmware, and alarm information can be output after the abnormal BMC firmware is determined to be abnormal, so that related personnel can process the abnormal BMC firmware in time.

Optionally, after detecting whether the code of the target BMC firmware has a static error by the code detection script, generating a code detection result of the code, the method further includes:

And if the code detection result is that the static error does not exist, determining that the compiling stage detection result of the target BMC firmware is that the abnormality does not exist.

According to the technical scheme provided by the embodiment of the invention, after the fact that the static error does not exist in the code of the BMC firmware is detected, the fact that the abnormality does not exist in the BMC firmware in the compiling stage is determined, and the detection result of the BMC firmware in the compiling stage is generated.

Optionally, performing performance test on the target BMC firmware running in the test server through a performance test script, and determining a performance test result of the target BMC firmware includes:

the performance test script is sent to a test server, so that the test server performs performance test on target BMC firmware running in the test server according to the performance test script, determines a performance test result of the target BMC firmware, and feeds back the performance test result of the target BMC firmware;

and acquiring a performance test result of the target BMC firmware fed back by the test server.

According to the technical scheme, based on the performance test script, the performance test of the BMC firmware can be automatically performed in the test stage of the BMC firmware, the performance test result of the BMC firmware is determined, whether the BMC firmware is abnormal or not is conveniently determined according to the performance test result, and the abnormality of the BMC firmware is timely found in the test stage of the BMC firmware.

Optionally, determining a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result includes:

performing anomaly detection on the monitoring data and the performance test result;

and determining a test stage detection result of the target BMC firmware according to the abnormality detection result.

According to the technical scheme, after performance testing and running state information monitoring are carried out on the BMC firmware running in the test server, whether the BMC firmware in the test stage is abnormal or not can be automatically determined based on the monitoring data and the performance testing result, and the abnormal situation of the BMC firmware can be found in time in the test stage of the BMC firmware.

Optionally, after determining the test stage detection result of the target BMC firmware according to the anomaly detection result, the method further includes:

and if the detection result in the test stage is that the abnormality exists, outputting second alarm information.

According to the technical scheme provided by the embodiment of the invention, after the target BMC firmware in the testing stage is determined to have the abnormality, the alarm information can be output, so that related personnel can timely process the abnormality of the BMC firmware.

Optionally, providing the compiling stage detection result and the testing stage detection result to a target user includes:

Generating a detection report of the target BMC firmware according to the compiling stage detection result, the performance test result, the monitoring data and the test stage detection result;

and providing the detection report to the target user.

According to the technical scheme of the embodiment of the invention, the detection report of the BMC firmware can be automatically generated according to the compiling stage detection result, the performance test result, the monitoring data and the testing stage detection result of the BMC firmware, and the detection report of the BMC firmware is provided for the target user, so that the target user can determine the detection condition of the BMC firmware.

According to another aspect of the present invention, there is provided a firmware detecting apparatus including:

the compiling detection module is used for detecting codes of the target BMC firmware through code detection scripts in a compiling stage of the target BMC firmware and determining a compiling stage detection result of the target BMC firmware;

the firmware testing module is used for performing performance testing on the target BMC firmware running in the testing server through a performance testing script in the testing stage of the target BMC firmware, and determining a performance testing result of the target BMC firmware;

the information monitoring module is used for monitoring the running state information of the target BMC firmware running in the test server through an information monitoring script in the performance test process to obtain the monitoring data of the target BMC firmware;

And the result providing module is used for determining a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result after the performance test process is finished, and providing the compiling stage detection result and the test stage detection result for a target user.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor;

and a memory communicatively coupled to the at least one processor;

wherein the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the firmware detection method according to any one of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement a firmware detection method according to any one of the embodiments of the present invention when executed.

According to the technical scheme, in the compiling stage of the target BMC firmware, codes of the target BMC firmware are detected through the code detection script, and the compiling stage detection result of the target BMC firmware is determined; in the test stage of the target BMC firmware, performing performance test on the target BMC firmware running in the test server through a performance test script, and determining a performance test result of the target BMC firmware; in the performance test process, monitoring the running state information of a target BMC firmware running in a test server through an information monitoring script to obtain monitoring data of the target BMC firmware; after the performance test process is finished, a test stage detection result of the target BMC firmware is determined according to the monitoring data and the performance test result, and the compiling stage detection result and the test stage detection result are provided for a target user, so that the problem that the BMC firmware cannot be detected comprehensively and accurately in the compiling stage and the test stage of the BMC firmware in the related technology is solved, the BMC firmware can be automatically detected in the compiling stage of the BMC firmware based on the code detection script, whether the BMC firmware is abnormal or not is determined, the performance detection and the information monitoring of the BMC firmware can be automatically performed in the compiling stage of the BMC firmware based on the performance test script and the information monitoring script, whether the BMC firmware is abnormal or not is determined, the BMC firmware can be detected comprehensively and accurately in the compiling stage and the test stage of the BMC firmware, whether the BMC firmware is abnormal or not is determined, and the efficiency and the accuracy of the detection process are improved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flowchart of a firmware detection method according to an embodiment of the present invention.

Fig. 2 is a flowchart of a firmware detection method according to a second embodiment of the present invention.

Fig. 3 is a flowchart of a firmware detection method according to a third embodiment of the present invention.

Fig. 4 is a schematic structural diagram of a firmware detecting apparatus according to a fourth embodiment of the present invention.

Fig. 5 is a schematic structural diagram of an electronic device implementing a firmware detection method according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "object," "first," "second," and the like in the description and the claims of the present invention and the above drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

Fig. 1 is a flowchart of a firmware detection method according to an embodiment of the present invention. The embodiment can be applied to detecting BMC firmware and determining whether the BMC firmware has an abnormal condition or not. The method may be performed by firmware detection means, which may be implemented in hardware and/or software, which may be configured in an electronic device. The electronic device is used for detecting BMC firmware. As shown in fig. 1, the method includes:

Step 101, in the compiling stage of the target BMC firmware, detecting the code of the target BMC firmware through a code detection script, and determining the compiling stage detection result of the target BMC firmware.

Alternatively, the target BMC firmware is BMC firmware that needs to be checked. The compiling stage of the target BMC firmware refers to a process that a developer of the target BMC firmware compiles source code of the target BMC firmware into instruction code. The test stage of the target BMC firmware refers to a process that a tester of the target BMC firmware tests various functions of the target BMC firmware.

Optionally, when the current time reaches a start time of a compilation stage of the target BMC firmware, the electronic device may determine that the compilation stage of the target BMC firmware starts, and the target BMC firmware is in the compilation stage. When the current time reaches the start time of the test phase of the target BMC firmware, the electronic device may determine that the test phase of the target BMC firmware starts, the target BMC firmware being in the test phase. The electronic device stores the compiling stage and the starting time of the testing stage of the target BMC firmware. The start time of the compilation stage of the target BMC firmware is the time at which the compilation stage begins, i.e., the time at which the developer begins compiling the source code of the target BMC firmware into instruction code. The start time of the test phase of the target BMC firmware is the time when the test phase starts, i.e. the time when the tester tests various functions of the target BMC firmware.

Optionally, when the current time reaches the start time of the compiling stage of the target BMC firmware, the electronic device determines that the target BMC firmware is in the compiling stage, and then detects the code of the target BMC firmware through a code detection script, to determine a compiling stage detection result of the target BMC firmware. In this way, in the compiling stage of the target BMC firmware, the code of the target BMC firmware is detected through the code detection script, and the compiling stage detection result of the target BMC firmware is determined.

Alternatively, in general, the presence of an exception to the target BMC firmware in the compile stage means that there is a static error in the code of the target BMC firmware. Static errors include, but are not limited to: syntax errors, parameter naming errors, and function call errors.

Optionally, the code detection script is a script that can be used to detect whether the code of the target BMC firmware has a static error after running, and generate a code detection result of the code. The code of the target BMC firmware refers to the source code of the target BMC firmware. The code detection script is stored in the electronic device. When the code detection script is executed, the operation of detecting whether the code of the target BMC firmware has a static error or not and generating a code detection result of the code is executed. The electronic equipment runs the code detection script, so that whether the code of the target BMC firmware has static errors or not is detected through the code detection script, and a code detection result of the code is generated.

Optionally, the code detection result of the code is information for characterizing whether the code has a static error. The code detection result of the code is that static errors exist or no static errors exist. The code detection result of the code is that the static error exists, which indicates that the code has the static error. The code detection result of the code is that no static error exists, which indicates that the code does not exist.

Optionally, the code detection script, when executed, performs the following operations: detecting whether a static error exists in a code of the target BMC firmware; if the static error exists in the code, determining the code detection result of the code as the static error; if the code is detected to have no static error, determining the code detection result of the code to have no static error.

Optionally, detecting the code of the target BMC firmware by a code detection script, and determining a compilation stage detection result of the target BMC firmware includes: acquiring codes of the target BMC firmware; detecting whether the code of the target BMC firmware has static errors or not through a code detection script, and generating a code detection result of the code; if the code detection result is that static errors exist, determining that the compiling stage detection result of the target BMC firmware is that the errors exist, outputting first alarm information, and stopping the current detection process.

Therefore, based on the code detection script, the BMC firmware can be automatically detected in the compiling stage of the BMC firmware, whether the BMC firmware is abnormal or not is determined, the abnormality of the BMC firmware can be found in time in the compiling stage of the BMC firmware, and alarm information can be output after the abnormality of the BMC firmware is determined, so that related personnel can process the abnormality of the BMC firmware in time.

Optionally, acquiring the code of the target BMC firmware includes: and acquiring the code of the target BMC firmware from the code database. The code database is a database for storing codes of BMC firmware. The code database stores the code of the target BMC firmware. The electronic device may obtain the code of the target BMC firmware from the code database.

Optionally, detecting, by a code detection script, whether a static error exists in a code of the target BMC firmware, and generating a code detection result of the code includes: running a code detection script, and executing the following operations through the code detection script: detecting whether static errors exist in codes of the target BMC firmware; if the static error exists in the code, determining that the code detection result of the code is the static error; and if the code is detected to have no static error, determining that the code detection result of the code has no static error.

Optionally, the compiling stage detection result of the target BMC firmware is information for characterizing whether the target BMC firmware in the compiling stage has an exception. The compiling stage detection result of the target BMC firmware is that the abnormality exists or the abnormality does not exist. And the compiling stage detection result of the target BMC firmware is that the target BMC firmware has an abnormality, which indicates that the target BMC firmware in the compiling stage has the abnormality. And the compiling stage detection result of the target BMC firmware shows that no abnormality exists, and the target BMC firmware in the compiling stage is indicated that no abnormality exists.

Optionally, if the code detection result is that there is a static error, which indicates that there is an abnormality in the target BMC firmware in the compiling stage, it may be determined that there is an abnormality in the compiling stage detection result of the target BMC firmware, the first alarm information is output, and the current detection process is stopped.

Optionally, the first alarm information is preset information for prompting that the target BMC firmware in the compiling stage has an abnormality. Outputting first alarm information, including: and sending the first alarm information to terminal equipment of a developer of the target BMC firmware so as to enable the developer of the target BMC firmware to timely process the abnormality of the BMC firmware. The developer of the target BMC firmware is the technician responsible for developing the target BMC firmware. The terminal device of the developer is a terminal device used by the developer.

Optionally, after the first alarm information is output, no subsequent operation step is performed, and it is determined that the current detection process of the target BMC firmware is finished, so that the current detection process of the target BMC firmware is stopped.

Optionally, after detecting whether the code of the target BMC firmware has a static error by the code detection script, generating a code detection result of the code, the method further includes: and if the code detection result is that the static error does not exist, determining that the compiling stage detection result of the target BMC firmware is that the abnormality does not exist.

Therefore, after detecting that the code of the BMC firmware does not have static errors, it can be determined that the BMC firmware in the compiling stage does not have anomalies, and a detection result of the BMC firmware in the compiling stage is generated.

Optionally, if the code detection result indicates that there is no static error, which indicates that there is no exception in the target BMC firmware in the compiling stage, it may be determined that there is no exception in the compiling stage detection result of the target BMC firmware.

Optionally, after determining that the result of the detection of the compiling stage of the target BMC firmware is that there is no abnormality, the electronic device stores the result of the detection of the compiling stage of the target BMC firmware in a local database.

Step 102, in the testing stage of the target BMC firmware, performing performance testing on the target BMC firmware running in the test server through a performance testing script, and determining a performance testing result of the target BMC firmware.

Optionally, when the current time reaches the start time of the test stage of the target BMC firmware, the electronic device determines that the target BMC firmware is in the test stage, and then performs performance test on the target BMC firmware running in the test server through a performance test script, so as to determine a performance test result of the target BMC firmware. In this way, in the test stage of the target BMC firmware, the performance test of the target BMC firmware running in the test server is performed through the performance test script, and the performance test result of the target BMC firmware is determined.

Optionally, performing performance test on the target BMC firmware running in the test server through a performance test script, and determining a performance test result of the target BMC firmware includes: the performance test script is sent to a test server, so that the test server performs performance test on target BMC firmware running in the test server according to the performance test script, determines a performance test result of the target BMC firmware, and feeds back the performance test result of the target BMC firmware; and acquiring a performance test result of the target BMC firmware fed back by the test server.

Therefore, based on the performance test script, the performance test of the BMC firmware can be automatically performed in the test stage of the BMC firmware, the performance test result of the BMC firmware is determined, whether the BMC firmware is abnormal or not can be conveniently determined according to the performance test result, and the abnormality of the BMC firmware can be timely found in the test stage of the BMC firmware.

Optionally, before the test phase of the target BMC firmware begins, a tester of the target BMC firmware may deploy the target BMC firmware in the BMC of the test server. The test server is a preset server. After the deployment process of the target BMC firmware is finished, the target BMC firmware runs in the BMC of the test server. The electronic equipment can establish communication connection with the test server according to a preset communication protocol, and information interaction is carried out based on the established communication connection.

Optionally, the performance test includes an overall test, an interface test, a stress test, and/or a response time test. The performance test scripts include an overall test script, an interface test script, a stress test script, and/or a response time test script. The performance test results include overall test results, interface test results, stress test results, and/or response time test results.

Alternatively, the overall test may refer to testing the integrity of the target BMC firmware to determine if the target BMC firmware contains the necessary subroutines. The whole test script is a script which can be used for testing the integrity of the target BMC firmware running in the server after running, determining whether the target BMC firmware contains necessary subroutines, and generating the whole test result of the target BMC firmware. The overall test script is stored in the electronic device. When the whole test script is run, the integrity of the target BMC firmware running in the server is tested, whether the target BMC firmware contains necessary subroutines is determined, and the operation of the whole test result of the target BMC firmware is generated.

Alternatively, the overall test result of the target BMC firmware is information that characterizes whether the target BMC firmware contains the necessary subroutines. The overall test result of the target BMC firmware is qualified or unqualified. And the overall test result of the target BMC firmware is qualified, which indicates that the target BMC firmware contains necessary subroutines. The overall test result of the target BMC firmware is failed, which indicates that the target BMC firmware does not contain necessary subroutines.

Optionally, the overall test script, when executed, performs the following operations: testing the integrity of a target BMC firmware running in a server to determine whether the target BMC firmware contains necessary subroutines; if the target BMC firmware contains necessary subroutines, determining that the overall test result of the target BMC firmware is qualified; if the target BMC firmware does not contain the necessary subprogram, determining that the overall test result of the target BMC firmware is unqualified.

Optionally, the interface test may refer to testing the function of the interface of the target BMC firmware to determine whether the function of the interface is normal. The interface test script is a script which can be used for testing the function of the interface of the target BMC firmware operated in the server after operation, determining whether the function of the interface is normal, and generating the interface test result of the target BMC firmware. The interface test script is stored in the electronic device. When the interface test script is run, the function of the interface of the target BMC firmware running in the server is tested, whether the function of the interface is normal is determined, and the operation of the interface test result of the target BMC firmware is generated.

Optionally, the interface test result of the target BMC firmware is information for characterizing whether the function of the interface of the target BMC firmware is normal. And the interface test result of the target BMC firmware is qualified or unqualified. And the interface test result of the target BMC firmware is qualified, which indicates that the function of the interface of the target BMC firmware is normal. And the interface test result of the target BMC firmware is unqualified, which indicates that the function of the interface of the target BMC firmware is abnormal.

Optionally, the interface test script, when executed, performs the following operations: testing the function of an interface of a target BMC firmware running in a server to determine whether the function of the interface is normal; if the function of the interface of the target BMC firmware is normal, determining that the interface test result of the target BMC firmware is qualified; if the function of the interface of the target BMC firmware is abnormal, determining that the interface test result of the target BMC firmware is unqualified.

Optionally, the pressure test may be a test of a maximum amount of data that can be received by the interface of the target BMC firmware, to determine whether the maximum amount of data that can be received by the interface of the target BMC firmware is within a preset data amount range. The pressure test script is a script which can be used for testing the maximum data volume which can be received by the interface of the target BMC firmware operated in the server after operation, determining whether the maximum data volume which can be received by the interface of the target BMC firmware is within a preset data volume range, and generating a pressure test result of the target BMC firmware. The stress test script is stored in the electronic device. When the pressure test script is run, the operation of testing the maximum data volume which can be received by the interface of the target BMC firmware running in the server, determining whether the maximum data volume which can be received by the interface of the target BMC firmware is within a preset data volume range, and generating a pressure test result of the target BMC firmware is executed.

Optionally, the pressure test result of the target BMC firmware is information for characterizing whether the maximum data amount that the interface of the target BMC firmware can receive is within a preset data amount range. And the pressure test result of the target BMC firmware is qualified or unqualified. And the pressure test result of the target BMC firmware is qualified, which indicates that the maximum data size which can be received by the interface of the target BMC firmware is within the preset data size range. And the pressure test result of the target BMC firmware is unqualified, which indicates that the maximum data volume which can be received by the interface of the target BMC firmware is not within the preset data volume range.

Optionally, the stress test script, when executed, performs the following operations: testing the maximum data volume which can be received by the interface of the target BMC firmware running in the server, and determining whether the maximum data volume which can be received by the interface of the target BMC firmware is within a preset data volume range; if the maximum data size which can be received by the interface of the target BMC firmware is within the preset data size range, determining that the pressure test result of the target BMC firmware is qualified; if the maximum data size which can be received by the interface of the target BMC firmware is not in the preset data size range, determining that the pressure test result of the target BMC firmware is unqualified.

Optionally, the response time test may be a test of the response time of the target BMC firmware to the received control command, to determine whether the response time of the target BMC firmware to the received control command is within a preset time range. The response time test script is a script which can be used for testing the response time of the received control instruction of the target BMC firmware running in the server after running, determining whether the response time of the received control instruction of the target BMC firmware is within a preset time range, and generating a response time test result of the target BMC firmware. The response time test script is stored in the electronic device. When the response time test script is executed, the target BMC firmware running in the server is executed to test the response time of the received control instruction, whether the response time of the target BMC firmware is within a preset time range is determined, and the operation of the response time test result of the target BMC firmware is generated.

Optionally, the response time test result of the target BMC firmware is information for characterizing whether the response time of the target BMC firmware to the received control command is within a preset time range. And the response time test result of the target BMC firmware is qualified or unqualified. And the response time test result of the target BMC firmware is qualified, which indicates that the response time of the target BMC firmware to the received control instruction is within a preset time range. And the response time test result of the target BMC firmware is unqualified, which indicates that the response time of the target BMC firmware to the received control instruction is not within the preset time range.

Optionally, the response time test script, when executed, performs the following operations: testing the response time of the received control instruction by the target BMC firmware running in the server, and determining whether the response time of the received control instruction by the target BMC firmware is within a preset time range; if the response time of the target BMC firmware to the received control instruction is within the preset time range, determining that the response time test result of the target BMC firmware is qualified; if the response time of the target BMC firmware to the received control instruction is not within the preset time range, determining that the response time test result of the target BMC firmware is unqualified.

Optionally, the electronic device sends the integrated test script, the interface test script, the pressure test script and the response time test script to the test server, so that the test server tests the target BMC firmware running in the test server according to the integrated test script, the interface test script, the pressure test script and the response time test script, and determines an integrated test result, an interface test result, a pressure test result and a response time test result.

Optionally, the electronic device sends the overall test script, the interface test script, the stress test script, and the response time test script to the test server. After receiving the whole test script, the interface test script, the pressure test script and the response time test script, the test server executes the following operations: running an integral test script, so that the integrity of a target BMC firmware running in a test server is tested through the integral test script, whether the target BMC firmware contains necessary subroutines is determined, and an integral test result of the target BMC firmware is generated; the identification information of the integral test and the integral test result of the target BMC firmware are sent to the electronic equipment, so that the integral test result of the target BMC firmware is fed back to the electronic equipment; operating an interface test script, so that the function of an interface of a target BMC firmware operated in a test server is tested through the interface test script, whether the function of the interface is normal is determined, and an interface test result of the target BMC firmware is generated; the identification information of the interface test and the interface test result of the target BMC firmware are sent to the electronic equipment, so that the interface test result of the target BMC firmware is fed back to the electronic equipment; operating a pressure test script, so that the maximum data volume which can be received by an interface of a target BMC firmware operated in a test server is tested through the pressure test script, determining whether the maximum data volume which can be received by the interface of the target BMC firmware is within a preset data volume range, and generating a pressure test result of the target BMC firmware; the identification information of the pressure test and the pressure test result of the target BMC firmware are sent to the electronic equipment, so that the pressure test result of the target BMC firmware is fed back to the electronic equipment; running a response time test script, so that the response time of a received control instruction is tested by a target BMC firmware running in a test server through the response time test script, whether the response time of the target BMC firmware is within a preset time range or not is determined, and a response time test result of the target BMC firmware is generated; and sending the identification information of the response time test and the response time test result of the target BMC firmware to the electronic equipment, so that the response time test result of the target BMC firmware is fed back to the electronic equipment.

Optionally, the electronic device receives the overall test identification information and the overall test result of the target BMC firmware, the interface test identification information and the interface test result of the target BMC firmware, the pressure test identification information and the pressure test result of the target BMC firmware, the response time test identification information and the response time test result of the target BMC firmware, which are sent by the test server, and correspondingly stores the above information into the local database. The identification information of the whole test may be a number or a character string for identifying the whole test. The identification information of the interface test may be a number or a character string for identifying the interface test. The identification information of the stress test may be a number or a character string for identifying the stress test. The identification information of the response time test may be a number or a character string for identifying the response time test.

And 103, monitoring the running state information of the target BMC firmware running in the test server through an information monitoring script in the performance test process to obtain the monitoring data of the target BMC firmware.

Optionally, in the performance test process, the information monitoring script monitors the running state information of the target BMC firmware running in the test server to obtain the monitoring data of the target BMC firmware, including: after a performance test script is sent to a test server, determining that a performance test process of a target BMC firmware starts, and monitoring running state information of the target BMC firmware running in the test server through an information monitoring script to obtain monitoring data of the target BMC firmware; after the performance test result of the target BMC firmware fed back by the test server is obtained, determining that the performance test process of the target BMC firmware is finished, and stopping monitoring the running state information of the target BMC firmware running in the test server through an information monitoring script to obtain the monitoring data of the target BMC firmware.

Optionally, the information monitoring script is a script that can be used to monitor the running state information of the target BMC firmware running in the test server after running, so as to obtain the monitoring data of the target BMC firmware. The information monitoring script is stored in the electronic device. When the information monitoring script is operated, the operation of monitoring the operation state information of the target BMC firmware operated in the test server to obtain the monitoring data of the target BMC firmware is executed. The electronic equipment runs the information monitoring script, so that the running state information of the target BMC firmware running in the test server is monitored through the information monitoring script, and the monitoring data of the target BMC firmware are obtained.

Optionally, the running state information of the target BMC firmware includes a memory space capacity, a number of processor cores, and/or a number of file handles of the target BMC firmware. The memory space capacity of the target BMC firmware may be the capacity of the memory space used by the target BMC firmware. The number of processor cores of the target BMC firmware is the number of processing cores of the central processor used by the target BMC firmware. The number of file handles of the target BMC firmware is the number of file handles used by the target BMC firmware. Monitoring the running state information of the target BMC firmware running in the test server to obtain the monitoring data of the target BMC firmware, wherein the monitoring data comprises the following steps: according to a preset time interval, acquiring the running state information of a target BMC firmware running in the test server from the test server at regular time; and determining the acquired running state information as monitoring data of the target BMC firmware, and storing the monitoring data into a local database. When the information monitoring script is executed, the following operations are performed: according to a preset time interval, acquiring the running state information of a target BMC firmware running in the test server from the test server at regular time; and determining the acquired running state information as monitoring data of the target BMC firmware, and storing the monitoring data into a local database. The preset time interval is a preset time interval. The preset time interval may be set according to the service requirement. The preset time interval is, for example, 30 seconds.

Optionally, the monitoring, by an information monitoring script, the running state information of the target BMC firmware running in the test server, to obtain the monitoring data of the target BMC firmware, including: running an information monitoring script, and executing the following operations through the information monitoring script: according to a preset time interval, acquiring the running state information of a target BMC firmware running in the test server from the test server at regular time; and determining the acquired running state information as monitoring data of the target BMC firmware, and storing the monitoring data into a local database.

Optionally, after the performance test process of the target BMC firmware is determined to start, starting to run an information monitoring script, so that the running state information of the target BMC firmware running in the test server is monitored through the information monitoring script, and the monitoring data of the target BMC firmware are obtained. And stopping running the information monitoring script after the performance test process of the target BMC firmware is determined to be finished, so that the running state information of the target BMC firmware running in the test server is stopped to be monitored through the information monitoring script, and the monitoring data of the target BMC firmware are obtained.

And 104, after the performance test process is finished, determining a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result, and providing the compiling stage detection result and the test stage detection result for a target user.

Optionally, the test phase detection result of the target BMC firmware is information for characterizing whether the target BMC firmware in the test phase has an abnormality. The detection result of the test stage of the target BMC firmware is that the abnormality exists or the abnormality does not exist. And the detection result of the test stage of the target BMC firmware is that the abnormality exists, which indicates that the abnormality exists in the target BMC firmware in the test stage. And the detection result of the testing stage of the target BMC firmware shows that no abnormality exists, and the target BMC firmware in the testing stage is indicated that no abnormality exists.

Alternatively, in general, the presence of an exception to the target BMC firmware in the test phase refers to an abnormal performance of the target BMC firmware or an abnormal running state of the target BMC firmware. If the performance of the target BMC firmware is abnormal, the performance test result of the target BMC firmware is unqualified. If the target BMC firmware is in an abnormal running state, the running state information of the target BMC firmware is larger than a corresponding threshold value.

Optionally, determining a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result includes: performing anomaly detection on the monitoring data and the performance test result; and determining a test stage detection result of the target BMC firmware according to the abnormality detection result.

Therefore, after performance test and running state information monitoring are carried out on the BMC firmware running in the test server, whether the BMC firmware in the test stage is abnormal or not can be automatically determined based on the monitoring data and the performance test result, and the abnormal situation of the BMC firmware can be found in time in the test stage of the BMC firmware.

Optionally, the monitoring data includes running state information of all target BMC firmware acquired during the performance test. The running state information of the target BMC firmware includes memory space capacity, the number of processor cores and/or the number of file handles of the target BMC firmware. When the running state information of the target BMC firmware is detected to be larger than the corresponding information threshold value, the target BMC firmware can be determined to be in an abnormal running state, and the target BMC firmware in the compiling stage is abnormal. The running state information being greater than the corresponding information threshold may refer to the memory space capacity being greater than a preset capacity threshold, may refer to the number of processor cores being greater than a preset core number threshold, and may refer to the number of file handles being greater than a preset handle number threshold.

Optionally, the preset capacity threshold is a preset value. When the target BMC firmware is in a normal running state, the memory space capacity of the target BMC firmware needs to be smaller than or equal to a preset capacity threshold. If the memory space capacity of the target BMC firmware is detected to be larger than the preset capacity threshold, the target BMC firmware can be determined to be in an abnormal running state. The predetermined core number threshold is a predetermined value. When the target BMC firmware is in a normal running state, the number of processor cores of the target BMC firmware needs to be smaller than or equal to a preset capacity threshold. If the number of processor cores of the target BMC firmware is detected to be larger than the preset core number threshold, the target BMC firmware can be determined to be in an abnormal running state. The preset handle number threshold is a preset value. When the target BMC firmware is in a normal running state, the number of file handles of the target BMC firmware needs to be smaller than or equal to a preset handle number threshold value. If the number of file handles of the target BMC firmware is detected to be larger than the preset handle number threshold value, the target BMC firmware can be determined to be in an abnormal running state.

Optionally, the anomaly detection result of the monitoring data is information for characterizing whether the target BMC firmware is in an abnormal running state. The abnormal detection result of the monitoring data is abnormal or normal. And the abnormal detection result of the monitoring data is abnormal, which indicates that the target BMC firmware is in an abnormal running state. And the abnormal detection result of the monitoring data is normal, which indicates that the target BMC firmware is not in an abnormal running state.

Optionally, the detecting the abnormality of the monitoring data includes: detecting whether the capacity of each memory space in the monitoring data is larger than a preset capacity threshold, whether the number of cores of each processor in the monitoring data is larger than a preset core number threshold, and whether the number of handles of each file in the monitoring data is larger than a preset handle number threshold; if one or more memory space capacities in the monitoring data are detected to be larger than a preset capacity threshold value, indicating that the target BMC firmware is in an abnormal running state, determining that an abnormal detection result of the monitoring data is abnormal; if one or more processor cores in the monitoring data are detected to be greater than a preset core number threshold value, indicating that the target BMC firmware is in an abnormal running state, determining that an abnormal detection result of the monitoring data is abnormal; if one or more file handles in the monitoring data are detected to be greater than a preset handle number threshold value, indicating that the target BMC firmware is in an abnormal running state, determining that an abnormal detection result of the monitoring data is abnormal; if all the memory space capacity in the monitoring data is detected to be smaller than or equal to a preset capacity threshold, the number of cores of all the processors in the monitoring data is smaller than or equal to a preset core number threshold, and the number of handles of all the files in the monitoring data is smaller than or equal to a preset handle number threshold, which indicates that the target BMC firmware is not in an abnormal running state, determining that an abnormal detection result of the monitoring data is normal.

Optionally, the performance test results include overall test results, interface test results, stress test results, and/or response time test results. And when the performance test result is detected to be unqualified, determining that the performance of the target BMC firmware is abnormal, wherein the target BMC firmware in the test stage is abnormal.

Optionally, the anomaly detection result of the performance test result is information for characterizing whether the performance of the target BMC firmware is anomalous. The abnormality detection result of the performance test result is abnormal or normal. And the abnormality detection result of the performance test result is abnormality, which indicates that the performance of the target BMC firmware is abnormal. And the abnormal detection result of the performance test result is normal, which indicates that the performance of the target BMC firmware is normal.

Optionally, performing anomaly detection on the performance test result includes: detecting whether the overall test result, the interface test result, the pressure test result and the response time test result in the performance test result are unqualified or not; if the overall test result, the interface test result, the pressure test result or the response time test result in the detection performance test result is unqualified, and the performance of the target BMC firmware is abnormal, determining that the abnormal detection result of the performance test result is abnormal; if the overall test result, the interface test result, the pressure test result and the response time test result in the test performance test result are all qualified, the performance of the target BMC firmware is normal, and the abnormal test result of the performance test result is determined to be normal.

Optionally, determining the test stage detection result of the target BMC firmware according to the anomaly detection result includes: if the abnormality detection result of the monitoring data is abnormality or the abnormality detection result of the performance test result is abnormality, indicating that the target BMC firmware is in an abnormal running state or the performance of the target BMC firmware is abnormal, determining that the detection result of the target BMC firmware in the test stage is abnormal; if the abnormal detection result of the monitoring data is normal and the abnormal detection result of the performance test result is normal, which indicates that the target BMC firmware is not in an abnormal running state and the performance of the target BMC firmware is normal, the target BMC firmware in the test stage is not abnormal, and the test stage detection result of the target BMC firmware is determined to be that the target BMC firmware is not abnormal.

Optionally, after determining the test stage detection result of the target BMC firmware according to the anomaly detection result, the method further includes: and if the detection result in the test stage is that the abnormality exists, outputting second alarm information.

Therefore, after the target BMC firmware in the test stage is determined to have an abnormality, alarm information can be output, so that related personnel can timely process the abnormality of the BMC firmware.

Optionally, the second alarm information is preset information for prompting that the target BMC firmware in the test stage has an abnormality. Outputting the second alarm information, including: and sending the second alarm information to terminal equipment of a tester of the target BMC firmware so as to enable the tester of the target BMC firmware to timely process the abnormality of the BMC firmware. The tester of the target BMC firmware is the technician responsible for managing the performance test procedure of the target BMC firmware. The terminal device of the tester is the terminal device used by the tester.

Optionally, providing the compiling stage detection result and the testing stage detection result to a target user includes: generating a detection report of the target BMC firmware according to the compiling stage detection result, the performance test result, the monitoring data and the test stage detection result; and providing the detection report to the target user.

Therefore, the detection report of the BMC firmware can be automatically generated according to the compiling stage detection result, the performance test result, the monitoring data and the testing stage detection result of the BMC firmware, and the detection report of the BMC firmware is provided for the target user, so that the target user can determine the detection condition of the BMC firmware.

Alternatively, the detection report of the target BMC firmware may be a table storing the compiling stage detection result, the performance test result, the monitoring data, and the test stage detection result of the target BMC firmware. Generating a detection report of the target BMC firmware according to the compiling stage detection result, the performance test result, the monitoring data and the test stage detection result, wherein the detection report comprises the following steps: and filling the compiling stage detection result, the performance test result, the monitoring data and the testing stage detection result into a preset form to obtain a detection report of the target BMC firmware. The preset table is a preset table for storing a compiling stage detection result, a performance test result, monitoring data and a testing stage detection result of the target BMC firmware. The preset table is provided with a cell used for filling out a compiling stage detection result of the target BMC firmware, a cell used for filling out a performance test result of the target BMC firmware, a cell used for filling out monitoring data of the target BMC firmware and a cell used for filling out a testing stage detection result of the target BMC firmware. And filling the compiling stage detection result, the performance test result, the monitoring data and the testing stage detection result into corresponding cells so as to obtain a detection report of the target BMC firmware.

Optionally, providing the detection report to the target user includes: and sending the detection report to the terminal equipment of the target user. The target user may be a developer and tester of the target BMC firmware.

Example two

Fig. 2 is a flowchart of a firmware detection method according to a second embodiment of the present invention. Embodiments of the invention may be combined with various alternatives to one or more of the embodiments described above. As shown in fig. 2, the method includes:

step 201, in a compiling stage of the target BMC firmware, acquiring a code of the target BMC firmware.

Step 202, detecting whether a static error exists in the code of the target BMC firmware through the code detection script, and generating a code detection result of the code: if the code detection result is that there is a static error, step 203 is executed; if the code detection result is that there is no static error, step 204 is performed.

And 203, determining that the compiling stage detection result of the target BMC firmware is abnormal, outputting first alarm information, and stopping the current detection process.

Step 204, determining that the compiling stage detection result of the target BMC firmware is that no abnormality exists.

In step 205, in the testing stage of the target BMC firmware, performance testing is performed on the target BMC firmware running in the test server through the performance test script, so as to determine a performance test result of the target BMC firmware.

And 206, monitoring the running state information of the target BMC firmware running in the test server through the information monitoring script in the performance test process to obtain the monitoring data of the target BMC firmware.

Step 207, after the performance testing process is finished, determining a testing stage detection result of the target BMC firmware according to the monitoring data and the performance testing result, and providing the compiling stage detection result and the testing stage detection result to the target user.

According to the technical scheme, the BMC firmware can be automatically detected in the compiling stage of the BMC firmware based on the code detection script, whether the BMC firmware is abnormal or not is determined, the abnormal BMC firmware can be conveniently found in time in the compiling stage of the BMC firmware, the performance detection and the information monitoring of the BMC firmware can be automatically carried out in the compiling stage of the BMC firmware based on the performance test script and the information monitoring script, whether the BMC firmware is abnormal or not is determined, and alarm information can be output after the abnormal BMC firmware is determined to be abnormal, so that related personnel can timely process the abnormal BMC firmware.

Example III

Fig. 3 is a flowchart of a firmware detection method according to a third embodiment of the present invention, including the following steps:

step 301, in a compiling stage of the target BMC firmware, acquiring a code of the target BMC firmware.

Step 302, detecting whether a static error exists in the code of the target BMC firmware through the code detection script, and generating a code detection result of the code: if the code detection result is that there is a static error, step 303 is executed; if the code detection result is that there is no static error, step 304 is performed.

Step 303, determining that the compiling stage detection result of the target BMC firmware is abnormal, outputting first alarm information, and stopping the current detection process.

Step 304, determining that the compiling stage detection result of the target BMC firmware is that no abnormality exists.

In step 305, in the testing stage of the target BMC firmware, performance testing is performed on the target BMC firmware running in the test server through the performance test script, so as to determine the performance test result of the target BMC firmware.

And 306, monitoring the running state information of the target BMC firmware running in the test server through the information monitoring script in the performance test process to obtain the monitoring data of the target BMC firmware.

Step 307, after the performance test process is finished, performing anomaly detection on the monitoring data and the performance test result.

And 308, determining a test stage detection result of the target BMC firmware according to the abnormality detection result.

And 309, generating a detection report of the target BMC firmware according to the compiling stage detection result, the performance test result, the monitoring data and the testing stage detection result.

Step 310, providing the detection report to the target user.

According to the technical scheme, the performance test can be automatically performed on the BMC firmware in the test stage of the BMC firmware based on the performance test script, the performance test result of the BMC firmware is determined, the running state information of the BMC firmware can be automatically monitored in the performance test process based on the information monitoring script, whether the BMC firmware in the test stage is abnormal or not can be automatically determined based on the monitoring data and the performance test result after the performance test and the information monitoring are performed on the BMC firmware, so that the abnormality of the BMC firmware can be conveniently found in time in the test stage of the BMC firmware, a detection report of the BMC firmware can be automatically generated according to the compiling stage detection result, the performance test result, the monitoring data and the test stage detection result of the BMC firmware, and the detection report of the BMC firmware is provided for a target user, so that the target user can determine the detection condition of the BMC firmware.

Example IV

Fig. 4 is a schematic structural diagram of a firmware detecting apparatus according to a fourth embodiment of the present invention. The apparatus may be configured in an electronic device. As shown in fig. 4, the apparatus includes: a compile detection module 401, a firmware test module 402, an information monitoring module 403, and a result providing module 404.

The compiling detection module 401 is configured to detect, in a compiling stage of a target BMC firmware, a code of the target BMC firmware through a code detection script, and determine a compiling stage detection result of the target BMC firmware; the firmware test module 402 is configured to perform a performance test on a target BMC firmware running in a test server through a performance test script in a test stage of the target BMC firmware, to determine a performance test result of the target BMC firmware; the information monitoring module 403 is configured to monitor, in a performance test process, operation state information of a target BMC firmware running in the test server through an information monitoring script, to obtain monitoring data of the target BMC firmware; and the result providing module 404 is configured to determine a test stage detection result of the target BMC firmware according to the monitoring data and the performance test result after the performance test process is finished, and provide the compiling stage detection result and the test stage detection result to a target user.

In an optional implementation manner of the embodiment of the present invention, optionally, when executing the operation of detecting the code of the target BMC firmware by the code detection script and determining the result of the compilation stage detection of the target BMC firmware, the compilation detection module 401 is specifically configured to: acquiring codes of the target BMC firmware; detecting whether the code of the target BMC firmware has static errors or not through a code detection script, and generating a code detection result of the code; if the code detection result is that static errors exist, determining that the compiling stage detection result of the target BMC firmware is that the errors exist, outputting first alarm information, and stopping the current detection process.

In an optional implementation of the embodiment of the present invention, optionally, the compiling detection module 401 is further configured to: and if the code detection result is that the static error does not exist, determining that the compiling stage detection result of the target BMC firmware is that the abnormality does not exist.

In an optional implementation manner of the embodiment of the present invention, optionally, when executing performance test on a target BMC firmware running in a test server through a performance test script, the firmware test module 402 is specifically configured to: the performance test script is sent to a test server, so that the test server performs performance test on target BMC firmware running in the test server according to the performance test script, determines a performance test result of the target BMC firmware, and feeds back the performance test result of the target BMC firmware; and acquiring a performance test result of the target BMC firmware fed back by the test server.

In an optional implementation manner of the embodiment of the present invention, optionally, when executing performance test on a target BMC firmware running in a test server through a performance test script, the result providing module 404 is specifically configured to: performing anomaly detection on the monitoring data and the performance test result; and determining a test stage detection result of the target BMC firmware according to the abnormality detection result.

In an optional implementation of the embodiment of the present invention, optionally, the result providing module 404 is further configured to: and if the detection result in the test stage is that the abnormality exists, outputting second alarm information.

In an optional implementation manner of the embodiment of the present invention, optionally, the result providing module 404 is specifically configured to, when performing an operation of providing the compiling stage detection result and the testing stage detection result to the target user: generating a detection report of the target BMC firmware according to the compiling stage detection result, the performance test result, the monitoring data and the test stage detection result; and providing the detection report to the target user.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

The firmware detection device can execute the firmware detection method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the firmware detection method.

Example five

Fig. 5 shows a schematic diagram of an electronic device 10 that may be used to implement the firmware detection method of an embodiment of the present invention. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program built into the Random Access Memory (RAM) 13 from the storage unit 18. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the respective methods and processes described above, such as a firmware detection method.

In some embodiments, the firmware detection method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When a computer program is built into RAM 13 and executed by processor 11, one or more steps of the firmware detection method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the firmware detection method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

The computer program for implementing the firmware detection method of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A firmware detection method, comprising:

2. The firmware detection method as claimed in claim 1, wherein detecting the code of the target BMC firmware by a code detection script, determining a compilation stage detection result of the target BMC firmware, comprises:

acquiring codes of the target BMC firmware;

3. The firmware detection method as claimed in claim 2, further comprising, after detecting whether a static error exists in the code of the target BMC firmware by a code detection script, generating a code detection result of the code:

4. The firmware detection method as claimed in claim 1, wherein the determining the performance test result of the target BMC firmware by performing a performance test on the target BMC firmware running in the test server through a performance test script comprises:

5. The firmware detection method according to claim 1, wherein determining a test phase detection result of the target BMC firmware according to the monitoring data and the performance test result comprises:

6. The firmware detection method as claimed in claim 5, further comprising, after determining the test phase detection result of the target BMC firmware according to the abnormality detection result:

7. The firmware detection method according to claim 1, wherein providing the compiling stage detection result and the testing stage detection result to a target user includes:

and providing the detection report to the target user.

8. A firmware detection apparatus, comprising:

9. An electronic device, the electronic device comprising:

at least one processor;

and a memory communicatively coupled to the at least one processor;

wherein the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the firmware detection method of any one of claims 1-7.

10. A computer readable storage medium storing computer instructions for causing a processor to implement the firmware detection method of any one of claims 1-7 when executed.