TW201421233A - System and method of testing motherboard - Google Patents

Abstract

The present invention provides a method for testing motherboard which applies to a testing host. The method includes: presetting a testing order for each test item of an UUT (Unit Unter Test); calling an appropriate test program of a test item to test the motherboard according to the preset testing order; scanning a process list of the testing host to check whether the test program of the test item is running; scanning the process list to check whether the test program of the test item exits the process list; encrypting and writing a test result of the test item in a log file when the appropriate test program was ever running and already exited the process list. The present invention also provides a related system for testing motherboard. The present invention can be used to prevent falsifying the test result.

Description

Motherboard function test control system and method

The invention relates to a motherboard test function control system and method.

The current motherboard test often uses the Linux system platform. The Linux system advocates software open source. There are many shared hardware test software that can be used free of charge. Therefore, when testing the software for the motherboard test, it is often possible to save development time. Some free shared test programs use scripts to connect these test programs with their own test programs.

In order to meet the factory requirements, each test item must have a test log document. When the test program is run in the factory, sometimes the factory operator or test engineer will manually mask some test programs, leaving only the log file function. Or manually copy the forged log file and evade the test. Obviously, these test behaviors greatly affect the quality of the motherboard test.

In view of the above, it is necessary to provide a motherboard test function control system and method, which can effectively prevent the fake behavior of the test result of the device under test.

The function test and control system of the motherboard includes: a preset module for presetting a test sequence of a test project to be executed by the device under test; and a calling module for calling a corresponding test program according to the preset test sequence. a scan module, configured to scan a process list of the test host after detecting one of the test projects to detect whether the test program of the test project is running; the scan module is further used to test the project After the test is completed, the process list of the test host is scanned to detect whether the test program of the test project has exited the process list; and the recording module is used when the test program of the test project is actually running and the test program exits After the process list is described, the test result of the test project is encrypted and written into the test log document.

The method for controlling and controlling the function of the motherboard includes: a preset step of presetting the test sequence of the test project to be executed by the device under test; and calling the step, calling the corresponding test program for testing according to the preset test sequence; the first scanning step Scanning a list of processes of the test host to detect whether the test program of the test project is running after starting one of the test projects; and a second scanning step of scanning the process of the test host after the test project completes the test The list is to detect whether the test program of the test project has exited the process list; and the recording step, when the test program of the test project is actually running and the test program exits the process list, the test result of the test project is encrypted and Write to the test log document.

Compared with the prior art, the motherboard functional test and control system and method can effectively prevent the fake behavior of the test result of the tested device from occurring.

As shown in FIG. 1 , it is an operating environment diagram of the functional test and control system of the motherboard of the present invention. In this embodiment, the functional test management system 10 is operated in the test host 100 for controlling the functional tests of the various functional accessories on the UUT (Unit Under Test) 200. The test host 100 further includes a memory 20 and a processor 30.

In this embodiment, the UUT 200 can be a motherboard or other electronic device with a functional accessory. When the UUT 200 is a motherboard, its functional accessories include, but are not limited to, a CPU, a memory, a hard disk, and the like.

The memory 20 can be used to store various materials, such as a programmatic code for storing the functional test control system 10 and a test log file for recording test results of the UUT 200. In this embodiment, the functional test management system 10 can be divided into one or more modules and executed by the processor 30 to perform the functions provided by the present invention. In this embodiment, the function test management system 10 includes a preset module 11, a call module 12, a scan module 13, a determination module 14, and a record module 15 (see FIG. 2). The module referred to in the present invention is a program segment for performing a specific function, and the functions of each module will be specifically described in the flowchart of FIG.

3 is a flow chart of a preferred embodiment of the functional test management method of the present invention.

This embodiment is described by taking the function test of the CPU, the memory, and the hard disk on the UUT 200 as an example. In other embodiments, the functions of other functional components such as the network card may also be tested.

In step S1, the preset module 11 presets the test sequence of the test project to be executed by the UUT 200.

For example, the test sequence of the test program to be executed by the UUT 200 is: CPU test, memory test, hard disk test.

In step S2, the calling module 12 calls the corresponding test program to perform a specific test according to the preset test sequence.

For example, assuming that the CPU test is first executed in step S1, the calling module 12 first calls the test program of the test CPU.

It should be noted that, in this embodiment, each test program may be named in advance according to the corresponding test program, and stored in the memory 20, for example, the file name of the test program of the test CPU is set to CPUtest.exe and stored. In the memory 20, the file name of the test program of the test memory is set to Memorytest.exe and stored in the memory 20. The test program for testing the hard disk can be named and stored in HDDtest.exe. In the memory 20. When you need to call the corresponding test program for functional test, for example, you need to call the test program of the test CPU to perform functional test on the CPU, you can directly call the execution according to the file name of the test program.

In step S3, the scan module 13 scans the process list of the test host 100 after starting a test project to detect whether the test program of the test project is running.

