CN115080382A - Code testing method, device, equipment and medium - Google Patents

Abstract

The invention discloses a code testing method, a device, equipment and a medium. The method comprises the following steps: acquiring a code merging request input by a user, wherein the code merging request carries a new BIOS branch source code; sending a control instruction to a compatibility test process, indicating the compatibility test process, compiling the new BIOS branch source code to obtain a new BIOS branch code, performing compatibility test on the new BIOS branch code in a simulator, and feeding back a compatibility test result of the new BIOS branch code; and if the test is passed, merging the new BIOS branch source code into the BIOS main body source code to generate the new BIOS main body source code. The embodiment of the invention carries out compatibility test before code merging, realizes the prevention of the compatibility problem of the BIOS main stem source code, prevents the compatibility problem from flowing into the code main stem, reduces the dependence of the compatibility test process on a physical machine, improves the portability of the test environment and reduces the test cost.

Description

A code testing method, device, equipment and medium

technical field

The present invention relates to the field of computer technology, and in particular, to a code testing method, apparatus, device and medium.

Background technique

The basic input and output system (Base Input Output System, BIOS) code of electronic equipment includes the most important basic input and output program, system setting information, self-checking program and system self-starting program of electronic equipment. After the development of the BIOS source code is completed, the BIOS source code is compiled by the compiler to obtain the BIOS code. Then, the BIOS code is burned into the chip of the electronic device, so that the BIOS code provides the lowest-level and most direct hardware setting and control for the electronic device. By performing Standard Compatibility Testing (SCT) on the BIOS code, the codes that do not conform to the specification in the BIOS code can be screened out and modified in time.

In the related art, the BIOS code testing scheme is as follows: developers complete the code development of new BIOS functions on multiple branches, and regularly merge the latest BIOS branch source code into the BIOS trunk source code to generate a new BIOS trunk source code. Compile the new BIOS main source code to get the new BIOS code. Then, the new BIOS code is updated to the electronic device, and a standard compatibility test is performed on the new BIOS code on the electronic device.

The defect of the related art is that although compatibility problems of new BIOS codes can be found, compatibility problems cannot be prevented from flowing into the BIOS main source code in advance. In addition, the compatibility test of the new BIOS code on the electronic device will occupy a lot of hardware resources and increase the test cost.

SUMMARY OF THE INVENTION

The present invention provides a code testing method, device, equipment and medium, so as to solve the BIOS code testing scheme in the related art, which cannot prevent compatibility problems from flowing into the BIOS main source code in advance, which will occupy a large amount of hardware resources and increase the testing cost. The problem.

According to an aspect of the present invention, a code testing method is provided, comprising:

Obtain the code merge request input by the user, and the code merge request carries the new BIOS branch source code;

Sending a control instruction to the compatibility test process, instructing the compatibility test process, compiling the new BIOS branch source code to obtain a new BIOS branch code, and performing a compatibility test on the new BIOS branch code in the simulator, And feedback the compatibility test result of the new BIOS branch code;

If the compatibility test result fed back by the compatibility test process is that the test is passed, the new BIOS branch source code is merged into the BIOS main source code to generate a new BIOS main source code.

According to another aspect of the present invention, a code testing device is provided, comprising:

a request acquisition module for acquiring a code merge request input by a user, where the code merge request carries the new BIOS branch source code;

The code test module is used for sending control instructions to the compatibility test process, instructing the compatibility test process, compiling the source code of the new BIOS branch, obtaining the new BIOS branch code, and performing the new BIOS branch code in the simulator The code is tested for compatibility, and the compatibility test result of the new BIOS branch code is fed back;

The code merging module is configured to merge the new BIOS branch source code into the BIOS main source code to generate a new BIOS main source code if the compatibility test result fed back by the compatibility test process is a test pass.

According to another aspect of the present invention, an electronic device is provided, 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, the computer program being executed by the at least one processor to enable the at least one processor to perform any of the embodiments of the present invention. Code testing methods.

According to another aspect of the present invention, a computer-readable storage medium is provided, where computer instructions are stored in the computer-readable storage medium, and the computer instructions are used to cause a processor to implement any of the embodiments of the present invention when executed. code testing method.

