CN112463466A - Computer testing method - Google Patents
Computer testing method Download PDFInfo
- Publication number
- CN112463466A CN112463466A CN201910846087.7A CN201910846087A CN112463466A CN 112463466 A CN112463466 A CN 112463466A CN 201910846087 A CN201910846087 A CN 201910846087A CN 112463466 A CN112463466 A CN 112463466A
- Authority
- CN
- China
- Prior art keywords
- test
- computer
- firmware
- version information
- bios
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a computer test method, which is suitable for testing a computer and comprises the steps of setting a first group of firmware and version information of the first group of firmware, performing first updating by using the first group of firmware, writing the version information of the first group of firmware into a nonvolatile memory of a test computer when the first updating is successful, performing first information comparison on the version information of the first group of firmware and the version information of the corresponding firmware stored in the nonvolatile memory, executing a pre-boot execution environment program, performing second updating by using a second group of firmware obtained by executing the pre-boot execution environment program, writing the version information of the second group of firmware into the nonvolatile memory when the second updating is successful, and performing second information comparison on the version information of the second group of firmware and the version information of the corresponding firmware stored in the nonvolatile memory.
Description
Technical Field
The present invention relates to a computer test method, and more particularly, to a computer test method for updating a plurality of Basic Input Output Systems (BIOS) of different versions.
Background
The Basic Input Output System (BIOS) is the firmware that executes hardware initialization and provides runtime services for operating systems and programs in a computer System during a power-on boot phase. The BIOS is the most basic firmware of a computer system during loading, and has the main functions of performing a Power On Self Test (POST) during booting to initialize hardware devices in the computer system, testing whether the states of the hardware devices are normal, loading a boot program from a mass storage device such as a hard disk, and loading the boot program into an operating system. The program code of the BIOS is usually stored in a Nonvolatile Memory (Nonvolatile Memory) of a motherboard of the computer system.
The computer will change the hardware device initialization due to the different customer requirements, and the BIOS firmware code needs to be modified, so as to derive many BIOS firmware codes with different versions. In addition, computer system manufacturers often perform BIOS version adjustment and upgrade/downgrade stress testing for computer system performance requirements and stability. If the tester must manually perform the cycle update and the boot verification of the BIOS with different versions, it can only determine whether the BIOS firmware code of the version is stable, and continuously verify the BIOS firmware during the update process of the BIOS with different versions, a large amount of human resources will be consumed. Therefore, how to make the computer system execute updating of different versions of BIOS by itself, execute testing of different versions of BIOS by itself, and notify the system administrator in real time when an error occurs is a problem to be solved in the BIOS updating technology.
Disclosure of Invention
The embodiment provides a computer test method, which comprises the steps of setting a first group of firmware and version information of the first group of firmware included in the BIOS update of a test computer, using the first group of firmware to carry out the first update of the BIOS by the test computer, writing the version information of the first group of firmware into a nonvolatile memory of the test computer when the first update is successful, comparing the version information of the first group of firmware with the version information of the corresponding firmware stored in the nonvolatile memory by the test computer, executing a pre-boot execution environment program by the test computer, using a second group of firmware obtained by executing the pre-boot execution environment program to carry out the second update of the BIOS, writing the version information of the second group of firmware into the nonvolatile memory when the second update is successful, and carrying out the second communication by the test computer on the version information of the second group of firmware and the version information of the corresponding firmware stored in the nonvolatile memory And (6) comparing.
Drawings
FIG. 1 is a system architecture diagram illustrating a computer testing method according to an embodiment.
FIG. 2 is a diagram of an embodiment software interface program.
FIG. 3 is a flowchart illustrating a computer testing method according to an embodiment.
FIG. 4 is a diagram of an embodiment pre-boot execution environment.
FIG. 5 is a flowchart illustrating an exemplary BIOS automatic test.
FIG. 6 is a diagram illustrating an embodiment of generating BIOS automatic test items for a batch file.
Description of the symbols:
1 computer test system
101 to 103 test computers
104 local area network
105 server
106 to 108 nonvolatile memories
110 system manager
201 software interface program
202 to 209 firmware names
212 to 219 firmware version number
220 testing computer name
230 BIOS version information
231 BIOS software
300 computer test method
S302 to S316
401 first request
402 DHCP server
403 first response
404 second request
405 TFTP Server
406 second response
500 BIOS automatic test flow
502 Normal Power supply mode of external Power supply System
504 low power mode of external power system
506 external power system standby mode
508 external power system sleep mode
510 normal power mode for internal battery system
512 internal battery system low power mode
514 internal battery system standby mode
517 sleep mode of internal battery system
602 files
604 preset test items for diagnostic routines
606 safely updated preset test items
608 management Engine Preset test items
620 batch files
630 BIOS automatic test items
SVN sub-version management system
Detailed Description
Fig. 1 is a system architecture diagram of a computer test system 1 according to an embodiment of the present invention. The test computers 101-103 may be connected to the server 105 through a local area network 104. The test computers 101 to 103 can automatically execute the updating of the BIOS of different versions and the testing of the BIOS of different versions according to the setting of the BIOS updating and/or the Execution of the Preboot Execution Environment (PXE) program, and can notify the System administrator 110 through the local area network 104 and the server 105 in real time when an error occurs.
Test computers 101-103 may include non-volatile memories 106-108, respectively. The non-volatile memories 106 to 108 may be Read Only Memories (ROMs), Programmable Read Only Memories (PROMs), Electrically Erasable Programmable Read-Only memories (EEPROMs), or Flash memories (Flash memories). Server 105 may include a program code management system (e.g., a subversion control System (SVN)). The server 105 and/or the test computers 101-103 may include a software Interface Application (User Interface Application). The system administrator 110 can individually set version information of the first set of firmware corresponding to the testing computers 101 to 103 on the software interface program 201, where the version information of the first set of firmware includes a firmware name and a corresponding firmware version number. In one embodiment, the system administrator 110 uses the software interface 201 to enter the test computer 101 and the firmware name and firmware version number. As shown in FIG. 2, the software interface program 201 can receive the updated test computer name 220, the firmware names 202 to 209, and the corresponding firmware version numbers 212 to 219. The software interface program 201 may generate BIOS version information 230, which may include the firmware names 202-209 and firmware version numbers 212-219 contained in the generated BIOS. The software interface 201 may use the code management system and generate the BIOS software 231 based on the BIOS version information 230. In one embodiment, the software interface 201 sends the instruction including the BIOS version information 230 to the code management system, which generates the BIOS software 231 according to the BIOS version information 230 and transmits the BIOS software 231 to the corresponding testing computers 101 to 103. The BIOS software 231 includes a first set of firmware corresponding to firmware names 202 through 209 and respective firmware version numbers 212 through 219.
The test computers 101 to 103 can use the respective first set of firmware to perform the first update of the BIOS, and then the server 105 can receive the result of the first update of the test computers 101 to 103 and notify the system administrator 110. When the test computers 101 to 103 execute the first update of the BIOS according to the respective first set of firmware, the test computers 101 to 103 may update the respective first set of firmware into the non-volatile memories 106 to 108. When all the first set of firmware of the test computers 101, 102, 103 are successfully updated to the non-volatile memories 106, 107, 108, the first update of the test computers 101, 102, 103 is successful, and the test computers 101, 102, 103 with the first update success can write the version information of the respective first set of firmware into the non-volatile memories 106, 107, 108. When at least one of the first set of firmware of the test computers 101 to 103 is not successfully updated to the non-volatile memories 106 to 108, the corresponding first update fails, and the test computers 101, 102, 103 that failed the first update will not write the version information of the firmware that failed to be updated in the version information of the first set of firmware into the non-volatile memories 106, 107, 108, and will only write the version information of the firmware that was successfully updated into the non-volatile memories 106, 107, 108, so that the non-volatile memories 106, 107, 108 still retain at least a part of the BIOS version information of the previous BIOS. For example, if the first set of firmware of the test computer 101 includes 5 firmware, and 3 of the 5 firmware are successfully updated and 2 firmware are failed to be updated, the test computer 101 may write the version information of the 3 successfully updated firmware into the non-volatile memory 106 and not write the version information of the 2 failed firmware into the non-volatile memory 106. The testing computers 101 to 103 may perform a first information comparison between the version information of the respective first set of firmware and the version information of the corresponding firmware stored in the non-volatile memories 106 to 108, and if the version information of the respective first set of firmware and the version information of the corresponding firmware stored in the non-volatile memories 106 to 108 do not completely match, the first information comparison fails, and the corresponding testing computers 101 to 103 send first notification information to the server 105. If the version information of the first set of firmware stored in the test computers 101 to 103 completely matches the version information of the corresponding firmware stored in the nonvolatile memories 106 to 108, the first information comparison is successful.
Then, the test computers 101 to 103 may execute computer booting using a Preboot Execution Environment (PXE). PXE works in Network mode of Client and Server, and provides a mechanism for using Network Interface (Network Interface) to make Client computer download boot image file from PXE Server and start computer. This mechanism allows the computer to boot without relying on a local data storage device (e.g., a hard disk) or a local operating system.
The test computers 101 to 103 may download the respective boot image files, then perform the second update of the BIOS using the respective boot image files, and perform the second information comparison. The boot image file includes a second set of firmware, which may be all the same, partially the same, or all different from the first set of firmware. When the test computers 101 to 103 execute the second update of the BIOS according to the respective second set of firmware, the test computers 101 to 103 may update the respective second set of firmware into the non-volatile memories 106 to 108. When all the second set of firmware of the test computers 101, 102, 103 are successfully updated to the non-volatile memories 106, 107, 108, the second update of the test computers 101, 102, 103 is successful, and the test computers 101, 102, 103 with successful second update can write the version information of the second set of firmware into the non-volatile memories 106, 107, 108. When at least one of the second sets of firmware of the test computers 106, 107, 108 is not successfully updated to the non-volatile memories 106, 107, 108, the corresponding second update fails, and the test computers 101, 102, 103 that failed the second update will not write the version information of the firmware that failed to be updated in the version information of the respective second set of firmware into the non-volatile memories 106, 107, 108, and will only write the version information of the firmware that was successfully updated into the non-volatile memories 106, 107, 108, so that the non-volatile memories 106, 107, 108 still retain at least a portion of the BIOS version information of the previous BIOS. In one embodiment, the test computer 101 uses the PXE to perform BIOS update, and the PXE server downloads the boot image file, so the test computer 101 needs to perform the second information comparison. The test computers 101 to 103 may perform a second information comparison between the version information of the respective second set of firmware and the version information of the corresponding firmware stored in the non-volatile memories 106 to 108, and if the version information of the respective second set of firmware and the version information of the corresponding firmware stored in the non-volatile memories 106 to 108 do not completely match, the second information comparison fails, and the corresponding test computers 101 to 103 send second notification information to the server 105. If the version information of the second set of firmware stored in the test computers 101 to 103 completely matches the version information of the corresponding firmware stored in the nonvolatile memories 106 to 108, the second information comparison is successful.
In some embodiments, the test computers 101 to 103 may execute the pre-boot execution environment program after performing the first information comparison. In other embodiments, the test computers 101 to 103 may execute the pre-boot execution environment program after the first information comparison is successful, and stop updating the BIOS after the first information comparison is failed. In other embodiments, the test computers 101 to 103 may perform the first update after performing the second information comparison. In other embodiments, the test computers 101 to 103 may perform the first update after the second information comparison is successful, and stop the update of the BIOS after the second information comparison is failed.
If the second information is successfully compared, the test computers 101 to 103 may start to execute the automatic test of the BIOS. The BIOS automatic test includes several items, and different working modes such as system normal power mode, system low power mode, system standby mode, system sleep mode, etc. If a test error occurs during the test process, the test computers 101 to 103 may automatically send a notification message to the server 105, and the server 105 notifies the system administrator 110, for example, using an Electronic Mail (EMAIL) to notify the system administrator 110. After the test computers 101 to 103 have executed the BIOS automatic test, the test result file is uploaded to the server 105, and the server 105 notifies the system administrator 110.
The test computers 101-103 may each perform the same BIOS update or may each perform different BIOS updates, as desired. The client computers 101 to 103 execute the system test and the pressure test of the BIOS version 2.1 of the client a at the same time, or execute the system test of the BIOS version 2.1.0, version 2.1.1 and version 2.1.2 of the client a at the client computers 101 to 103 respectively, aiming at the reliability test of different versions.
FIG. 3 is a flowchart of an embodiment of a computer testing method 300, which is applied to testing computers 101 to 103 of the computer testing system 1, and the testing computer 101 is taken as an example for description. The method of fig. 3 comprises the steps of:
step S302: setting a first group of firmware and version information of the first group of firmware contained in the BIOS update of the test computer 101;
step S304: the test computer 101 uses the first set of firmware to perform a first update of the BIOS, and writes version information of the first set of firmware into the non-volatile memory 106 when the first update is successful;
step S306: the test computer 101 compares the version information of the first set of firmware with the version information of the corresponding firmware stored in the non-volatile memory 106, and sends a first notification message to the server 105 if the first information comparison is incorrect;
step S308: the test computer 101 executes the pre-boot execution environment program;
step S310: the test computer 101 performs a second update of the BIOS using a second set of firmware obtained by executing the pre-boot execution environment program, and writes version information of the second set of firmware into the non-volatile memory 106 when the second update is successful;
step S312: the test computer 101 compares the version information of the second set of firmware with the version information of the corresponding firmware stored in the non-volatile memory 106, and sends a second notification message to the server 105 if the second information comparison is wrong;
step S314: the test computer 101 executes the BIOS automatic test; and
step S316: the test computer 101 uploads the test result file to the server 105, and the server 105 notifies the system administrator 110.
In step S302, the system administrator 110 can use a software interface application (user interface application) to set version information of the first set of firmware included in the BIOS update, including at least one firmware and at least one firmware version number, and set an Management Engine (Intel Management Engine) and a Management Engine version number. For example, when the system administrator 110 wants to update the BIOS of the testing computer 101, the system administrator 110 uses the software interface 201 to input: the test computer 101, and the update firmware include diagnostics and version 3.10, security update and version 2.1.0, and Management Engine (Intel Management Engine) and version 2.2.0. Then, the software interface 201 generates a first set of firmware updated by the BIOS according to the version information of the first set of firmware, wherein the first set of firmware includes: the diagnostics use version 3.10, the security update uses version 2.1.0, and the Intel ME uses version 2.2.0, and the software interface program will generate BIOS version information 230 including: diagnostics program 3.10, security update 2.1.0, Intel ME 2.2.0.
In step S304, the test computer 101 uses the first set of firmware to perform a first update of the BIOS, updates the first set of firmware to the non-volatile memory 106 of the test computer 101, and stores version information of the first set of firmware in the non-volatile memory 106 after the first update is successful. When at least one firmware version fails to be updated in the first updating process, the testing computer 101 sends a third notification message to the system administrator 110 via the server 105. For example, the first set of firmware is updated to the test computer 101, wherein the security update version 2.1.0 and the Intel ME version 2.2.0 are successfully updated to the non-volatile memory 106, but the update of the diagnostic program version 3.10 fails, and the test computer 101 sends a third notification message to the system administrator 110 via the server 105, and the system administrator 110 then sends the third notification message to the test computer 101 to resolve the problem. In the present example, since the security update version 2.1.0 and the Intel ME version 2.2.0 are successfully updated, the nonvolatile memory 106 (e.g., flash memory) of the testing computer 101 stores the security update version 2.1.0 and the Intel ME version 2.2.0. Therefore, the firmware that has been successfully updated does not need to be updated again, and only the failed diagnostic program version 3.10 needs to be updated.
In step S306, the test computer 101 compares the version information of the first set of firmware with the version information of the corresponding firmware stored in the non-volatile memory 106. If the first information comparison fails, i.e. the firmware versions are different, a first notification message is sent to the system administrator 110 via the server 105. In the above example, the testing computer 101 reads the firmware version information of the corresponding firmware from the non-volatile memory 106 and compares the firmware version information with the version information of the first set of firmware, such as the version information of the diagnostic program 3.10, the security update 2.1.0, and the version information of the Intel ME 2.2.0. When the version of the diagnostic program, the security update, and the Intel ME are all the same as the firmware version number of the corresponding firmware read by the non-volatile memory 106, the next step S308 is executed. If not, a first notification message is sent to the system administrator 110 via the server 105, where the first notification message includes the firmware name and the corresponding version number that failed to be compared.
Step S308, the testing computer 101 tests a local area network Port (LAN Port), and after the LAN Port is successfully tested, the network is connected and the pre-boot execution environment procedure is executed. The pre-boot execution environment provides a mechanism for booting a computer using a network interface that allows booting of the computer independent of local data storage devices (e.g., hard disks) or installed operating systems. As shown in fig. 4, the testing computer 101 sends a request to a Dynamic Host Configuration Protocol (DHCP) server 402, the DHCP server 402 receives a first request 401 from the testing computer 101 and sends a first response 403 containing IP information and an IP address of a Trivial File Transfer Protocol (TFTP) server 405, and the testing computer 101 receives the first response 403 and then uses the IP address of the TFTP server 405 and sends a second request 404 to the TFTP server 405. After receiving the second request 404, the TFTP server 405 sends a second response 406, which includes the boot image file and the remote version information, and the testing computer 101 stores the boot image file and the remote version information in a Random Access Memory (RAM) of the testing computer 101. The boot image file may include a second set of firmware. The remote version information may include a firmware version number and a management engine version number. In this embodiment, the boot image file may be firmware and management engine associated with the BIOS, and/or software including the operating system. The DHCP server 402 and the TFTP server 405 may be separate or integrated servers, such as integrated within a PXE server.
In step S310, the test computer 101 performs a second update of the BIOS using a second set of firmware obtained by executing the pre-boot execution environment program to update the second set of firmware onto the non-volatile memory 106, and writes version information of the second set of firmware into the non-volatile memory 106 when the second update is successful. When at least one firmware version fails to be updated during the updating process, the testing computer 101 sends a fourth notification message to the system administrator 110 via the server 105.
In step S312, the test computer 101 compares the version information of the second set of firmware with the version information of the corresponding firmware stored in the non-volatile memory 106. If the second information is wrong, i.e. the firmware version is different, a second notification message is sent to the server 105, and the server 105 notifies the system administrator 110.
In step S314, if the test computer 101 has completed the BIOS update, the test computer 101 may start to execute the BIOS automatic test, in this embodiment, the test computer 101 defines different modes to execute the BIOS test, where the modes include: the system comprises a system normal power supply mode, a system low power supply mode, a system standby mode and a system sleep mode. The BIOS executing the automatic test further includes the test computer 101 executing BIOS automatic test items of different modes using the external power supply, and the test computer 101 executing BIOS automatic test items of different modes using the internal battery. In one embodiment, as shown in FIG. 5, FIG. 5 is a flow chart of an embodiment BIOS automatic test. The BIOS automatic test flow 500 may include: an external power system normal power mode 502, an external power system low power mode 504, an external power system standby mode 506, an external power system sleep mode 508, an internal battery system normal power mode 510, an internal battery system low power mode 512, an internal battery system standby mode 514, and/or an internal battery system sleep mode 516.
In the embodiment, the BIOS automatic test is performed by reading a batch file (batch) from the test computer 101 and generating BIOS automatic test items according to the batch file. The batch file generates a BIOS automatic test item according to the version information of the first group of firmware and/or the version information of the second group of firmware and the firmware name and version number in the batch file. In one example, the system administrator 110 may input default test items for BIOS respective firmware, such as default test items for diagnostics, default test items for security updates, and the like. When the BIOS of the test computer 101 is updated successfully, the batch file obtains the current update of the BIOS including the update of the diagnostic program and the update of the management engine according to the version information of the first group of firmware and/or the version information of the second group of firmware, and therefore, the batch file automatically loads the preset test items of the diagnostic program and the preset test items of the management engine to generate the automatic BIOS test items. As shown in FIG. 6, the file 602 is a plurality of default test items of BIOS firmware stored by the system administrator 110, including a default test item 604 of a diagnostic procedure, a default test item 606 of a security update, a default test item 608 of a management engine, and so on. The batch file 620 obtains the update according to the version information of the first firmware and/or the version information of the second firmware, including: diagnostic program updates and management engine updates. The batch file 620 reads the default test items of the BIOS firmware from the file 602, and generates the BIOS automatic test items 630 from the batch file 620, including the default test items 604 of the diagnostic program and the default test items 608 of the management engine.
In step S316, after the BIOS automatic test is executed by the test computer 101, the test result file is uploaded to the server 105, and the server 105 notifies the system administrator 110. In one embodiment, if a system error occurs during the automatic BIOS test process of the testing computer 101, the testing computer 101 may report the error test result to the server 105 in real time. The server 105 may define different severity levels (severity). If the system error does not affect the subsequent system test, it is defined as a low severity, if the file does not exist, and the test computer 101 with the system error reports the test result with the error to the server 105 in real time, and then the subsequent automatic test of the BIOS can be continuously executed. If the system error is Of high severity, such as a Blue Screen Of Death, the testing computer 101 having the system error stops the BIOS automatic test and reports the test result to the server 105 in real time. The server 105 notifies the system administrator 110 of the error test result in real time to help the system administrator 110 to quickly eliminate the problem of testing the computer 101. When the BIOS automatic test executed by the test computer 101 is successfully completed, the server 105 may also calculate the execution time of the test computer 101, and notify the system administrator 110 of the execution time and the test result.
The embodiment provides a computer test method, which comprises the steps of setting at least one firmware version contained in BIOS updating of a test computer and storing BIOS version information. The plurality of test computers may individually execute the same BIOS or different BIOS updates as desired. The test computer executes the first version to update the BIOS. The test computer executes the first information comparison to compare whether the BIOS is updated successfully or not, and if the BIOS is not updated successfully, the test computer sends a first notification message to a system manager. The test computer can execute the pre-boot execution environment program to achieve BIOS update. The pre-boot execution environment may update the BIOS of the plurality of test computers simultaneously. The individual test computer executes the second information comparison to compare whether the BIOS is updated successfully. After success, the testing computer starts to execute the BIOS automatic test, and uploads the test result file to the server, and the server informs the system manager. The system manager can immediately know the BIOS update and BIOS automatic test result of several test computers. If the testing computer encounters serious system error problem during BIOS automatic test, the test stops, and the system manager can also know the immediate location in time.
The above-mentioned embodiments are merely preferred embodiments of the present invention, and all equivalent changes and modifications made by the claims of the present invention should be covered by the scope of the present invention.
Claims (10)
1. A computer testing method, comprising:
setting a first group of firmware and version information of the first group of firmware contained in a basic input/output system update of a test computer;
the test computer uses the first group of firmware to carry out first updating of a basic input output system, and when the first updating is successful, the version information of the first group of firmware is written into a nonvolatile memory of the test computer;
the testing computer compares the version information of the first group of firmware with the version information of the corresponding firmware stored in the non-volatile memory by first information;
the test computer executes a pre-boot execution environment program;
the test computer uses a second group of firmware obtained by executing the pre-boot execution environment program to perform a second update of the basic input output system, and writes the version information of the second group of firmware into the non-volatile memory when the second update is successful; and
and the test computer compares the version information of the second group of firmware with the version information of the corresponding firmware stored in the non-volatile memory by second information.
2. The method of claim 1, wherein the test computer executes the pre-boot execution environment program after the first information comparison.
3. The method of claim 1, wherein the test computer performs the first update after performing the second information comparison.
4. The method of claim 1, further comprising sending a first notification message to a server if the first message fails to be compared.
5. The method of claim 1, further comprising sending a second notification message to a server if the second message fails to be compared.
6. The computer test method of claim 1, wherein said executing said pre-boot execution environment program by said test computer comprises:
the test computer sends a request to a dynamic host configuration protocol server;
the testing computer receives an IP address from the DHCP server and requests a boot image file from a simple file transfer protocol server;
the testing computer obtains the boot image file from the simple file transfer protocol server; and
the testing computer obtains remote version information of the startup image file;
the remote version information includes at least one firmware version number and a management engine version number.
7. The method of any of claims 1 to 6, further comprising:
the test computer executes a basic input and output system automatic test; and
and the test computer uploads a test result file of the automatic test of the basic input and output system to the server.
8. The computer test method of claim 7, wherein said testing the computer to perform the bios auto-test comprises:
the test computer generates a basic input and output system automatic test item according to the version information of the first group of firmware and/or the version information of the second group of firmware.
9. The computer test method of claim 8, wherein said testing computer performing said bios auto-test further comprises:
the test computer executes the automatic test items of the basic input and output system in a system normal power supply mode;
the test computer executes the automatic test items of the basic input and output system in a system low power mode;
the test computer executes the automatic test items of the basic input and output system in a system standby mode; and/or
The test computer executes the BIOS automatic test items in a system sleep mode.
10. The computer test method of claim 8, wherein said testing computer performing said bios auto-test further comprises:
the test computer executes the automatic test items of the basic input and output system by using an external power supply; and/or
The test computer uses an internal battery to execute the automatic test items of the basic input and output system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910846087.7A CN112463466B (en) | 2019-09-09 | 2019-09-09 | Computer testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910846087.7A CN112463466B (en) | 2019-09-09 | 2019-09-09 | Computer testing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112463466A true CN112463466A (en) | 2021-03-09 |
| CN112463466B CN112463466B (en) | 2022-06-24 |
Family
ID=74806997
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910846087.7A Active CN112463466B (en) | 2019-09-09 | 2019-09-09 | Computer testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463466B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114003452A (en) * | 2021-10-29 | 2022-02-01 | 苏州浪潮智能科技有限公司 | Device testing method, control device, testing device, and storage medium |
| CN115567487A (en) * | 2021-07-01 | 2023-01-03 | 昆达电脑科技(昆山)有限公司 | Server |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW479201B (en) * | 2000-12-07 | 2002-03-11 | Giga Byte Tech Co Ltd | Method for updating BIOS of the computer system |
| TW200622869A (en) * | 2004-12-31 | 2006-07-01 | Inventec Corp | Method for automatically updating and backup BIOS |
| TW201106155A (en) * | 2009-08-12 | 2011-02-16 | Inventec Corp | Examining method of switching firmwares and computer program product thereof |
| CN102073514A (en) * | 2009-11-23 | 2011-05-25 | 英业达股份有限公司 | Basic input and output system update method |
| TW201217963A (en) * | 2010-10-28 | 2012-05-01 | Hon Hai Prec Ind Co Ltd | Device and method for testing a PXE function of a network card |
| US20130031541A1 (en) * | 2011-07-29 | 2013-01-31 | Wilks Andrew W | Systems and methods for facilitating activation of operating systems |
| TW201342236A (en) * | 2012-04-03 | 2013-10-16 | Asrock Inc | Method for updating firmware |
| CN103793238A (en) * | 2012-10-31 | 2014-05-14 | 英业达科技有限公司 | Rack and method for simultaneously updating multiple basic input output systems thereof |
| US20150261520A1 (en) * | 2014-03-12 | 2015-09-17 | Wistron Corporation | Basic input/output system updating method and computer readable storage medium |
-
2019
- 2019-09-09 CN CN201910846087.7A patent/CN112463466B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW479201B (en) * | 2000-12-07 | 2002-03-11 | Giga Byte Tech Co Ltd | Method for updating BIOS of the computer system |
| TW200622869A (en) * | 2004-12-31 | 2006-07-01 | Inventec Corp | Method for automatically updating and backup BIOS |
| TW201106155A (en) * | 2009-08-12 | 2011-02-16 | Inventec Corp | Examining method of switching firmwares and computer program product thereof |
| CN102073514A (en) * | 2009-11-23 | 2011-05-25 | 英业达股份有限公司 | Basic input and output system update method |
| TW201217963A (en) * | 2010-10-28 | 2012-05-01 | Hon Hai Prec Ind Co Ltd | Device and method for testing a PXE function of a network card |
| US20130031541A1 (en) * | 2011-07-29 | 2013-01-31 | Wilks Andrew W | Systems and methods for facilitating activation of operating systems |
| TW201342236A (en) * | 2012-04-03 | 2013-10-16 | Asrock Inc | Method for updating firmware |
| CN103793238A (en) * | 2012-10-31 | 2014-05-14 | 英业达科技有限公司 | Rack and method for simultaneously updating multiple basic input output systems thereof |
| US20150261520A1 (en) * | 2014-03-12 | 2015-09-17 | Wistron Corporation | Basic input/output system updating method and computer readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115567487A (en) * | 2021-07-01 | 2023-01-03 | 昆达电脑科技(昆山)有限公司 | Server |
| CN114003452A (en) * | 2021-10-29 | 2022-02-01 | 苏州浪潮智能科技有限公司 | Device testing method, control device, testing device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112463466B (en) | 2022-06-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100620216B1 (en) | Network-expanded basic input / output system that enables remote management of computers without a functioning operating system | |
| US9858066B2 (en) | Updating firmware of a hardware component | |
| US20040255106A1 (en) | Recovery of operating system configuration data by firmware of computer system | |
| US9507604B2 (en) | Boot method and boot system | |
| TWI576764B (en) | A computer system | |
| US20030069951A1 (en) | Zero-click deployment of data processing systems | |
| CN112463466B (en) | Computer testing method | |
| CN107220085A (en) | A kind of method of automatic upgrading RAID card firmware | |
| US7356685B2 (en) | System and method for enabling automated run-time input to network bootstrapping processes | |
| US11675601B2 (en) | Systems and methods to control software version when deploying OS application software from the boot firmware | |
| US11403113B2 (en) | Server with system setting data synchronization function | |
| CN119576420A (en) | Basic input and output system configuration method and device | |
| CN113507384A (en) | A system and method for switching equipment working mode | |
| US20080201572A1 (en) | Method and system for uniformizing product data embedded in a computer platform | |
| CN106484442B (en) | Server system and method for updating startup mapping file | |
| CN115913913B (en) | Method and device for locating fault of network card pre-start execution environment function | |
| CN109684134B (en) | Method and server for rapidly deploying firmware settings among multiple devices | |
| CN111367735A (en) | A test method and system based on a server to be tested and an Ubuntu operating system | |
| TWI694452B (en) | Computer test method | |
| CN115328717A (en) | Kernel testing method and system supporting various domestic platforms | |
| CN113452550A (en) | Information acquisition device, firmware updating method and system of embedded system device | |
| US8245021B2 (en) | System and method for re-imaging computers | |
| US20220350705A1 (en) | Linking embedded controller with memory reference code and system bios shadowing | |
| CN115314471A (en) | MAC address allocation method and terminal | |
| CN114817042A (en) | A server testing method, device, testing platform and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |