Test document generation method and device based on FPGA software test

Abstract

The invention relates to the field of computers, in particular to a test document generation method and device based on FPGA software testing. The method comprises the following steps: displaying an input interface; the input interface is used for prompting a user to input the test content corresponding to the FPGA software test; in the input interface, receiving a first user operation used for inputting first test content; according to the first test content, generating a target test document conforming to a preset document template; the target test document comprises at least one of a test plan used for describing the test content of the FPGA software test or a test report used for describing the test result of the FPGA software test.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method and device for generating test documents based on FPGA software testing. Background Art

[0002] Field-Programmable Gate Array (FPGA) is a commonly used programmable logic device. Currently, FPGA software testing typically requires the preparation of test documentation so that technicians can understand the FPGA software test content and corresponding test results by reading the test documentation.

[0003] In the prior art, technicians are usually required to spend a lot of time manually writing test documents, and the manually written test documents may contain human errors.

[0004] Therefore, how to generate test documents more efficiently and accurately is a problem that needs to be solved at present. Summary of the Invention

[0005] In order to solve the above technical problems, the present application provides a test document generation method and device based on FPGA software testing.

[0006] In a first aspect, the present application provides a test document generation method based on FPGA software testing, which is applied to a test document generation device, and the method includes: displaying an entry interface; the entry interface is used to prompt a user to enter the test content corresponding to this FPGA software test; in the entry interface, receiving a first user operation for entering a first test content; based on the first test content, generating a target test document that conforms to a preset document template; the target test document includes: a test plan for describing the test content of this FPGA software test or at least one of a test report for describing the test results of this FPGA software test.

[0007] In some implementations, the entry interface includes a first interactive area for entering test items, a second interactive area for entering test cases corresponding to the test items, and a third interactive area for entering test steps corresponding to the test cases; the first test content includes: the test items corresponding to this FPGA software test, the test cases corresponding to each test item, and the test steps corresponding to each test case.

[0008] In some implementations, the method further includes: displaying a project information interface; the project information interface is used to prompt a user to enter project information corresponding to this FPGA software test; in the project information interface, receiving a second user operation for inputting first project information; generating a target test document based on the first test content and a preset document template, including: generating a target test document that conforms to a preset document template based on the first project information and the first test content.

[0009] In some implementations, the method further includes: generating statistical results based on the first test content; the statistical results include: at least one of the completion process of each test case and the impact domain relationship between the test cases.

[0010] In some implementations, the method further includes: storing the target test document in a document library according to the document type corresponding to the target test document and in a classified management manner; wherein the document library is used to record the test documents generated in the completed FPGA software test.

[0011] In some implementations, the method further includes: displaying a document search interface; the document search interface includes a fifth interactive area; the fifth interactive area is used to prompt a user to input document information; in the document search interface, receiving a third user operation for inputting first document information; displaying a set of test documents that conform to the first document information in the test documents stored in the document library; the document library is used to record test documents generated in completed FPGA software testing.

[0012] In some implementations, the method further includes: receiving a fourth user operation for performing a target modification on a target test document; generating a modified test file obtained after performing the target modification on the target test document; storing the modified test file and the modification history in a document library; the modification history is used to indicate that the modified test file is obtained after performing the target modification on the target test document; and the document library is used to record the test documents generated in the completed FPGA software test.

[0013] In some implementations, the method further includes: displaying a preset control in a display interface during FPGA software testing according to the first test content; displaying a preset input box in response to a fifth user operation on the preset control; receiving a sixth user operation for inputting a target text into the preset input box; generating a record log including the target text, and adding the record log to a record log collection corresponding to this FPGA software test; the record log collection may include: one or more record logs generated in this FPGA software test.

[0014] In the second aspect, the present application provides a test document generation device, including: a display unit for displaying an entry interface; the entry interface is used to prompt a user to enter the test content corresponding to this FPGA software test; a processing unit for receiving a first user operation for entering a first test content in the entry interface; the processing unit is also used to generate a target test document based on the first test content and a preset document template; the target test document includes: at least one item in the test plan or test report of this FPGA software test.

[0015] In some implementations, the entry interface includes a first interactive area for entering test items, a second interactive area for entering test cases corresponding to the test items, and a third interactive area for entering test steps corresponding to the test cases; the first test content includes: the test items corresponding to this FPGA software test, the test cases corresponding to each test item, and the test steps corresponding to each test case.