In the technical solution of the embodiment of the present invention, the code merge request input by the user is obtained, and the code merge request carries the source code of the new BIOS branch; then a control instruction is sent to the compatibility test process, indicating the compatibility test process, and the new BIOS branch source code is carried out. Compile, get the new BIOS branch code, test the compatibility of the new BIOS branch code in the simulator, and feed back the compatibility test result of the new BIOS branch code; Merge the BIOS main source code to generate a new BIOS main source code, which solves the test scheme of the BIOS code in the related technology. It cannot prevent the standard compatibility problem from flowing into the BIOS main source code in advance, which will occupy a lot of hardware resources and increase the test cost. , get the compatibility test before the code is merged, realize the prevention of the compatibility problem of the BIOS trunk source code, prevent the compatibility problem from flowing into the code trunk, and truly realize the compatibility of the BIOS code before the problem occurs. problems, which greatly reduces the possible impact of compatibility problems. At the same time, by conducting compatibility tests under the simulator, the dependence of the compatibility test process on physical machines is reduced, the portability of the test environment is improved, and the Beneficial effect of testing costs; by sending control commands to the compatibility testing process, instructing the compatibility testing process, and performing compatibility testing on the new BIOS branch code under the simulator, the dependence of the compatibility testing process on physical machines is reduced, and the performance of the compatibility testing process is improved. The portability of the test environment also reduces the test cost; in the case that the compilation of the new BIOS branch source code fails, it is directly determined that the test of the new BIOS branch code fails, the test efficiency is improved, and the defective new BIOS branch source code is avoided Merge the BIOS main source code; if the new BIOS branch code fails the compatibility test, directly determine that the new BIOS branch code fails the test, improve the test efficiency, and avoid the new BIOS branch source code with compatibility defects from being merged The BIOS main source code prevents compatibility problems from flowing into the BIOS main source code; in the case of a new BIOS branch code test failure, the new BIOS branch source code is automatically blocked and merged into the BIOS main source code to avoid the new BIOS branch with compatibility defects. The source code is merged into the BIOS trunk source code, preventing compatibility issues from flowing into the BIOS trunk source code; based on the interaction with the user, the code merge request input by the user can be obtained in real time, so as to determine the user's request to merge the new BIOS branch source code. Enter the BIOS main source code; store the preset compatibility test script in the preset storage location, so that the compatibility test process can call the preset compatibility test script in real time, automatically perform compatibility test on the new BIOS branch code, and provide test efficiency.

It should be understood that the content described in this section is not intended to identify key or critical features of the embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become readily understood from the following description.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 is a flowchart of a code testing method according to Embodiment 1 of the present invention.

FIG. 2 is a flowchart of a code testing method according to Embodiment 2 of the present invention.

FIG. 3 is a flowchart of a code testing method according to Embodiment 3 of the present invention.

FIG. 4 is a schematic structural diagram of a code testing apparatus according to Embodiment 4 of the present invention.

FIG. 5 is a schematic structural diagram of an electronic device implementing the code testing method according to an embodiment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only Embodiments are part of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the terms "object", "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order. or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising", "including" and "having", and any variations thereof, are intended to cover non-exclusive inclusion, eg, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to the explicit Those steps or units are explicitly listed, but may include other steps or units not expressly listed or inherent to the process, method, product or apparatus.

Example 1

1 is a flowchart of a code testing method provided in Embodiment 1 of the present invention. This embodiment can be applied to a new BIOS trunk source code corresponding to a new BIOS trunk source code before the new BIOS branch source code is merged into the BIOS trunk source code. The BIOS source code, standard compatibility test is carried out to prevent the standard compatibility problem from flowing into the BIOS backbone source code in advance, the method can be performed by a code testing device, and the code testing device can be implemented in the form of hardware and/or software, The code testing device can be configured in electronic equipment. As shown in Figure 1, the method includes:

Step 101: Obtain a code merge request input by a user, where the code merge request carries the source code of the new BIOS branch.

Optionally, the BIOS backbone source code is the BIOS source code that has been developed and put into use. The BIOS source code is compiled by the compiler to obtain the BIOS code. Burning the BIOS code into the chip of the designated electronic device can provide the lowest and most direct hardware setting and control for the designated electronic device through the BIOS code.

Optionally, the user can be a developer. The new BIOS branch source code is newly developed by the developer and needs to be merged into the BIOS main source code, thereby adding a new BIOS source code with new BIOS functions. Merge the new BIOS branch source code into the BIOS trunk source code, and update the BIOS source code. Then, the updated BIOS source code is compiled to obtain a new BIOS code that adds a new function of the BIOS.

