TW202301104A - Device and method of building test file - Google Patents

Abstract

A device for building a test file comprises a receiving module, for receiving a first request of a first user and for analyzing the first request, and for notifying an analysis result of the first request to the first user; a building module, coupled to the receiving module, for building the test file according to the first request of a task queue; and a transmitting module, coupled to the building module, for notifying a building result of the test file to the first user.

Description

Device and method for building test files

The invention relates to a device and method for building test files.

When the user wants to modify the BIOS code, the user must notify the builder, so that the builder can modify the BIOS code and create a test file for testing the BIOS. After the builder builds the test file, the builder and the user receive the built test file and use it to test the basic input/output system. However, the above-mentioned manual operations involving construction personnel will not only increase the consumption of human resources, but also increase the risk of mistakes. These problems are aggravated when builders operate repeatedly. Therefore, how to build test files for testing the basic input and output system while reducing the consumption of human resources and the risk of errors is an urgent problem to be solved.

The present invention provides a device and method for building test files, which are used to build test files to solve the above problems.

The invention discloses a device for building a test file, including: a receiving module, used to receive a first request from a first user, analyze the first request, and notify the first An analysis result of the request is sent to the first user; a building module, coupled to the receiving module, is used to build the test file according to the first request in a task queue (Task Queue); and a sending module, coupled to the building module, for notifying a building result of the test file to the first user.

The present invention also discloses a method for building a test file, which is used for building the above test file.

FIG. 1 is a schematic diagram of a device 10 for building a test file according to an embodiment of the present invention. As shown in FIG. 1 , the device 10 for building test files includes a receiving module 100 , a building module 110 and a sending module 120 . In detail, the receiving module 100 can be used to receive the first request from the first user and analyze (for example, interpret or analyze) the first request, and can notify the first user of the analysis result of the first request. The building module 110 is coupled to the receiving module 100 and can be used to build a test file according to the first request in the task queue (Task Queue). The sending module 120 is coupled to the building module 110 and can be used to notify (for example, send) the building result of the test file to the first user.

In one embodiment, the receiving module 100 can receive the first request from the first user by monitoring (eg, periodically querying) the communication software (eg, a folder therein). In one embodiment, through the communication software, the receiving module 100 can notify the first user of the analysis result of the first request. In one embodiment, through communication software, the transmission module 120 can notify the first user of the construction result of the test file. In one embodiment, the communication software may include email software (such as Outlook or Gmail), instant messaging software (such as Skype) or a combination thereof, but is not limited thereto.

In one embodiment, in the operation of notifying the first user of the analysis result of the first request, when the analysis result is successful, the receiving module 100 may add the first request to the task queue, and may notify the first request A request is received to the first user. In addition, the receiving module 100 can receive the second request. In one embodiment, when the analysis result is unsuccessful, the receiving module 100 may notify the first user that the first request is failed. In addition, the receiving module 100 can receive the second request. In one embodiment, the receiving module 100 can receive the second request from the first user or the second user.

In one embodiment, during the operation of building the test file according to the first request in the task queue, the building module 110 may determine (for example, analyze) the platform of the first request according to the first request in the task queue ( Platform). The build module 110 can generate scripts for the platform. The build module 110 can execute the script and can wait for the script to be successfully executed. When the script is successfully executed, the build module 110 can build a test file. In one embodiment, the script may include instructions for building test files. In one embodiment, instructions may be predetermined or dynamically determined.

In one embodiment, the platform may include an operating system. In one embodiment, the operating system may include WINDOWS XP, WINDOWS VISTA, WINDOWS 7, WINDOWS 8, WINDOWS 10, any version among the above WINDOWS operating system versions or a subsequent version of WINDOWS 10, but not limited thereto.

In an embodiment, the first request or the second request may include a Basic Input Output System (BIOS) version or a machine type. In one embodiment, according to the version or machine type, the build module 110 may determine (for example, analyze) the platform of the first request or the second request.

In one embodiment, the first request or the second request may include a compressed file, and the compressed file may include a path (such as a link), source code (source code), information related to the source code, or a combination of the above information, but Not limited to this. In one embodiment, according to the above information or a combination thereof, the building module 110 may determine (for example, analyze) the platform of the first request or the second request. In one embodiment, the test file may include a binary file, a description file or an information file for testing the BIOS.

In one embodiment, during the operation of notifying the first user of the construction result of the test file, the transmission module 120 can determine whether an error occurs according to the error code of the test file. In one embodiment, when an error occurs, the transmission module 120 can analyze the event log file (Log) of the test file and can notify the first user of the construction result. The build result may contain error messages associated with error codes. In one embodiment, when no error occurs, the transmission module 120 can transmit the test file to the file transmission space, and can notify the first user of the construction result. In one embodiment, the build result may include access information that the first request is successfully built and the file transfer space.

In one embodiment, during the operation of transmitting the test file to the file transmission space, the transmission module 120 can compress the test file to generate a compressed test file, and can transmit the compressed test file to the file transmission space. In one embodiment, through data compression software, the transmission module 120 can compress the test file to generate a compressed test file. In one embodiment, the data compression software may include ZIP, RAR or 7z, but is not limited thereto.

In one embodiment, during the operation of transmitting the test file to the file transmission space, according to the File Transfer Protocol (FTP), the transmission module 120 can transmit the test file to the file transmission space. In one embodiment, the access information may include an access link or at least one communication port, but is not limited thereto. In an embodiment, at least one communication port may include a command port (Command Port) (such as the communication port 21 ) or a data communication port (Data Port) (such as the communication port 20 ), but not limited thereto.

The aforementioned method for building the device 10 for building test files can be summarized as a process 20 in FIG. 2 . Process 20 includes the following steps:

Step 200: start.