[0016] In some implementations, the display unit is also used to display a project information interface; the project information interface is used to prompt the user to enter project information corresponding to this FPGA software test; the processing unit is also used to receive a second user operation for inputting first project information in the project information interface; the processing unit is also used to generate a target test document based on the first test content and a preset document template, including: the processing unit is also used to generate a target test document that conforms to a preset document template based on the first project information and the first test content.

[0017] In some implementations, the processing unit is further configured to generate statistical results based on the first test content; the statistical results include at least one of the completion process of each test case and the impact domain relationship between the test cases.

[0018] In some implementations, the processing unit is further used to store the target test document in a document library according to the document type corresponding to the target test document and in a classified management manner; wherein the document library is used to record the test documents generated in the completed FPGA software test.

[0019] In some implementations, the display unit is also used to display a document search interface; the document search interface includes a fifth interaction area; the fifth interaction area is used to prompt the user to input document information; the processing unit is also used to receive a third user operation for inputting first document information in the document search interface; the processing unit is also used to display a set of test documents that conform to the first document information in the test documents stored in the document library; the document library is used to record test documents generated in completed FPGA software tests.

[0020] In some implementations, the processing unit is further used to receive a fourth user operation for performing a target modification on a target test document; the processing unit is further used to generate a modified test file obtained after performing a target modification on the target test document; the processing unit is further used to store the modified test file and the modification history in a document library; the modification history is used to indicate that the modified test file is obtained after performing a target modification on the target test document; the document library is used to record the test documents generated in the completed FPGA software test.

[0021] In some implementations, the display unit is further used to display a preset control in a display interface during the process of performing FPGA software testing according to the first test content; the processing unit is further used to display a preset input box in response to a fifth user operation on the preset control; the processing unit is further used to receive a sixth user operation for inputting a target text into the preset input box; the processing unit is further used to generate a record log including the target text, and add the record log to a record log collection corresponding to this FPGA software test; the record log collection may include: one or more record logs generated in this FPGA software test.

[0022] In a third aspect, a test document generation device is provided, comprising: a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to enable the test document generation device to implement a method as in the first aspect or any implementation method of the first aspect when executing the computer program.

[0023] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computing device, the computing device implements the method as in the first aspect or any implementation method in the first aspect.

[0024] In a fifth aspect, a computer program product is provided, which, when executed on a computer, enables the computer to implement the method according to the first aspect or any one of the implementations of the first aspect.

[0025] The technical solution provided by the embodiments of the present application has the following advantages compared with the prior art:

[0026] Through the technical solution provided in the embodiment of the present application, not only can the test document generation device be used to generate test documents more efficiently and accurately, but the user can also be guided to enter the test content corresponding to the current FPGA software test by displaying an input interface, thereby improving the user experience. In addition, the technical solution provided in the embodiment of the present application can generate a target test document that conforms to a preset document template. In this way, the format and template of the same document can be used to ensure that all generated documents have a consistent structure and style, which is easy to read and manage. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0028] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0029] Figure 1 One of the flow charts of a test document generation method provided in an embodiment of the present application;

[0030] Figure 2 This is one of the schematic diagrams of a display interface provided in an embodiment of the present application;

[0031] Figure 3 This is a second schematic diagram of a display interface provided in an embodiment of the present application;

[0032] Figure 4 A second flow chart of a test document generation method provided in an embodiment of the present application;

[0033] Figure 5 This is a third schematic diagram of a display interface provided in an embodiment of the present application;

[0034] Figure 6 A third flow chart of a test document generation method provided in an embodiment of the present application;

[0035] Figure 7 A fourth flow chart of a test document generation method provided in an embodiment of the present application;

[0036] Figure 8 A fifth flow chart of a test document generation method provided in an embodiment of the present application;

[0037] Figure 9A fourth schematic diagram of a display interface provided in an embodiment of the present application;

[0038] Figure 10 Flowchart 6 of a test document generation method provided in an embodiment of the present application;

[0039] Figure 11 Flowchart 7 of a test document generation method provided in an embodiment of the present application;

[0040] Figure 12 One of the structural diagrams of a test document generation device provided in an embodiment of the present application;

[0041] Figure 13 This is a second structural diagram of a test document generation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to more clearly understand the above-mentioned objectives, features and advantages of the present application, the scheme of the present application will be further described below. It should be noted that, in the absence of conflict, the embodiments of the present application and the features therein can be combined with each other.