Optionally, the code merge request is used to request that the new BIOS branch source code be merged into the BIOS trunk source code.

Optionally, obtaining the code merge request input by the user, where the code merge request carries the source code of the new BIOS branch, includes: obtaining the code merge request input by the user through the code merge page, where the code merge request carries the new BIOS branch source code.

Optionally, the code merging page is a page for interacting with the user, acquiring various information related to the BIOS source code input by the user, and displaying various information related to the BIOS source code to the user. The user enters a code merge request by filling in or selecting the new BIOS branch source code in the code merge page.

Therefore, based on the interactive operation with the user, the code merge request input by the user can be acquired in real time, so as to determine that the user requests to merge the new BIOS branch source code into the BIOS trunk source code.

Step 102: Send a control instruction to the compatibility test process, instruct the compatibility test process, compile the new BIOS branch source code, obtain a new BIOS branch code, and perform compatibility with the new BIOS branch code in the simulator and feedback the compatibility test results of the new BIOS branch code.

Optionally, the compatibility testing process is a preset process for performing compatibility testing on the new BIOS branch code. The control instruction is used to instruct the compatibility test process, compile the source code of the new BIOS branch to obtain a new BIOS branch code, perform a compatibility test on the new BIOS branch code in the simulator, and feed back the Instructions for compatibility test results for the new BIOS branch code. After obtaining the code merge request input by the user, a control command is sent to the compatibility testing process.

Optionally, the instructing the compatibility testing process, compiling the source code of the new BIOS branch to obtain the new BIOS branch code, performing a compatibility test on the new BIOS branch code in the simulator, and feeding back all the codes. Describe the compatibility test result of the new BIOS branch code, including: instructing the compatibility test process to perform the following operations: compiling the new BIOS branch source code by a compiler; if the compilation is successful, the new BIOS branch code is obtained, then The new BIOS branch code is run in the simulator, and during the running process of the new BIOS branch code, a preset compatibility test script is called to perform a compatibility test on the new BIOS branch code; If the branch code passes the compatibility test, the result of the compatibility test of the new BIOS branch code is determined as passing the test, and the compatibility test result of the new BIOS branch code is fed back.

Optionally, use a compiler to compile the source code of the new BIOS branch. If the compilation is successful, you can get the new BIOS branch code. The new BIOS branch code is a BIOS code obtained by compiling the new BIOS branch source code.

Optionally, the pre-built simulator includes a running environment of BIOS codes, and various types of BIOS codes can be run in the simulator.

Optionally, the preset compatibility test script is a script used for standard compatibility test on the new BIOS branch code. The standard compatibility test is used to detect whether the code content of various interface codes in the new BIOS branch code conforms to the corresponding interface code rules.

Optionally, after the preset compatibility test script is invoked, during the running process of the new BIOS branch code, the operation of various types of interface codes in the new BIOS branch code is monitored. The preset compatibility test script detects whether the code content of various interface codes conforms to the corresponding interface code rules when monitoring the running of various interface codes. If all kinds of interface codes in the new BIOS branch code conform to the corresponding interface code rules, it is determined to pass the compatibility test. If a certain interface code in the new BIOS branch code does not conform to the corresponding interface code rule, it is determined that the compatibility test is not passed.

Therefore, by sending control commands to the compatibility testing process, instructing the compatibility testing process, and performing compatibility testing on the new BIOS branch code under the simulator, the dependence of the compatibility testing process on the physical machine is reduced, and the test environment is improved. Portability also reduces testing costs.

Optionally, after compiling the source code of the new BIOS branch by the compiler, the method further includes: if the compilation fails, determining that the compatibility test result of the new BIOS branch code is a test failure, and feeding back the new BIOS branch. Code compatibility test results.

Thus, in the case that the compilation of the new BIOS branch source code fails, it is directly determined that the new BIOS branch code fails to be tested, thereby improving the test efficiency and preventing the defective new BIOS branch source code from being merged into the BIOS trunk source code.

Optionally, after invoking a preset compatibility test script to perform a compatibility test on the new BIOS branch code, the method further includes: if the new BIOS branch code fails the compatibility test, determining the new BIOS branch code The compatibility test result is that the test fails, and the compatibility test result of the new BIOS branch code is fed back.