Specifically, the scanning module 13 scans the process list of the test host 100, and detects whether there is a test program named according to the test project to determine whether the test program of the test project is running. For example, if the currently started test item is a CPU test, the scan module 13 scans the process list of the test host 100 to find whether a test program named CPUtest.exe appears in the process list. If the result of the search is that the test program with the file name CPUtest.exe appears in the process list, it is determined that the test program of the test CPU is running.

If the result of the detection in step S3 is that the currently started test project is running, step S4 is performed, otherwise the flow is ended.

In step S4, the determining module 14 determines whether the test item is tested. If yes, step S5 is performed. Otherwise, returning to step S3, the scanning module 13 continues to scan the process list to determine whether the test program corresponding to the test project is still running.

For example, after running the test program of the test CPU, if the test result of the CPU is obtained, it can be determined that the CPU test is completed, and then step S5 is performed.

In step S5, the scan module 13 scans the process list of the test host 100 to detect whether the test program of the test project has exited the process list. If the process proceeds to step S6, the process ends.

For example, when the test program named CPUtest.exe does not exist in the process list of the test host 100, it can be determined that the test program of the test CPU has exited the process list.

In step S6, the recording module 15 encrypts and writes the test result of the test project into the test log document.

It should be noted that the encryption method involved in this step may adopt any encryption algorithm in the prior art, such as loop encryption.

In step S7, the determining module 14 determines whether there are other test projects in the UUT 200 that are not completed. If yes, step S2 is performed, otherwise the process ends.

For example, after the CPU test is completed, if the function test of the memory or the hard disk is still required, the flow returns to step S2, and the calling module 12 calls the corresponding test program to perform the test according to the preset test sequence.

It can be seen from the entire process execution steps of the present invention that each time a test project is started, the test program of the test host 100 is scanned for whether a corresponding test program is running, that is, whether the test project is running. When the test is completed, the process list is scanned again to determine whether the corresponding test program has exited the process list, and the test result is written to the test log file when the test program is run and exits the process list after running. Therefore, the present invention can ensure that the test results of each test item are obtained based on the actual running test program, and effectively prevent the fake behavior of the test result from occurring.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments. Modifications or equivalents are made without departing from the spirit and scope of the invention.

100. . . Test host

200. . . UUT

10. . . Functional test control system

20. . . Memory

30. . . processor

11. . . Preset module

12. . . Call module

13. . . Scanning module

14. . . Judging module

15. . . Recording module

S1. . . Default test project test sequence

S2. . . Call the corresponding test program for testing according to the preset test sequence

S3. . . Is the test program for the test project running?

S4. . . Is the test project completed?

S5. . . Has the test program of the test project exited the process list?

S6. . . Encrypt the test results of the test project and write them to the test log document

S7. . . Are there other test projects not completed?

1 is a diagram showing the operating environment of a functional test and control system for a motherboard of the present invention.

2 is a functional block diagram of a functional test and control system for a motherboard of the present invention.

3 is a flow chart of a preferred embodiment of a method for controlling and testing a function of a motherboard of the present invention.

S1. . . Default test project test sequence

S2. . . Call the corresponding test program for testing according to the preset test sequence

S3. . . Is the test program for the test project running?

S4. . . Is the test project completed?

S5. . . Has the test program of the test project exited the process list?

S6. . . Encrypt the test results of the test project and write them to the test log document

S7. . . Are there other test projects not completed?

Claims (6)

A motherboard functional test management system runs on a test host, the system comprising:
a preset module for presetting the test sequence of the test project to be executed by the device under test;
Calling a module for invoking a corresponding test program for testing according to a preset test sequence;
a scanning module, configured to scan a process list of the test host after starting one of the test projects to detect whether the test program of the test project is running;
The scanning module is further configured to: after the test project completes the test, scan a list of processes of the test host to detect whether the test program of the test project has exited the process list; and the recording module is used for the test After the project test program is actually running and the test program exits the process list, the test result of the test project is encrypted and written into the test log file. For example, in the motherboard functional test and control system described in claim 1, the test program of the test project is named according to the corresponding test project and stored in the memory. The motherboard function test and control system according to claim 2, wherein the scan module scans a process list of the test host, and detects from the process list whether there is a test program named according to the test project, thereby Check if the test program of the test project is running or has exited the process list. A method for controlling and controlling a motherboard function is applied to a test host, and the method includes:
a preset step of presetting the test sequence of the test project to be executed by the device under test;
Invoking the step, calling the corresponding test program according to the preset test sequence for testing;
a first scanning step of scanning a process list of the test host after starting one of the test projects to detect whether the test program of the test project is running;
a second scanning step, after the test project completes the test, scanning a list of processes of the test host to detect whether the test program of the test project has exited the process list; and recording the step, when the test program of the test project is actually running After the test program exits the process list, the test result of the test project is encrypted and written into the test log document. The method for controlling and controlling the motherboard function according to the fourth aspect of the patent application, wherein the test program of the test project is named according to the corresponding test project and stored in the memory. The method for controlling and controlling a motherboard function according to claim 5, wherein the first and second scanning steps scan a process list of the test host, and check whether the existence of the test program is named according to the test program. Test program to detect if the test program of the test project is running or has exited the process list.