[0043] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application can also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present application, not all of the embodiments.

[0044] The technical solutions provided in the embodiments of the present application are introduced below with reference to examples.

[0045] In the current Field-Programmable Gate Array (FPGA) software testing process, it is usually necessary to write corresponding test documents so that technicians can understand the content of the FPGA software test and the corresponding test results by reading the test documents. However, traditional FPGA software testing methods usually rely on technicians to manually write test documents. Among them, the test documents referred to in the embodiments of the present application may specifically include: a test plan for describing the test content of this FPGA software test, and the test documents may also include: a test report for describing the test results of this FPGA software test. This method of technicians manually writing test documents is not only time-consuming and labor-intensive, but also prone to human errors, resulting in uneven document quality.

[0046] In view of the above problems, the embodiments of the present application take into account: on the one hand, a test document generation device can be designed by software or hardware, and then the test document generation device can be used to generate test documents, thereby replacing manual writing of test documents; on the other hand, in order to facilitate user operation, the user can be guided to enter the corresponding test content into the test document generation device by displaying a corresponding input interface (wherein the input interface can be used to prompt the user to enter the test content corresponding to this test). And after receiving the first user operation for entering the test content (hereinafter referred to as the first test content), a target test document that conforms to the preset document template can be generated according to the first test content. In this way, the technical solution provided by the embodiment of the present application can not only generate test documents more efficiently and accurately, but also guide the user to enter the test content corresponding to this FPGA software test by displaying the input interface, thereby improving the user's experience. In addition, the technical solution provided by the embodiment of the present application can generate a target test document that conforms to the preset document template, which helps to unify the format and template of the test document, ensuring that all generated documents have a consistent structure and style, which is easy to read and manage.

[0047] The technical solution provided by the embodiment of the present application is described in detail below with reference to examples. Specifically, the embodiment of the present application provides a test document generation method based on FPGA software testing. Among them, the execution subject of the test document generation method based on FPGA software testing can be a test document generation device. When the test document generation device is running, it can be used to execute all or part of the steps in the test document generation method based on FPGA software testing provided by the embodiment of the present application. Among them, in actual application, the function of the test document generation device can be implemented by a personal computer (including desktop computers, laptop computers, handheld computers and notebook computers, etc.), or electronic devices such as smart phones and servers; or, the function of the above-mentioned test document generation device can also be implemented by some hardware / software devices in the above-mentioned electronic devices. The embodiment of the present application does not impose any special restrictions on the specific form of the test document generation device.

[0048] like Figure 1 As shown, the test document generation method based on FPGA software testing provided in the embodiment of the present application may include:

[0049] S101. The test document generating device displays an input interface.

[0050] The input interface is used to prompt the user to input the test content corresponding to this FPGA software test.

[0051] In some implementations, the test content corresponding to this FPGA software test may include: one or more test items included in this FPGA software test, one or more test cases included in each test item, and one or more test steps included in each test case.

[0052] Specifically, the test items included in an FPGA software test may include: code review, functional testing, logic testing, timing testing, power analysis, performance testing, static analysis, data processing testing, boundary testing, interface testing, security testing, strength testing, document review, and margin testing, etc.

[0053] It is understood that, during implementation, the test content corresponding to FPGA software testing may vary as the actual test scenario changes. For example, in some scenarios, when the user does not need to enter test steps, the test content entered by the user may only include test items and test cases without test steps.

[0054] S102: The test document generating apparatus receives a first user operation for entering first test content in an input interface.

[0055] In some implementations, the entry interface includes a first interaction area for entering a test item, a second interaction area for entering a test case corresponding to the test item, and a third interaction area for entering a test step corresponding to the test case.

[0056] Furthermore, the first user operation may specifically include: user operations on the first interaction area, the second interaction area, and the third interaction area.

[0057] The first test content mentioned above may specifically include: the test items included in this FPGA software test, the test cases included in each test item, and the test steps included in each test case.

[0058] For example, Figure 2 As shown, the input interface 20 may include an interactive area 201 for inputting test items. By receiving the user's operation on the interactive area 201, the test document generation device can obtain information related to the test item, such as: "test item name", "test item identification", "test content", "test method, sufficiency and evaluation criteria" and "test termination conditions". In other words, Figure 2 In the example shown, the first interaction area may include interaction area 201 .