Therefore, in the case that the new BIOS branch code fails the compatibility test, it is directly determined that the new BIOS branch code fails the test, the test efficiency is improved, and the new BIOS branch source code with compatibility defects is prevented from being merged into the BIOS trunk source code , preventing compatibility issues from flowing into the BIOS backbone source code.

Optionally, before acquiring the code merge request input by the user, the method further includes: acquiring a preset compatibility test script uploaded by the user, and storing the preset compatibility test script in a preset storage location. The user uploads the preset compatibility test script to the electronic device. The electronic device stores the preset compatibility test script in a preset storage location. The preset storage location may be a memory or other storage device in the electronic device.

Thus, the preset compatibility test script is stored in the preset storage location, so that the compatibility test process can call the preset compatibility test script in real time, and automatically perform compatibility test on the new BIOS branch code, thereby improving test efficiency.

Step 103: If the compatibility test result fed back by the compatibility test process is that the test is passed, the new BIOS branch source code is merged into the BIOS main source code to generate a new BIOS main source code.

Optionally, the compatibility test result fed back by the compatibility test process is that the test is passed, indicating that there is no compatibility problem in the new BIOS branch source code, then the new BIOS branch source code is merged into the BIOS trunk source code Generate new BIOS backbone source code.

Optionally, after the new BIOS branch source code is merged into the BIOS trunk source code to generate the new BIOS trunk source code, the method further includes: compiling the new BIOS trunk source code with a compiler to obtain a new BIOS code; The code is burned into the chip of the specified electronic device. Provides the lowest-level, most direct hardware setup and control for specified electronic devices through the new BIOS code.

Optionally, after sending a control instruction to the compatibility test process, instructing the compatibility test process, compiling the new BIOS branch source code to obtain the new BIOS branch code, and performing the new BIOS branch code in the simulator. After the compatibility test is performed and the compatibility test result of the new BIOS branch code is fed back, the method further includes: if the compatibility test result fed back by the compatibility test process is a test failure, providing the merge failure prompt information to the The user; wherein the merging failure prompt information is used to prompt that the merging of the new BIOS branch source code and the BIOS main source code fails, and after the modification of the new BIOS branch source code is completed, re-enter the code merging request.

Optionally, the compatibility test result fed back by the compatibility test process is a test failure, indicating that there is a compatibility problem in the new BIOS branch source code, then automatically blocking the new BIOS branch source code from being merged into the BIOS trunk source code , providing the user with the prompt information of the merge failure, so that the user can determine that the merge of the new BIOS branch source code and the BIOS trunk source code fails, and after the modification of the new BIOS branch source code is completed, re-enter the code to merge ask.

Therefore, in the case of a new BIOS branch code test failure, the new BIOS branch source code is automatically blocked from being merged into the BIOS trunk source code, so as to prevent the new BIOS branch source code with compatibility defects from being merged into the BIOS trunk source code, preventing compatibility. The problem flows into the BIOS backbone source code.

In the technical solution of the embodiment of the present invention, the code merge request input by the user is obtained, and the code merge request carries the source code of the new BIOS branch; then a control instruction is sent to the compatibility test process, indicating the compatibility test process, and the new BIOS branch source code is carried out. Compile, get the new BIOS branch code, test the compatibility of the new BIOS branch code in the simulator, and feed back the compatibility test result of the new BIOS branch code; Merge the BIOS main source code to generate a new BIOS main source code, which solves the test scheme of the BIOS code in the related technology. It cannot prevent the standard compatibility problem from flowing into the BIOS main source code in advance, which will occupy a lot of hardware resources and increase the test cost. , get the compatibility test before the code is merged, realize the prevention of the compatibility problem of the BIOS trunk source code, prevent the compatibility problem from flowing into the code trunk, and truly realize the compatibility of the BIOS code before the problem occurs. problems, which greatly reduces the possible impact of compatibility problems. At the same time, by conducting compatibility tests under the simulator, the dependence of the compatibility test process on physical machines is reduced, the portability of the test environment is improved, and the Beneficial effects of testing costs.

Embodiment 2

FIG. 2 is a flowchart of a code testing method according to Embodiment 2 of the present invention. This embodiment of the present invention may be combined with each optional solution in one or more of the foregoing embodiments. As shown in Figure 2, the method includes:

Step 201: Obtain a code merge request input by a user, where the code merge request carries the source code of the new BIOS branch.

Step 202: Send a control instruction to the compatibility test process, instruct the compatibility test process, compile the new BIOS branch source code to obtain a new BIOS branch code, and perform compatibility with the new BIOS branch code in the simulator and feedback the compatibility test results of the new BIOS branch code.