Step 202: Receive a first request from a first user and analyze the first request, and notify the first user of the analysis result of the first request.

Step 204: Create a test file according to the first request in the task queue.

Step 206 : Notify the first user of the test file construction result.

Step 208: end.

The aforementioned receiving method of the receiving module 100 can be summarized as a process 30 in FIG. 3 . Process 30 includes the following steps:

Step 300: start.

Step 302: Receive a first request from a first user.

Step 304: Analyze whether the analysis result of the first request is successful.

Step 306a: When the analysis result is successful, add the first request to the task queue, and notify the first user that the first request is received.

Step 306b: When the analysis result is unsuccessful, notify the first user that the first request is failed.

Step 308: Receive a second request.

Step 310: end.

The aforementioned construction method of the construction module 110 can be summarized as a process 40 in FIG. 4 . Process 40 includes the following steps:

Step 400: start.

Step 402: Determine the platform of the first request according to the first request in the task queue.

Step 404: Generate a script for the platform.

Step 406: Execute the script.

Step 408: Wait for the script to be executed successfully.

Step 410: When the script is executed successfully, build a test file.

Step 412: end.

The transmission method of the aforementioned transmission module 120 can be summarized as a process 50 in FIG. 5 . Process 50 includes the following steps:

Step 500: start.

Step 502: Determine whether an error occurs according to the error code of the test file.

Step 504a: When an error occurs, analyze the event log file of the test file, and notify the first user of an error message associated with the error code.

Step 504b: When no error occurs, send the test file to the file transfer space, and notify the first user that the first request is successfully constructed and the access information of the file transfer space.

Step 506: end.

It should be noted that the above "first" and "second" are used to distinguish the relevant statements, not to limit the order of the relevant statements.

It should be noted that there are many ways to implement the device 10 for building the test file (and the receiving module 100 , the building module 110 , and the sending module 120 therein). For example, the above modules may be integrated into one or more modules. In addition, the device 10 (and the receiving module 100, the building module 110, and the transmitting module 120) for building the test file can be implemented through hardware (such as a circuit or chip), software, and firmware (for hardware devices and Combination of computer instructions and data, and computer instructions and data belong to the read-only software on the hardware device), electronic system, or a combination of the above modules to achieve, but not limited to this. The steps of all the aforementioned processes can be implemented through hardware (such as circuits or chips), software (such as program codes), and firmware (which is the combination of hardware devices and computer instructions and data, and the computer instructions and data belong to the hardware device. Read-only software), electronic systems, or a combination of the above modules, but not limited thereto.

In summary, the present invention provides a device and method for building test files. When the user wants to modify the basic input and output system code, the user can notify the device for building the test file of his request through the communication software. . The device for building test files can automatically receive requests, can automatically build test files for testing the basic input output system, and can automatically send the completed test files to users. That is to say, in the process of building the test file, no manual operation of the builder is involved. Therefore, the problems caused by manual operation of builders in the prior art can be solved. The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

10: Device for building test files 100: receiving module 110: Build modules 120: Teleportation Module 20, 30, 40, 50: Process 200, 202, 204, 206, 208, 300, 302, 304, 306a, 306b, 308, 310, 400, 402, 404, 406, 408, 410, 412, 500, 502, 504a, 504b, 506: steps

FIG. 1 is a schematic diagram of a device for building test files according to Embodiment 1 of the present invention. Fig. 2 is a flow chart of the process of Embodiment 1 of the present invention. Fig. 3 is a flow chart of the process of Embodiment 1 of the present invention. Fig. 4 is a flow chart of the first embodiment of the present invention. Fig. 5 is a flow chart of the first embodiment of the present invention.

20: Process

200, 202, 204, 206, 208: steps

Claims (10)

A device for building (Build) a test file, comprising: A receiving module, used to receive a first request from a first user and analyze the first request, and notify the first user of an analysis result of the first request; a building module, coupled to the receiving module, for building the test file according to the first request in a task queue (Task Queue); and A sending module, coupled to the building module, is used for notifying a building result of the test file to the first user. The device as described in claim 1, wherein the operation of notifying the analysis result of the first request to the first user includes: when the analysis result is successful, adding the first request to the job queue, and notifying the first user that the first request is received; when the analysis result is unsuccessful, notifying the first request that the first request has failed; and A second request is received. The device according to claim 2, wherein the second request is received from the first user or a second user. The device as described in claim 1, wherein according to the first request in the task queue, the operation of building the test file includes: determine a platform (Platform) for the first request; Generate a script (Script) for the platform; execute the script and wait for the script to be successfully executed; and When the script is executed successfully, the test file is built. The device according to claim 1, wherein the first request includes a version of a Basic Input Output System (BIOS). The device as claimed in claim 5, wherein the test file includes a binary file for testing the BIOS. The device as described in claim 1, wherein the operation of notifying the first user of the construction result of the test file includes: Determine whether an error occurs according to an error code of the test file; When the error occurs, analyzing an event log file (Log) of the test file and notifying the first user of the construction result, wherein the construction result includes an error message associated with the error code; and When the error does not occur, send the test file to a file transfer space, and notify the first user of the build result, wherein the build result includes the first request being built successfully and the file An access information of the transmission space. The device as described in claim item 7, wherein the operation of sending the test file to the file transmission space includes: Compress the test file to generate a compressed test file, and send the compressed test file to the file transmission space. The device as described in claim item 7, wherein the operation of sending the test file to the file transmission space includes: According to a file transfer protocol (File Transfer Protocol, FTP), the test file is sent to the file transfer space. A method for building (Build) a test file, comprising: receiving a request from a user and analyzing the request, and notifying the user of an analysis result of the request; building the test file according to the first request in a task queue (Task Queue); and Notifying the user of a build result of the test file.

Images