[0059] In addition, the input interface 20 also includes an interactive area 202 for inputting test cases. By receiving user operations on the interactive area 202, the test document generating apparatus can determine the test cases corresponding to the test items.

[0060] Further, when the user clicks on the test case in the interactive area 202, as shown in FIG. Figure 3 As shown, the input interface 20 may display an interactive area 203 and an interactive area 204. By receiving the user's operation on the interactive area 203, the test document generation device may determine information such as the test case name, identifier, and traceability relationship of the test case. In addition, by receiving the user's operation on the interactive area 204, the test document generation device may determine the test steps included in the test case. In other words, Figure 2 and Figure 3 In the example shown, the second interaction area may include interaction area 202 and interaction area 203, and the third interaction area may include interaction area 204. The first user operation may include the user Figure 2 and Figure 3 User operations in the input interface 20 are shown.

[0061] S103: The test document generating device generates a target test document that conforms to a preset document template according to the first test content.

[0062] The target test document includes at least one of a test plan for describing the test content of this FPGA software test or a test report for describing the test results of this FPGA software test.

[0063] Specifically, the test document generation device can be pre-configured with standardized preset document templates. These preset document templates may specifically include a test plan template and a test report template. This allows the test document generation device to generate target test documents that conform to the preset document templates. Furthermore, in different FPGA software tests, the test document generation device can generate test documents that conform to the preset document templates, ensuring that all generated documents have a consistent structure and style, making them easier to read and manage.

[0064] It should be noted that, for ease of description, in the embodiments of this application, the document used to describe the test content of the FPGA software test is referred to as a "test plan," and the document used to describe the test results of the FPGA software test is referred to as a "test report." Specifically, the test plan may include: basic information about the test project, information about the test items, information about the test cases included in each test item, information about the test steps included in each test case, etc. The test report may include: the test results of each test step during the test process, as well as the test results of the entire FPGA software test, etc.

[0065] In other words, the information recorded in the test plan is information that can be determined before the test is carried out, and the information recorded in the test report includes the test results obtained after the test. In actual application, the test plan can also be called a "test outline", "test plan", etc., and the "test report" can be called a "test conclusion", "test minutes", etc. That is to say, in the embodiment of the present application, there is no restriction on the names of the test plan and the test report. In actual application, as long as it is a document used to describe the test content of the FPGA software test, it can be understood as the "test plan" described in the embodiment of the present application; as long as it is a document used to describe the test results of the FPGA software test, it can be understood as the "test report" described in the embodiment of the present application.

[0066] In addition, when the target test document is a test report used to describe the test results of this FPGA software test, the target test document can specifically be a test report used to describe the test results of the entire FPGA software test. In addition, the target test document can also specifically be a test report used to describe the test results of a sub-step in the FPGA software test.

[0067] In some implementations, such as Figure 4 As shown, the method may further include:

[0068] S104: The test document generating device displays a project information interface.

[0069] Among them, the project information interface is used to prompt the user to enter the project information corresponding to this FPGA software test.

[0070] The project information may include: basic information about the test project corresponding to this FPGA software test, information about the party issuing the test project, etc.

[0071] S105: The test document generating apparatus receives, in the project information interface, a second user operation for inputting first project information.

[0072] For example Figure 5 As shown, the project information interface 30 includes an interactive area 301 and an interactive area 302. By receiving the user's operation on the interactive area 301, the test document generation device can obtain the information of the test project issuer, such as "client name", "client address", etc.; in addition, by receiving the user's operation on the interactive area 302, the test document generation device can obtain the basic information of the test project, such as "test project name", "test document confidentiality level", etc. In other words, the second user operation mentioned above can include the user's operation on the interactive area 301. Figure 5 User operations in the project information interface 30 are shown.

[0073] In addition, S103 may specifically include:

[0074] S103a: The test document generating device generates a target test document that conforms to a preset document template according to the first project information and the first test content.

[0075] For example, the test document generating device may perform corresponding data processing on the first project information and the data in the first test content, and fill the processed data into corresponding positions of a preset document template to obtain a target test document.