Step 203: If the compatibility test result fed back by the compatibility test process is that the test fails, provide the user with prompt information of merge failure.

Wherein, the merging failure prompt information is used to prompt that the merging of the new BIOS branch source code and the BIOS main source code fails, and after the modification of the new BIOS branch source code is completed, a code merging request is input again.

Optionally, the compatibility test result fed back by the compatibility test process is a test failure, indicating that there is a compatibility problem in the new BIOS branch source code, then automatically blocking the new BIOS branch source code from being merged into the BIOS trunk source code , providing the user with the prompt information of the merge failure, so that the user can determine that the merge of the new BIOS branch source code and the BIOS trunk source code fails, and after the modification of the new BIOS branch source code is completed, re-enter the code to merge ask.

Therefore, in the case of a new BIOS branch code test failure, the new BIOS branch source code is automatically blocked from being merged into the BIOS trunk source code, so as to prevent the new BIOS branch source code with compatibility defects from being merged into the BIOS trunk source code, preventing compatibility. The problem flows into the BIOS backbone source code.

The technical solution of the embodiment of the present invention takes the compatibility test before code merging, realizes the prevention of the compatibility problem of the BIOS main source code, prevents the compatibility problem from flowing into the code main body, and truly realizes the problem before the problem occurs. Solved the compatibility problem of BIOS code, greatly reducing the possible impact of compatibility problems. At the same time, by conducting compatibility testing under the simulator, the dependence of the compatibility testing process on physical machines is reduced, and the test environment is improved. Portability also has the beneficial effect of reducing the cost of testing.

Embodiment 3

3 is a flowchart of a code testing method provided in Embodiment 3 of the present invention, comprising the following steps:

Step 301: Obtain a code merge request input by a user, where the code merge request carries the source code of the new BIOS branch.

Step 302: Send a control instruction to the compatibility test process, instruct the compatibility test process, compile the new BIOS branch source code to obtain a new BIOS branch code, and perform compatibility with the new BIOS branch code in the simulator The compatibility test is performed, and the compatibility test result of the new BIOS branch code is fed back: if the compatibility test result fed back by the compatibility test process is that the test has passed, then step 303 is executed; If the test result is that the test fails, step 304 is executed.

Step 303: Merge the new BIOS branch source code into the BIOS trunk source code to generate a new BIOS trunk source code.

Step 304 , providing the user with prompt information of a merge failure.

Wherein, the merging failure prompt information is used to prompt that the merging of the new BIOS branch source code and the BIOS main source code fails, and after the modification of the new BIOS branch source code is completed, a code merging request is input again.

The technical solution of the embodiment of the present invention takes the compatibility test before code merging, realizes the prevention of the compatibility problem of the BIOS main source code, prevents the compatibility problem from flowing into the code main body, and truly realizes the problem before the problem occurs. Solved the compatibility problem of BIOS code, greatly reducing the possible impact of compatibility problems. At the same time, by conducting compatibility testing under the simulator, the dependence of the compatibility testing process on physical machines is reduced, and the test environment is improved. Portability also has the beneficial effect of reducing the cost of testing.

Embodiment 4

FIG. 4 is a schematic structural diagram of a code testing apparatus according to Embodiment 4 of the present invention. The apparatus may be configured in an electronic device. As shown in FIG. 4 , the apparatus includes: a request obtaining module 401, a code testing module 402 and a code merging module 403.

Wherein, the request acquisition module 401 is used to acquire the code merge request input by the user, and the code merge request carries the source code of the new BIOS branch; the code test module 402 is used to send a control instruction to the compatibility test process, indicating the compatibility In the test process, the new BIOS branch source code is compiled to obtain the new BIOS branch code, the compatibility test is performed on the new BIOS branch code in the simulator, and the compatibility test result of the new BIOS branch code is fed back; The code merging module 403 is configured to merge the new BIOS branch source code into the BIOS main source code to generate a new BIOS main source code if the compatibility test result fed back by the compatibility test process is the test passed.