[0076] It should be noted that in Figure 4 In the example, S104 and S105 are executed before S101. In actual application, the execution order of each step in the method provided by the embodiment of the present application can be set according to actual needs. For example, the above S104-S105 can be executed at any time before S103a is executed. In other words, the execution order of each step in the method provided by the embodiment of the present application is determined by the logical relationship between each step. The order of description of each step in the embodiment of the present application and the execution order of each step in the accompanying drawings do not limit the implementation process of the solution of the embodiment of the present application.

[0077] Additionally, in some implementations, such as Figure 6 As shown, the method may further include:

[0078] S106. The test document generating device generates statistical results according to the first test content.

[0079] The statistical results include: the completion process of each test case and the impact domain relationship between the test cases.

[0080] Through the above implementation, after the user enters the test content corresponding to this FPGA software test, not only can the corresponding test document be generated, but also statistics can be generated for the first test content to obtain at least one of the completion progress of each test case and the impact domain relationship between test cases. This makes it convenient for technicians to review the above statistical results.

[0081] In some designs, after obtaining the statistical results through S106, the statistical results may be added to the target test document so that the technicians can obtain the statistical results when consulting the target test document.

[0082] In other designs, after obtaining the statistical results in S106 , the statistical results may be stored in a test statistics library. The test statistics library records the statistical results corresponding to each completed FPGA software test. In this way, technicians can search the test statistics library for the statistical results of the corresponding FPGA software test.

[0083] In some implementations, such as Figure 7 As shown, the method may further include:

[0084] S107 . The test document generating device stores the target test document in a document library according to the document type corresponding to the target test document and in a classified management manner.

[0085] The document library is used to record the test documents generated during the completed FPGA software testing.

[0086] For example, the classification management method may specifically include: setting different indexes for test documents of different document types in the document library to facilitate searching for test documents of different document types. For another example, the classification management method may specifically include: storing test documents of different document types in different storage areas in the document library.

[0087] In some implementations, such as Figure 8 As shown, the method may further include:

[0088] S108. The test document generating device displays a document search interface.

[0089] The document search interface includes a fifth interactive area, which is used to prompt the user to input document information.

[0090] The document information may specifically include: file name, document type, publishing unit, and publishing date, etc.

[0091] S109: The test document generating device receives a third user operation for inputting first document information in the document search interface.

[0092] For example Figure 9 As shown, the document search interface 40 includes an interactive area 401. By receiving the user's operation on the interactive area 401, the test document generation device can obtain the document information such as "file name", "document type", "publishing unit" and "publishing date". In other words, the third user operation can include the user's Figure 9 User operations in the interactive area 401 are shown.

[0093] S110. The test document generating apparatus displays a set of test documents that match the first document information among the test documents stored in the document library.

[0094] The document library is used to record the test documents generated during the completed FPGA software testing.

[0095] For example, after the target test document is stored in the document library through S107 above, the user can enter the document information corresponding to the target test document in the fifth interactive area in the document search interface, so that the test document set including the target test document can be displayed on the interface.

[0096] In some implementations, such as Figure 10 As shown, the method may further include:

[0097] S111. The test document generating apparatus receives a fourth user operation for performing a target modification on a target test document.

[0098] For example, after the target test document is stored in the document library through the above S107 , the user can also find the target test document through the above process of S108 - S110 and modify the target test document through the fourth user operation.

[0099] The target modification includes: deleting, updating, adding, etc. the information included in the target test document.

[0100] S112. The test document generating device generates a modified test file obtained by performing target modification on the target test document.

[0101] S113: The test document generating device stores the modified test file and the modification history in a document library.

[0102] The modification history is used to indicate that the modified test file is obtained after the target test document is modified. The document library is used to record the test documents generated in the completed FPGA software test.

[0103] Through the above implementation method, on the one hand, the user can modify the target test document as needed. On the other hand, by storing the modified test file and modification history in the document library after the user modifies the target test document, the consistency and traceability of the document version can be guaranteed.

[0104] In some implementations, such as Figure 11 As shown, the method may further include:

[0105] S114 . The test document generating device displays preset controls in a display interface during the process of performing FPGA software testing according to the first test content.

[0106] For example, after the test document generation device receives the first user operation according to the content of S102, the test document generation device can obtain the first test content. The test document generation device can then perform FPGA software testing according to the first test content to obtain the results of the FPGA software testing, and then generate a test report describing the test results of this FPGA software testing. In particular, during the process of performing FPGA software testing according to the first test content, the test document generation device can display preset controls on the display interface.