In the technical solution of the embodiment of the present invention, the code merge request input by the user is obtained, and the code merge request carries the source code of the new BIOS branch; then a control instruction is sent to the compatibility test process, indicating the compatibility test process, and the new BIOS branch source code is carried out. Compile, get the new BIOS branch code, test the compatibility of the new BIOS branch code in the simulator, and feed back the compatibility test result of the new BIOS branch code; Merge the BIOS main source code to generate a new BIOS main source code, which solves the test scheme of the BIOS code in the related technology. It cannot prevent the standard compatibility problem from flowing into the BIOS main source code in advance, which will occupy a lot of hardware resources and increase the test cost. , get the compatibility test before the code is merged, realize the prevention of the compatibility problem of the BIOS trunk source code, prevent the compatibility problem from flowing into the code trunk, and truly realize the compatibility of the BIOS code before the problem occurs. problems, which greatly reduces the possible impact of compatibility problems. At the same time, by conducting compatibility tests under the simulator, the dependence of the compatibility test process on physical machines is reduced, the portability of the test environment is improved, and the Beneficial effects of testing costs.

In an optional implementation of the embodiment of the present invention, optionally, the code testing module 402 executes the instruction of the compatibility testing process, compiles the source code of the new BIOS branch, obtains the new BIOS branch code, and simulates When the compatibility test is performed on the new BIOS branch code in the compiler, and the operation of feeding back the compatibility test result of the new BIOS branch code is specifically used for: instructing the compatibility test process to perform the following operations: through the compiler Compile the source code of the new BIOS branch; if the compilation is successful, and obtain the new BIOS branch code, then run the new BIOS branch code in the simulator, and during the running process of the new BIOS branch code, call the preset The compatibility test script performs a compatibility test on the new BIOS branch code; if the new BIOS branch code passes the compatibility test, it is determined that the compatibility test result of the new BIOS branch code is the test passed, and the new BIOS branch code is fed back. Compatibility test results for BIOS branch code.

In an optional implementation manner of the embodiment of the present invention, optionally, after the new BIOS branch source code is compiled by a compiler, the method further includes: if the compilation fails, determining the compatibility of the new BIOS branch code The result of the compatibility test is that the test fails, and the compatibility test result of the new BIOS branch code is fed back.

In an optional implementation manner of the embodiment of the present invention, optionally, after calling a preset compatibility test script to perform a compatibility test on the new BIOS branch code, the method further includes: if the new BIOS branch code does not have If the compatibility test is passed, it is determined that the compatibility test result of the new BIOS branch code is a test failure, and the compatibility test result of the new BIOS branch code is fed back.

In an optional implementation manner of the embodiment of the present invention, optionally, the code testing apparatus further includes: a prompt information providing module, configured to combine the test results if the compatibility test result fed back by the compatibility test process is a test failure. The failure prompt information is provided to the user; wherein, the merge failure prompt information is used to prompt that the new BIOS branch source code and the BIOS trunk source code fail to merge, and after the modification of the new BIOS branch source code is completed, re-enter the code merge request.

In an optional implementation of the embodiment of the present invention, optionally, the request obtaining module 401 is specifically configured to: obtain a code merging request input by a user through a code merging page, where the code merging request carries the source code of the new BIOS branch.

In an optional implementation manner of the embodiment of the present invention, optionally, the code testing apparatus further includes: a script obtaining module, configured to obtain a preset compatibility test script uploaded by a user, and use the preset compatibility test script to The script is stored to the preset storage location.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

The above code testing apparatus can execute the code testing method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the code testing method.

Embodiment 5