[0107] S115 . The test document generating apparatus displays a preset input box in response to a fifth user operation on the preset control.

[0108] S116. The test document generating apparatus receives a sixth user operation for inputting a target text into a preset input box.

[0109] For example, during FPGA software testing, when an abnormal situation occurs, the user can click on the preset control in the display interface (i.e., the fifth user operation) to display the preset input box, and then the user can enter the target text for recording the abnormal situation into the preset input box through the sixth user operation.

[0110] S117 , the test document generating device generates a record log including the target text, and adds the record log to the record log set corresponding to this FPGA software test.

[0111] The record log set may include: one or more record logs generated during this FPGA software test.

[0112] Through the above implementation, on the one hand, through the contents of the above S114-S116, the user can record information such as abnormal situations that occur during the test at any time during the FPGA software test; on the other hand, after the test is completed, one or more record logs generated in this FPGA software test can be found in the record log collection for subsequent analysis and processing.

[0113] Based on the same inventive concept, as an implementation of the above method, an embodiment of the present application also provides a test document generation device, which corresponds to the aforementioned method embodiment. For ease of reading, this embodiment will no longer repeat the details of the aforementioned method embodiment one by one, but it should be clear that the test document generation device in this embodiment can correspond to all the contents of the aforementioned method embodiment.

[0114] The present application embodiment provides a test document generation device, Figure 12 A structural diagram of the test document generating device is shown as follows: Figure 12As shown, the test document generating device 50 includes:

[0115] The display unit 501 is used to display an input interface; the input interface is used to prompt the user to enter the test content corresponding to this FPGA software test;

[0116] The processing unit 502 is configured to receive, in the input interface, a first user operation for inputting first test content;

[0117] The processing unit 502 is also used to generate a target test document that conforms to a preset document template based on the first test content; the target test document includes: a test plan for describing the test content of this FPGA software test or at least one of a test report for describing the test results of this FPGA software test.

[0118] In some implementations, the entry interface includes a first interactive area for entering a test item, a second interactive area for entering a test case corresponding to the test item, and a third interactive area for entering a test step corresponding to the test case;

[0119] The first test content includes: test items corresponding to this FPGA software test, test cases corresponding to each test item, and test steps corresponding to each test case.

[0120] In some implementations, the display unit 501 is further configured to display a project information interface; the project information interface is configured to prompt the user to input project information corresponding to the current FPGA software test;

[0121] The processing unit 502 is further configured to receive, in the project information interface, a second user operation for inputting first project information;

[0122] The processing unit 502 is further configured to generate a target test document according to the first test content and a preset document template, including:

[0123] The processing unit 502 is further configured to generate a target test document conforming to a preset document template according to the first project information and the first test content.

[0124] In some implementations, the processing unit 503 is further configured to generate statistical results based on the first test content; the statistical results include at least one of the completion process of each test case and the impact domain relationship between the test cases.

[0125] In some implementations, the processing unit 503 is further used to store the target test document in a document library according to the document type corresponding to the target test document and in a classified management manner; wherein the document library is used to record the test documents generated in the completed FPGA software test.

[0126] In some implementations, the display unit 501 is further configured to display a document search interface; the document search interface includes a fifth interaction area; the fifth interaction area is configured to prompt the user to input document information;

[0127] The processing unit 502 is further configured to receive, in the document search interface, a third user operation for inputting first document information;

[0128] The processing unit 502 is further configured to display a set of test documents that conform to the first document information among the test documents stored in the document library; the document library is configured to record the test documents generated in the completed FPGA software test.

[0129] In some implementations, the processing unit 502 is further configured to receive a fourth user operation for performing a target modification on the target test document;

[0130] The processing unit 502 is further configured to generate a modified test file obtained by performing target modification on the target test document;

[0131] The processing unit 502 is also used to store the modified test file and the modification history in a document library; the modification history is used to indicate that the modified test file is obtained after the target test document is modified; the document library is used to record the test documents generated in the completed FPGA software test.

[0132] In some implementations, the display unit 501 is further configured to display preset controls in a display interface during the process of performing the FPGA software test according to the first test content;

[0133] The processing unit 502 is further configured to display a preset input box in response to a fifth user operation on the preset control;

[0134] The processing unit 502 is further configured to receive a sixth user operation for inputting a target text into the preset input box;

[0135] The processing unit 502 is further configured to generate a record log including the target text, and add the record log to a record log set corresponding to this FPGA software test; the record log set may include: one or more record logs generated in this FPGA software test.

[0136] The test document generation device 50 provided in the embodiment of the present application can execute the test document generation method provided in any of the above embodiments. Its implementation principle and technical effect are similar and will not be repeated here.

[0137] Based on the same inventive concept, an embodiment of the present application also provides a test document generating device. Figure 13 A schematic diagram of the structure of the test document generation device provided in the embodiment of the present application is shown as follows: Figure 13 As shown, the test document generating apparatus provided in this embodiment includes: a memory 601 and a processor 602 , wherein the memory 601 is used to store a computer program, and the processor 602 is used to execute the method provided in the above embodiment when executing the computer program.

[0138] Based on the same inventive concept, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the computing device implements the method provided in the above embodiment.

[0139] Based on the same inventive concept, an embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computing device to implement the method provided in the above embodiment.

[0140] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0141] The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0142] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0143] Computer-readable media includes both permanent and non-permanent, removable and non-removable storage media. Storage media can implement any method or technology for storing information, which can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0144] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some or all of the technical features therein, and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A test document generation method based on FPGA software testing, characterized in that: The method is applied to a test document generating device, and the method comprises: Displaying an input interface; the input interface is used to prompt the user to enter the test content corresponding to this FPGA software test; In the input interface, receiving a first user operation for inputting first test content; Based on the first test content, a target test document that conforms to a preset document template is generated; the target test document includes: a test plan for describing the test content of this FPGA software test, or at least one of a test report for describing the test results of this FPGA software test.

2. The method according to claim 1, characterized in that The input interface includes a first interactive area for inputting a test item, a second interactive area for inputting a test case corresponding to the test item, and a third interactive area for inputting a test step corresponding to the test case; The first test content includes: test items corresponding to this FPGA software test, test cases corresponding to each test item, and test steps corresponding to each test case.

3. The method according to claim 1, characterized in that The method further comprises: Display the project information interface; the project information interface is used to prompt the user to enter the project information corresponding to this FPGA software test; In the project information interface, receiving a second user operation for inputting first project information; Generating a target test document according to the first test content and a preset document template includes: A target test document conforming to a preset document template is generated according to the first project information and the first test content.

4. The method according to claim 1, wherein The method further comprises: Generate statistical results based on the first test content; the statistical results include at least one of the completion process of each test case and the impact domain relationship between the test cases.

5. The method according to claim 1, wherein The method further comprises: According to the document type corresponding to the target test document and in a classified management manner, the target test document is stored in a document library; wherein the document library is used to record the test documents generated in the completed FPGA software test.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Displaying a document search interface; the document search interface includes a fifth interactive area; the fifth interactive area is used to prompt the user to enter document information; In the document search interface, receiving a third user operation for inputting first document information; A test document set that matches the first document information among the test documents stored in the document library is displayed; the document library is used to record the test documents generated in the completed FPGA software test.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: receiving a fourth user operation for performing a target modification on the target test document; Generate a modified test file obtained by performing target modifications on the target test document; The modified test file and the modification history are stored in a document library; the modification history is used to indicate that the modified test file is obtained after the target test document is modified; the document library is used to record the test documents generated in the completed FPGA software test.

8. The method according to any one of claims 1 to 5, characterized in that The method further comprises: During the process of performing the FPGA software test according to the first test content, displaying a preset control in a display interface; In response to a fifth user operation on the preset control, displaying a preset input box; receiving a sixth user operation for inputting a target text into the preset input box; Generate a record log including the target text, and add the record log to a record log set corresponding to the current FPGA software test; the record log set may include: one or more record logs generated in the current FPGA software test.

9. A test document generating device, characterized in that: include: A display unit, used for displaying an input interface; The input interface is used to prompt the user to enter the test content corresponding to this FPGA software test; a processing unit, configured to receive, in the input interface, a first user operation for inputting first test content; The processing unit is further configured to generate a target test document according to the first test content and a preset document template; The target test document includes: at least one of the test plan or test report of this FPGA software test.

10. A test document generating device, characterized in that: include: A memory and a processor, wherein the memory is used to store a computer program, and the processor is used to enable the test document generating device to implement the method according to any one of claims 1 to 8 when executing the computer program.

Images