FIG. 5 shows a schematic structural diagram of an electronic device 10 that can be used to implement the code testing method according to the embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices (eg, helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended 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., connected in communication with the at least one processor 11, wherein the memory stores There is a computer program executable by at least one processor, the processor 11 can be implemented according to a computer program stored in a read only memory (ROM) 12 or a computer program constructed from a storage unit 18 into a random access memory (RAM) 13. Various appropriate actions and processes are performed. In the RAM 13, various programs and data necessary for the operation of the electronic device 10 can also be stored. The processor 11 , the ROM 12 and the RAM 13 are connected to each other through a bus 14 . An input/output (I/O) interface 15 is also connected to the 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, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc. etc.; and a communication unit 19, such as a network card, modem, wireless communication transceiver, and the like. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

The processor 11 may be various general and/or special purpose processing components having processing and computing capabilities. Some examples of processors 11 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various specialized artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as code testing methods.

In some embodiments, the code testing 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 on 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 code testing method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the code testing method by any other suitable means (eg, by means of firmware).

Various implementations of the systems and techniques described herein 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 chips system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor The processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.

Computer programs for implementing the code testing methods 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/operations specified in the flowcharts and/or block diagrams to be carried out. 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 may contain or store a computer program for use by or in connection with the instruction execution system, apparatus or device. Computer-readable storage media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

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

The systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user's computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the Internet.

A computing system can include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or a cloud host. It is a host product in the cloud computing service system to solve the traditional physical host and VPS services, which are difficult to manage and weak in business scalability. defect.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, the steps described in the present invention can be performed in parallel, sequentially or in different orders, and as long as the desired results of the technical solutions of the present invention can be achieved, no limitation is imposed herein.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a code testing method, is characterized in that, comprises: Obtain the code merge request input by the user, and the code merge request carries the new BIOS branch source code; Sending a control instruction to the compatibility test process, instructing the compatibility test process, compiling the new BIOS branch source code to obtain a new BIOS branch code, and performing a compatibility test on the new BIOS branch code in the simulator, And feedback the compatibility test result of the new BIOS branch code; If the compatibility test result fed back by the compatibility test process is that the test is passed, the new BIOS branch source code is merged into the BIOS main source code to generate a new BIOS main source code. 2. The method according to claim 1, wherein the instructing the compatibility test process, compiling the new BIOS branch source code to obtain a new BIOS branch code, and performing the new BIOS branch code in the simulator. The BIOS branch code is tested for compatibility, and the compatibility test results of the new BIOS branch code are fed back, including: Instruct the compatibility testing process to do the following: Compile the source code of the new BIOS branch by a compiler; If the compilation is successful and a new BIOS branch code is obtained, the new BIOS branch code is run in the simulator, and during the running process of the new BIOS branch code, a preset compatibility test script is called for the new BIOS branch code. Code for compatibility testing; If the new BIOS branch code passes the compatibility test, it is determined that the compatibility test result of the new BIOS branch code is the test passed, and the compatibility test result of the new BIOS branch code is fed back. 3. The method according to claim 2, wherein after compiling the new BIOS branch source code by a compiler, further comprising: If the compilation fails, it is determined that the compatibility test result of the new BIOS branch code is a test failure, and the compatibility test result of the new BIOS branch code is fed back. 4. The method according to claim 2, characterized in that, after invoking a preset compatibility test script to carry out a compatibility test to the new BIOS branch code, further comprising: If the new BIOS branch code fails the compatibility test, it is determined that the compatibility test result of the new BIOS branch code is a test failure, and the compatibility test result of the new BIOS branch code is fed back. 5. The method according to claim 1, characterized in that, in sending a control instruction to a compatibility test process, instructing the compatibility test process, compiling the new BIOS branch source code to obtain a new BIOS branch code, After the compatibility test is performed on the new BIOS branch code in the simulator, and the compatibility test result of the new BIOS branch code is fed back, the method further includes: If the compatibility test result fed back by the compatibility test process is that the test fails, provide the user with prompt information of merge failure; Wherein, the merging failure prompt information is used to prompt that the merging of the new BIOS branch source code and the BIOS main source code fails, and after the modification of the new BIOS branch source code is completed, the code merging request is re-input. 6. The method according to claim 1, wherein the code merging request input by the user, the code merging request carrying a new BIOS branch source code, comprises: Through the code merging page, a code merging request input by the user is obtained, where the code merging request carries the source code of the new BIOS branch. 7. The method according to claim 2, wherein before acquiring the code merge request input by the user, further comprising: Acquire a preset compatibility test script uploaded by the user, and store the preset compatibility test script in a preset storage location. 8. a code testing device, is characterized in that, comprises: a request acquisition module for acquiring a code merge request input by a user, where the code merge request carries the new BIOS branch source code; The code test module is used for sending control instructions to the compatibility test process, instructing the compatibility test process, compiling the source code of the new BIOS branch, obtaining the new BIOS branch code, and performing the new BIOS branch code in the simulator The code is tested for compatibility, and the compatibility test result of the new BIOS branch code is fed back; A code merging module, configured to merge the new BIOS branch source code into the BIOS main source code to generate a new BIOS main source code if the compatibility test result fed back by the compatibility test process is the test passed. 9. An electronic device, characterized in that the electronic device comprises: 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 executed by the at least one processor to enable the at least one processor to perform any of claims 1-7 The described code testing method. 10. A computer-readable storage medium, characterized in that, the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method described in any one of claims 1-7 when executed. Code testing methods.

Images