Testing method based on FPGA software integrated testing management platform and management platform

Through the automated testing methods and platforms based on the FPGA software integrated test management platform, the inefficiency and poor integration of coding specifications and quality control in FPGA software development are solved, automated testing and efficient collaboration are achieved, and development and testing efficiency is improved.

CN118916264AInactive Publication Date: 2024-11-08AEROSPACE SOFTWARE TECH (BEIJING) CO LTD

Patent Information

Application Number
CN202410906380.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-08
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

During the development of existing FPGA software, coding specifications and quality control rely on developers to manually execute special tools, resulting in inefficiency, inconvenient rule set management, low efficiency in result feedback and positioning, difficulty in tracking and rectification of results, and lack of integration with the test management platform. Inadequate automation.

Method used

Provide an integrated test management platform based on FPGA software, using B/S architecture to communicate with the test tool server, realize tool selection, parameter configuration, script generation, file transfer and result analysis, and simplify tool access through graphical interfaces or standardized interfaces. , supports multilingual and multi-tool rule set management, real-time status monitoring and notification, provides source-level accurate positioning and interaction, intelligent result management and efficient collaboration.

Benefits of technology

It realizes automated execution of project inspection tasks, reduces manual intervention, improves project development and testing efficiency, simplifies the access and use of test tools, ensures consistent execution of coding specifications and problem positioning efficiency, and provides centralized result management and collaborative support.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916264A_ABST
    Figure CN118916264A_ABST
Patent Text Reader

Abstract

The invention provides a test method based on an FPGA software integrated test management platform and the management platform. The method comprises the steps that a target test tool selected by a user through an operation page provided by the FPGA software integrated test management platform and an uploaded tested item are acquired; obtaining target parameters matched with the target test tool and the tested item and configured by the user through the operation page; generating a test script by using an operation command of the target test tool according to the target parameter; sending the tested item and the test script to a test tool server, so that the test tool server starts a target test tool to execute the test script to test the tested item, generate a test result file and return the test result file to the FPGA software integrated test management platform; receiving a test result file sent by the test tool server; and analyzing the test result file to obtain an analysis result, and displaying the analysis result through the interactive page. According to the scheme, the project inspection task is automatically executed, and the project development and test efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of automated testing technology, and in particular to a testing method and management platform based on an FPGA software integrated testing management platform. Background Art

[0002] In the current FPGA (Field Programmable Gate Array) software development process, coding standards and quality control are important links to ensure the smooth progress of the project and product quality.

[0003] The current coding rule checking method usually relies on developers to manually execute special tools (such as Alint-Pro, BluePearl) to check the code file by file or in batches. This requires developers to separately install, configure and update coding rule checking tools such as Alint-Pro in the local environment. This involves tedious steps such as downloading installation packages, setting environment variables, obtaining and configuring tool licenses, and familiarizing themselves with tool interfaces and usage processes, which takes up a lot of non-value time and results in low testing efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide a testing method and management platform based on an FPGA software integrated testing management platform that can realize project automated testing in response to the above technical problems.

[0005] In a first aspect, an embodiment of the present disclosure provides a testing method based on an FPGA software integrated test management platform, wherein the FPGA software integrated test management platform adopts a B / S architecture and is communicatively connected to a test tool server, wherein different FPGA software test tools are pre-installed on the test tool server, and the method comprises:

[0006] Obtaining the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform;

[0007] Acquire target parameters configured by the user through the operation page that match the target test tool and the tested item;

[0008] Generate a test script using the operation command of the target test tool according to the target parameters;

[0009] Sending the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform;

[0010] Receiving the test result file sent by the test tool server;

[0011] The test result file is parsed to obtain a parsing result, and the parsing result is displayed through an interactive page.

[0012] In a second aspect, an embodiment of the present disclosure provides an FPGA software integrated test management platform, which adopts a B / S architecture and is communicated with a test tool server, on which different FPGA software test tools are pre-installed. The FPGA software integrated test management platform includes:

[0013] A first acquisition module is used to acquire the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform;

[0014] A second acquisition module is used to acquire target parameters configured by the user through the operation page and matching the target test tool and the tested item;

[0015] A script generation module, used to generate a test script according to the target parameters using the operation commands of the target test tool;

[0016] A sending module, used to send the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform;

[0017] A receiving module, used for receiving the test result file sent by the test tool server;

[0018] A parsing module, used for parsing the test result file to obtain a parsing result;

[0019] The display module is used to display the analysis results through an interactive page.

[0020] In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

[0021] Processor; and

[0022] Memory for storing programs,

[0023] Wherein, the program includes instructions, and when the instructions are executed by the processor, the processor executes the steps of the test method based on the FPGA software integrated test management platform according to the first aspect.

[0024] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the test method based on the FPGA software integrated test management platform according to the first aspect are implemented.

[0025] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, wherein when the computer program is executed by a processor, the steps of the testing method based on the FPGA software integrated testing management platform according to the first aspect are implemented.

[0026] The test method and management platform based on the FPGA software integrated test management platform provided by the embodiment of the present disclosure obtains the target test tool and the uploaded tested project selected by the user through the operation page provided by the FPGA software integrated test management platform, and obtains the target parameters configured by the user through the operation page that match the target test tool and the tested project, and generates a test script according to the target parameters using the operation command of the target test tool, and then sends the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform, the platform receives the test result file sent by the test tool server, parses the test result file to obtain the parsing result, and displays the parsing result through the interactive page. The scheme of the present disclosure is adopted, through tool selection, parameter configuration, script generation, file transfer, result parsing and other links, to achieve the close coupling of the test tool and the test management platform, the user only needs to select the test tool and configure the parameters through the FPGA software integrated test management platform to complete the automated test of the project, simplifying the access and use process of the test tool, eliminating the tool use obstacles, realizing the automated execution of project inspection tasks, reducing manual intervention, and improving the project development and testing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A flowchart of a testing method based on an FPGA-software integrated testing management platform according to an exemplary embodiment of the present disclosure;

[0028] Figure 2 A schematic diagram of some commands of Alint-Pro according to an exemplary embodiment of the present disclosure;

[0029] Figure 3 is a schematic diagram of an analysis result of an exemplary embodiment of the present disclosure;

[0030] Figure 4 A process diagram of a testing method based on an FPGA software integrated testing management platform provided in a specific embodiment of the present disclosure;

[0031] Figure 5 The figure is a schematic diagram of the structure of an FPGA software integrated test management platform according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0033] In the current FPGA software development process, coding standards and quality control are important links to ensure the smooth progress of the project and product quality. Traditional coding rule checking usually relies on developers to manually execute special tools (such as Alint-Pro, BluePearl) to check the code file by file or in batches. This method has problems such as low efficiency, inconsistent specification execution, and difficulty in centralized management and tracking of results. With the improvement of the automation level of software engineering, the test management platform has gradually become the core carrier for integrating various test tools and optimizing the development process.

[0034] In the current FPGA software development field, traditional methods or preliminary automation methods used for coding rule checking usually include the following core components:

[0035] 1. Separate deployment and use of static checking tools: Developers need to separately install, configure, and update coding rule checking tools, such as Alint-Pro, in the local environment. When using, developers need to manually start the tool, specify the source files or directories to be checked, and select the corresponding rule set. This model requires developers to have certain tool usage knowledge and invest extra time in configuration and maintenance.

[0036] 2. Tool rule set management: In traditional solutions, coding rule sets are usually provided by the tool itself or compiled by the team according to project requirements. The selection and customization of rule sets are relatively limited, and the process of updating rule sets may involve complex configuration file modifications or rule file compilation. Sharing and version management of rule sets also often require the use of external tools or manual processes.

[0037] 3. Manual execution and result review: The static inspection process is completely dependent on manual triggering by the developer, and the inspection results are usually output to the terminal or a specified file in the form of a text report. The developer needs to read the report line by line, understand the cause of the violation, and manually open the source code to locate the problem based on the source file path and line number information provided in the report. This process is not only time-consuming, but also prone to omission or misunderstanding of inspection results.

[0038] 4. Result tracking and problem rectification: In large projects, static inspection may generate a large number of results. Traditional solutions lack effective result management mechanisms, such as problem classification, priority division, status tracking, etc. Developers need to manually record or use auxiliary tools to track problem rectification, which is a cumbersome process and difficult to form a team-shared view.

[0039] However, the traditional methods or preliminary automated means used for coding standard checking have the following significant defects:

[0040] 1. High reliance on manual operations, increasing non-value workload

[0041] (1) Complex deployment and configuration: Developers need to manually install, configure, and update coding rule checking tools, such as Alint-Pro, in the local environment. This involves tedious steps such as downloading installation packages, setting environment variables, and configuring rule files, which takes up a lot of non-value time.

[0042] (2) Frequent triggering of inspection tasks: After each code modification, developers need to manually start the tool to perform inspection tasks. Especially in an agile development environment, frequent code submissions mean frequent manual inspection operations, which increases the daily burden.

[0043] (3) Time-consuming result interpretation and location: The inspection results are presented in the form of text reports. Developers need to read and understand the reasons for the violations one by one, and manually open the source code to locate the problem based on the source file path and line number information provided in the report. This process is not only time-consuming, but also prone to omission or misunderstanding of inspection results, reducing the speed and accuracy of problem rectification.

[0044] 2. Inconvenient rule set management, limiting the adaptability of the specification

[0045] (1) Limited selection of rule sets: The built-in rule sets of the tool do not support customization and may not fully cover the coding standards required by the project. Custom rule sets require writing or modifying rule files, which places high technical requirements on developers.

[0046] (2) Difficulty in updating rules: As coding standards evolve or project requirements change, rule sets need to be updated in a timely manner. However, in existing solutions, the rule set update process often involves complex configuration file modifications or rule file compilation, which is difficult to operate and prone to errors.

[0047] (3) Lack of rule set sharing and version management: When team members share rule sets or trace back historical versions of rule sets, there is a lack of convenient tool support. Usually, file sharing, email communication, etc. are required, which is inefficient and prone to version confusion.

[0048] 3. The efficiency of result feedback and positioning is low, which affects the speed of problem rectification

[0049] (1) The result display is poorly structured: The inspection results are presented in the form of text reports, lacking structured display functions such as classification, sorting, and filtering, making it difficult for developers to quickly focus on key issues when browsing a large number of results.

[0050] (2) Missing or inconvenient source code links: The source file path and line number information in the report needs to be manually copied and pasted into the IDE or file browser to open. There is no function to directly jump to the source code by clicking, which increases the operation steps for problem locating.

[0051] (3) Insufficient explanation of the causes of violations: Some inspection results simply list the facts of the violations, lacking in-depth explanations of the causes of the violations or examples, making it difficult for developers to understand the nature of the violations and how to correct them.

[0052] 4. Difficulty in result tracking and rectification, affecting quality management

[0053] (1) Lack of problem tracking mechanism: The existing solution lacks a unified management and tracking mechanism for inspection results. Developers need to manually record the problem list or use external tools to track it. The process is cumbersome and prone to omissions.

[0054] (2) Inconvenient priority division and status management: It is not possible to easily assign priorities to inspection results or track their rectification status (such as pending rectification, rectified, verified, etc.), which makes it difficult to grasp the priority and progress of problem rectification.

[0055] (3) Insufficient support for team collaboration: There is a lack of support for multiple people to collaborate on the same problem, such as problem assignment, discussion, and merging and rectifying problems, which affects the coordination and efficiency of coding standard rectification within the team.

[0056] 5. Lack of integration with the test management platform reduces development and testing efficiency

[0057] (1) Limited resource scheduling and task management: Static code checking tasks cannot be included in the unified scheduling and management of the test management platform, and cannot utilize the platform's parallel execution, scheduled tasks, dependency management and other functions, reducing overall development and testing efficiency.

[0058] (2) Inconvenient association between result feedback and source code: Inspection results cannot be directly displayed in the test management platform and associated with the source code. Developers need to switch between multiple systems to view them, which affects the consistency of problem location and rectification.

[0059] (3) Data silos and duplication of work: Static inspection results are isolated from other project test data (such as unit testing, integration testing, etc.), making it difficult to conduct comprehensive analysis and trend monitoring, which may lead to duplication of work or omission of important issues.

[0060] In summary, the defects of existing solutions are mainly reflected in the strong dependence on manual operations, inconvenient rule set management, low efficiency of result feedback and positioning, difficulty in result tracking and rectification, lack of integration with test management platforms, and insufficient degree of automation. Therefore, innovative solutions are urgently needed to overcome these limitations.

[0061] In view of the shortcomings of the above existing solutions, this paper proposes a static test tool integration method based on an FPGA software integrated test management platform, which realizes the automated testing of the project by integrating coding rule checking tools (i.e., test tools). This solution achieves the following core goals:

[0062] 1. Tool access and automated operation and maintenance

[0063] (1) One-click tool access: Provides a graphical interface or standardized interface, allowing developers to quickly add, configure, and enable static inspection tools such as Alint-Pro without having to understand the underlying details, significantly lowering the access threshold.

[0064] (2) Cross-platform compatibility: The FPGA software integrated test management platform (referred to as the "test management platform" or "platform") adopts a B / S architecture and supports seamless integration of static checking tools in multiple operating systems (such as Windows, Linux, etc.) and development environments, ensuring that different team members can use them smoothly in their respective working environments.

[0065] 2. Highly customizable rule configuration system

[0066] (1) Rule set classification and management: The FPGA software integrated test management platform supports multi-language and multi-tool rule set management, and provides professional rule set classification for various aerospace institutes and research institutes. It also supports the import and export of rule set data and supports users to preview the rule set content online. The platform also facilitates users to quickly select rule sets that meet project characteristics and team specifications.

[0067] 3. Seamless process-level integration and real-time feedback

[0068] (1) Test plan and task scheduling: Static inspection tasks are seamlessly integrated into the test plan of the FPGA software integrated test management platform, which supports flexible setting of the triggering time and priority of inspection tasks according to project phases, modules, code changes, and other conditions, and realizes automatic scheduling and execution of tasks. Users can set the priority of different projects through the test management platform, and the test management platform automatically schedules and executes tasks according to the priority of the project. In addition, if there is an ongoing task, when a new task of a higher level is submitted, it is necessary to wait for the ongoing task to end before scheduling the new task according to the priority. For different tasks with the same priority, the tasks are scheduled according to the order of submission time.

[0069] (2) Real-time status monitoring and notification: Provides a real-time task execution status monitoring interface to display key information such as inspection progress, number of results, and violation distribution. Specifically, the test management platform can refresh the page in real time and display the acquired tool execution status (such as executing, completed, etc.) to the user. When the user sees that the execution status is completed, the user can view the test result file returned by the test tool server; if the test tool fails to execute the task, an error execution log is generated and fed back to the platform for display to inform the user of the exception type, occurrence time, and other information.

[0070] (3) Source code-level precise positioning and interaction: The inspection results are directly displayed on the FPGA software integrated test management platform, including the illegal code snippets, the reasons for the violations, and the recommended repair solutions. A source code link is also provided, and users can click to jump to the specific location of the corresponding source file, greatly improving the efficiency of problem positioning.

[0071] 4. Intelligent result management and efficient collaboration

[0072] (1) Multi-dimensional result filtering and sorting: Provides a variety of filtering conditions and sorting options, such as violation type and severity, to help developers quickly focus on key issues and optimize the order of problem handling.

[0073] (2) One-click generation of customized reports: Supports on-demand generation of various customized reports to meet the problem reporting requirements generated in different scenarios.

[0074] The following is a detailed explanation of the test method and management platform based on the FPGA software integrated test management platform disclosed in the present invention in conjunction with the accompanying drawings.

[0075] Figure 1 The present invention is a flowchart of a test method based on an FPGA software integrated test management platform according to an exemplary embodiment of the present invention. The method can be applied to the FPGA software integrated test management platform provided in the embodiment of the present invention. The FPGA software integrated test management platform can be implemented by software and / or hardware, and can be integrated in an electronic device, which can be a computer or other device. The FPGA software integrated test management platform of the present invention adopts a B / S architecture and is connected to a test tool server for communication. The test tool server is pre-installed with different FPGA software test tools (referred to as test tools), such as Alint-Pro, BluePearl and other coding rule checking tools. The FPGA software integrated test management platform and the test tool server are deployed in two different electronic devices.

[0076] like Figure 1 As shown, the test method based on the FPGA software integrated test management platform includes the following steps:

[0077] Step 101 , obtaining the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform.

[0078] In the disclosed embodiment, the FPGA software integrated test management platform can provide an operation page, and a graphical interface or standardized interface for selecting the required FPGA software testing tool is provided in the operation interface, allowing users (developers) to quickly add, configure and enable static inspection tools such as Alint-Pro without understanding the underlying details. After the user selects the FPGA software testing tool through the operation page, the platform can obtain the FPGA software testing tool selected by the user (called the target testing tool). In addition, the operation page also provides a task upload interface for uploading the project to be tested. The user can upload the project to be tested through the task upload interface, and then the platform can obtain the project to be tested uploaded by the user. It can be understood that a project, that is, a file contained in an FPGA software, includes a handwritten file and / or an IP file. The IP file is an IP core, which can be understood as a pre-designed circuit function module for ASIC or FPGA.

[0079] Step 102: Obtain target parameters configured by the user through the operation page that match the target test tool and the item under test.

[0080] In the disclosed embodiment, the operation page also supports user-friendly parameter configuration. Users can independently configure the execution parameters related to the target test tool for the project under test through the operation page on the platform to ensure that the parameters are closely matched with the specific requirements of the project under test and realize project-level personalized parameter settings. The parameters include but are not limited to:

[0081] ① Top-level file specification: Specify the top-level design file or module list in the project as the starting point for analysis to ensure that the tool can correctly identify the project architecture;

[0082] ② Rule set customization: Supports selection or uploading of custom rule sets, covering language specifications, design styles, best practices and other aspects, ensuring that the inspection standards are consistent with project characteristics and team specifications;

[0083] ③ Black box file management: allows users to specify black box files (such as third-party libraries and verified modules), so that the tool ignores the internal structure of these files and focuses on checking the core code of the project;

[0084] ④ File processing strategy setting: set file inclusion and exclusion rules to control the inspection scope; define default processing methods such as file encoding and dependency parsing to ensure that the tool correctly parses the source code;

[0085] ⑤IP library configuration: Connect internal or external IP libraries to provide Alint-Pro with necessary metadata to support correct analysis and compliance checking of IP cores.

[0086] In the disclosed embodiment, after the user configures the parameters through the operation page, the platform can obtain the parameters configured by the user that match the target test tool and the item under test (referred to as target parameters).

[0087] In an optional embodiment of the present disclosure, the platform may display parameter options associated with the target testing tool through an operation page, and the user may select matching parameter options and perform parameter configuration according to the requirements of the project under test. In response to receiving a parameter configuration operation performed by the user on at least one parameter option through the operation page, the platform obtains the parameters configured by at least one parameter option as the target parameter.

[0088] In an optional embodiment of the present disclosure, the platform can provide preset parameter templates for common application scenarios and support dynamic adjustment of templates. Users can apply parameter templates with one click or make adaptive adjustments based on existing parameter templates to obtain parameter files. In addition, the parameter files adjusted by the user support real-time storage and version management, allowing users to trace back or compare the effects of different configuration versions at any time. Thus, in this embodiment, the platform can display parameter templates associated with the target test tool through the operation page for users to choose, and users can select the required parameter template (called the target parameter template) from it according to the needs of the project under test. After the user selects, the platform can determine the target parameter template selected by the user through the operation page, and determine the target parameter file based on the user's editing operation on the target parameter template, wherein, if the target parameter template can meet the user's needs, the user can perform an editing operation of one-click application on the target parameter template, and the platform determines the target parameter template as the target parameter file; if some parameters in the target parameter template cannot meet the user's needs, the user can perform an editing operation of parameter modification on the target parameter template, and after the user modifies the parameters, the platform determines the target parameter template after the modified parameters as the target parameter file. Afterwards, the platform determines the parameters configured in the target parameter file as the target parameters.

[0089] In an optional implementation of the present disclosure, the two methods of configuring target parameters through parameter options displayed on the operation page and determining target parameters based on a target parameter template selected by the user can be used in combination to ensure the integrity of the parameter configuration and ensure that the configured parameters can meet project requirements.

[0090] Step 103: Generate a test script according to the target parameters using the operation commands of the target testing tool.

[0091] In the disclosed embodiment, after obtaining the target parameters configured by the user, the platform can generate a test script using the operation commands of the target test tool.

[0092] For example, if the target test tool selected by the user is Alint-Pro, the platform follows the official interface specifications of Alint-Pro according to the target parameters set by the user, and uses Alint-Pro commands to add inspection files (i.e. files of the project under test, which can be added multiple times) to the previously created workspace (file storage path pre-set by code); use Alint-Pro commands to add rule sets (which can be added multiple times); use Alint-Pro commands to add black box units, set top-level files, parse, link, run, generate reports, complete and exit, etc. Some of the commands of Alint-Pro are as follows: Figure 2 shown.

[0093] Step 104, sending the project under test and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the project under test, and generates a test result file and returns it to the FPGA software integrated test management platform.

[0094] In the disclosed embodiment, after obtaining the test script, the platform can send the project under test and the test script to the test tool server. After the test tool server receives the file sent by the platform, it starts the target test tool to execute the test script to test the project under test, and generates a test result file after the test is completed, and returns the test result file to the FPGA software integrated test management platform.

[0095] For example, the FPGA software integrated test management platform can use a safe and efficient file transfer protocol to synchronize the handwritten files to be checked, black box files, and possibly required dependent files (such as constraint files, simulation models, etc.) to the test tool server, and the test tool server starts the target test tool to test the files. During the file transfer process, the platform supports breakpoint resumption (for example, if the network is interrupted during the transmission process, the transmission will continue from the interrupted position after the network is restored, without the need to retransmit the entire file), compressed transmission (compress the file before transmission to save transmission resources), permission verification (for example, only users with operating permissions can operate the platform to perform project testing) and other functions to ensure data integrity and security.

[0096] Step 105: Receive the test result file sent by the test tool server.

[0097] Step 106, parse the test result file to obtain a parsing result, and display the parsing result through an interactive page.

[0098] Exemplarily, after the platform sends the file to the test tool server, it can wait to receive the test result file returned by the test tool server, and after receiving the test result file, parse the test result file to obtain the parsing result, and display the parsing result through an interactive page.

[0099] Exemplarily, after the platform sends the file to the test tool server, it can monitor the test status of the test tool server in real time, and display the test status through the task execution status monitoring interface to show the test progress to the user. When the test is completed, it receives the test result file returned by the test tool server, parses the test result file, and displays the parsed results through an interactive page.

[0100] The test method based on the FPGA software integrated test management platform disclosed in the present invention obtains the target test tool and the uploaded tested project selected by the user through the operation page provided by the FPGA software integrated test management platform, and obtains the target parameters matching the target test tool and the tested project configured by the user through the operation page, generates a test script according to the target parameters using the operation command of the target test tool, and then sends the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform, the platform receives the test result file sent by the test tool server, parses the test result file to obtain the parsing result, and displays the parsing result through the interactive page. The scheme disclosed in the present invention is adopted, through tool selection, parameter configuration, script generation, file transfer, result parsing and other links, to achieve the close coupling of the test tool and the test management platform, the user only needs to select the test tool and configure the parameters through the FPGA software integrated test management platform to complete the automated test of the project, simplifies the access and use process of the test tool, eliminates the tool use obstacles, realizes the automated execution of project inspection tasks, reduces manual intervention, and improves the project development and testing efficiency.

[0101] In the disclosed embodiment, after the test tool server executes the target test tool to test the tested item, it feeds back the test result file to the platform. The platform receives and parses the test result file. The parsing process not only extracts basic information such as rule number, introduction, and detailed description, but also refines the specific attributes of the violation item. That is, the parsing result obtained by parsing the test result file includes at least one violation item, and each violation item includes the following attributes:

[0102] Rule name, used to identify the rule violated by the offending entry;

[0103] Violating content, which indicates code snippets or design elements that violate the rules;

[0104] Source file path and row and column position: used to indicate the location of the source file where the illegal content is located. The location indication is accurate and easy to locate quickly;

[0105] Design unit: used to indicate the context information involved in the rule content, including the logical level involved, instance name and other context information;

[0106] Violation type: used to indicate the type of rule violated by the violation entry, such as syntax error, logic error, design risk, etc.

[0107] Severity level and rule level: used to quantify the impact of violations and the importance of rules.

[0108] For example, the parsing result obtained by parsing is as follows Figure 3 As shown, it can be seen that different violation entries can contain different attributes, such as Figure 3 The first violation entry in the example includes the rule level, while the second violation entry does not include the rule level. That is, the attributes included in a violation entry may be part or all of the above attributes.

[0109] In the disclosed embodiment, the platform provides an interactive result view (interactive page) that can display the analysis results in a structured and interactive manner. The interactive page supports the following functions:

[0110] ① Paged browsing: display results in pages according to user needs to avoid information overload;

[0111] ② Source code link: Click on the illegal entry to jump directly to the corresponding position of the source code editor, realizing seamless connection between source code and results;

[0112] ③ Quick filtering and searching: Provides multiple filtering conditions and keyword search functions to help users quickly focus on problems of a specific type or severity.

[0113] Based on the above interactive page, in an optional implementation of the present disclosure, on the basis of the above embodiment, displaying the parsing result through the interactive page may include the following sub-steps: extracting the violation items from the parsing result, and obtaining the number of violation items contained in the parsing result; obtaining the display threshold of the interactive page, wherein the display threshold refers to the maximum number of violation items that the interactive page can display, and the display threshold can be a default value, or it can be pre-set by the user when submitting the task; in response to the number of violation items being greater than the display threshold, the violation items are displayed in pages in the interactive page, wherein the number of violation items displayed per page is not greater than the display threshold; in response to the number of violation items being less than the display threshold, all violation items are displayed in one page in the interactive page. In addition, after displaying the violation items through the interactive page, the bottom of the interactive page can also display the display threshold that can be selected by the user, and after the user selects another display threshold, the number of violation items is compared with the size of the newly selected display threshold, and when the number of violation items is greater than the new display threshold, the violation items are displayed in pages. Displaying the violation items by pages is conducive to avoiding information overload.

[0114] Furthermore, in an optional implementation of the present disclosure, each violation item displayed in the interactive page corresponds to a source code link, so that on the basis of the aforementioned embodiment, the method of the present disclosure may further include the following steps: in response to receiving a click operation of a user on a target source code link, obtaining a target violation item corresponding to the target source code link, wherein the target source code link is a source code link clicked by the user among the source code links corresponding to the violation items displayed on the interactive page; then, the violation content of the target violation item may be obtained, wherein the violation content may be extracted according to the attributes contained in the target violation item; and then, the violation content of the target violation item may be displayed in the form of a pop-up window.

[0115] Exemplarily, the source code link can be a "view source code" control. After the user clicks it, the illegal content of the corresponding illegal entry is displayed in the form of a pop-up window. In order to reduce the obstruction of the interactive page, the pop-up window can be displayed in the blank area on the right side of the interactive page.

[0116] In this embodiment, by setting corresponding source code links for illegal entries and displaying them in the interactive page, it is possible to directly jump to the illegal source code by clicking the source code link, thereby achieving seamless connection between the source code and the results.

[0117] Based on the above interactive page, in an optional implementation of the present disclosure, on the basis of the above embodiment, after displaying the violation items through the interactive page, the method of the present disclosure may further include the following steps: obtaining the filtering conditions set by the user through the interactive page, wherein the filtering conditions may be selected search keywords or set extraction conditions; filtering at least one violation item based on the filtering conditions to determine the violation items that meet the filtering conditions; and displaying the violation items that meet the filtering conditions through the interactive page. Thus, by providing extraction conditions and keyword search functions, it is possible to quickly filter and search for the required violation items, helping users to quickly focus on problems of a specific type or severity.

[0118] In an optional implementation of the present disclosure, each violation item displayed in the interactive page corresponds to a check box, so that on the basis of the aforementioned embodiment, the method of the present disclosure may further include the following steps: in response to receiving a user's selection operation on a target check box, obtaining the violation item corresponding to the target check box, wherein the target check box is the check box selected by the user in the check box corresponding to the violation item displayed on the interactive page, and the user may select one or more check boxes; obtaining a preset report template; generating a problem report based on the report template and the violation item corresponding to the target check box. In this embodiment, the generated problem report supports export, which is convenient for sharing, archiving or reporting to superiors within the team. Therefore, by setting a corresponding check box for each violation item and displaying it on the interactive page, the user can select a specific violation item from the displayed violation items to generate a problem report according to the needs, thereby realizing the generation of a custom report; and by providing a report template, generating a problem report based on the report template, realizing the standardization of the problem report format, so that the generated report follows the unified format and template of the platform, ensuring that the information is clear, standardized, and easy to read and understand.

[0119] In an optional implementation of the present disclosure, the platform also supports a false report management function. Specifically, for the remaining violation items that have not been selected by the user to be included in the problem report form, the platform can mark them as "false reports", indicating that these violation items may be false reports or issues that do not need to be paid attention to for the time being. The false report information is still retained in the platform, but it will not affect the presentation of the report form. The user can adjust the false report status at any time according to the subsequent analysis.

[0120] In an optional implementation of the present disclosure, based on the aforementioned embodiments, the method of the present disclosure may further include the following steps: obtaining an error log file sent by a test tool server, wherein the error log file is generated by a target test tool when an exception occurs in the test process of the project under test, and is sent to the FPGA software integrated test management platform through the test tool server; displaying the content in the error log file through a task execution status monitoring interface, and the error log file may record execution script data, error data, exception type, occurrence time, possible impact, etc.

[0121] That is to say, the FPGA software integrated test management platform disclosed in the present invention also supports abnormal diagnosis and log management functions, including:

[0122] (1) Real-time anomaly monitoring and prompting: When an anomaly occurs during the execution of a task by the test tool, the platform can monitor in real time and inform the anomaly type, occurrence time, and possible impact;

[0123] (2) Detailed log viewing: Provides detailed error log viewing function, including execution script data and error data, which helps users to deeply analyze the root cause of the problem;

[0124] (3) Log archiving and retrieval: All execution logs are properly saved and bound to the project. The execution log files are also stored in the project-related directory on the server to facilitate historical problem tracing and experience accumulation.

[0125] In an optional implementation of the present disclosure, the platform also supports task scheduling and concurrent execution. Specifically, the platform can automatically schedule multiple inspection tasks based on factors such as project scale and server resources, and start a corresponding number of processes to execute these inspection tasks in parallel, thereby making full use of computing resources, shortening the overall project inspection time, and improving testing efficiency.

[0126] In summary, the solution proposed in this paper builds a complete and efficient FPGA software static test management process through detailed parameter configuration, intelligent script generation, in-depth result analysis, flexible report generation and powerful exception diagnosis capabilities, which greatly improves the efficiency and experience of the development team in coding standard checking, problem location, collaborative rectification and decision support.

[0127] Figure 4 A process diagram of a testing method based on an FPGA software integrated testing management platform provided in a specific embodiment of the present disclosure is shown in FIG. Figure 4As shown, when a project test is needed, the user can select a tool (i.e., select a target test tool) through the FPGA software integrated test management platform, and perform parameter configuration. After that, the platform performs the steps generated according to the execution script according to the configured target parameters to generate a test script, and then executes the script (i.e., the generated test script) and the step of checking the text (i.e., the project under test) transmission, sends the test script and the project under test to the test tool server for tool execution, and the target test tool in the test tool server tests the project under test based on the test script, and generates the inspection result (i.e., the test result file), and sends the test result file to the platform through the test tool server. After that, the platform executes the step of result parsing, and after parsing, the execution result is displayed and the step of linking the source file is performed to associate the parsed illegal items with the relevant source code. After the display result, the platform can also perform the step of selecting and generating a problem report, so as to generate a problem report sheet according to the illegal items selected by the user, and realize personalized report generation. In addition, the platform also supports the real-time feedback function of execution progress to monitor the execution status of the task.

[0128] In summary, the present disclosure provides a static test tool integration solution based on an FPGA software integrated test management platform. The core innovation of this solution is:

[0129] (1) Deep tool integration: Through parameter configuration, script generation, file transfer, result analysis and other links, the test tool and the test platform are tightly coupled to eliminate obstacles to tool use. At the same time, it ensures smooth data interaction between the test tool and the test platform, including defect information, version control data, etc., and realizes instant synchronization of status updates;

[0130] (2) Flexible rule customization: Supports users to customize rule sets according to actual needs and upload them to the platform for FPGA software testing, ensuring that coding specifications are consistent with project characteristics and team standards;

[0131] (3) Integrated workflow: Integrate the static inspection process into the platform workflow to achieve seamless connection between task scheduling, status monitoring, result feedback and source code association;

[0132] (4) Intelligent result management: It provides centralized result display, source code linking, problem report generation and other functions, and provides custom filtering conditions. Users can quickly focus on related issues based on their concerns (such as severity, responsible person, problem type, etc.), greatly improving the efficiency of result understanding and processing.

[0133] This solution effectively solves the problems of poor integration, poor flexibility, weak interactivity, and low manageability in traditional methods by deeply integrating coding rule checking tools. The specific performance is as follows:

[0134] 1. Improve efficiency: Simplify the access and use of test tools, realize automatic execution of inspection tasks, reduce manual intervention, and improve development and testing efficiency;

[0135] 2. Standardization: Supports personalized rule configuration, which helps ensure consistent implementation of coding standards across teams, thereby improving code quality;

[0136] 3. Friendly interaction: It can intuitively display the association between inspection results and source code, which is convenient for quickly locating problems, thereby improving the speed of problem understanding and repair;

[0137] 4. Easy to manage: It provides centralized and convenient result management views and report generation functions, strengthens quality management and problem tracking capabilities, and thus helps promote team collaboration and decision-making.

[0138] In order to implement the above embodiments, the present disclosure also provides an FPGA software integrated test management platform.

[0139] Figure 5 The present invention is a schematic diagram of the structure of an FPGA software integrated test management platform of an exemplary embodiment of the present invention, which can be implemented by software and / or hardware and can be integrated in an electronic device. The FPGA software integrated test management platform adopts a B / S architecture and is connected to a test tool server in communication, and different FPGA software test tools are pre-installed on the test tool server.

[0140] like Figure 5 As shown, the FPGA software integrated test management platform 40 includes: a first acquisition module 401, a second acquisition module 402, a script generation module 403, a sending module 404, a receiving module 405, a parsing module 406 and a display module 407, wherein:

[0141] The first acquisition module 401 is used to acquire the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform;

[0142] The second acquisition module 402 is used to acquire the target parameters configured by the user through the operation page and matching the target test tool and the tested item;

[0143] A script generation module 403, configured to generate a test script according to the target parameters and using the operation commands of the target test tool;

[0144] The sending module 404 is used to send the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform;

[0145] The receiving module 405 is used to receive the test result file sent by the test tool server;

[0146] The parsing module 406 is used to parse the test result file to obtain a parsing result;

[0147] The display module 407 is used to display the analysis result through an interactive page.

[0148] In one embodiment, the second acquisition module 402 is further configured to:

[0149] Displaying parameter options associated with the target testing tool through the operation page;

[0150] In response to receiving a parameter configuration operation performed by the user on at least one parameter option through the operation page, acquiring a parameter configured by the at least one parameter option as a target parameter;

[0151] and / or

[0152] Displaying a parameter template associated with the target test tool through the operation page;

[0153] Determine the target parameter template selected by the user through the operation page;

[0154] Determining a target parameter file based on the user's editing operation on the target parameter template;

[0155] The parameters configured in the target parameter file are determined as target parameters.

[0156] In one embodiment, the parsing result includes at least one violation entry, and each violation entry includes the following attributes:

[0157] Rule name, used to identify the rule violated by the offending entry;

[0158] Violating content, which indicates code snippets or design elements that violate the rules;

[0159] Source file path and row and column position: used to indicate the location of the source file where the illegal content is located;

[0160] Design unit: used to indicate the context information involved in the rule content;

[0161] Violation Type: used to indicate the type of rule violated by the violation entry;

[0162] Severity level and rule level: used to quantify the impact of violations and the importance of rules.

[0163] In one embodiment, the display module 407 is further used to:

[0164] Extracting illegal entries from the parsing result, and obtaining the number of illegal entries contained in the parsing result;

[0165] Obtaining a display threshold of the interactive page;

[0166] In response to the number of the illegal entries being greater than the display threshold, the illegal entries are displayed in pages in the interactive page, wherein the number of illegal entries displayed on each page is not greater than the display threshold.

[0167] In one embodiment, each violation item displayed in the interactive page corresponds to a source code link; the FPGA software integrated test management platform 40 also includes:

[0168] A third acquisition module, configured to acquire a target violation entry corresponding to the target source code link in response to receiving a click operation of the user on the target source code link;

[0169] A fourth acquisition module, used to acquire the illegal content of the target illegal entry;

[0170] The pop-up window display module is used to display the illegal content of the target illegal entry in the form of a pop-up window.

[0171] In one embodiment, the FPGA software integrated test management platform 40 further includes:

[0172] A fifth acquisition module, used to acquire the screening conditions set by the user through the interactive page;

[0173] A screening module, configured to screen the at least one illegal entry based on the screening condition to determine an illegal entry that satisfies the screening condition;

[0174] The display module 407 is also used to display the illegal items that meet the screening conditions through the interactive page.

[0175] In one embodiment, each violation item displayed in the interactive page corresponds to a check box; the FPGA software integrated test management platform 40 also includes:

[0176] A sixth acquisition module, configured to, in response to receiving a selection operation of a target check box by the user, acquire a violation entry corresponding to the target check box;

[0177] A seventh acquisition module is used to acquire a preset report template;

[0178] The report generation module is used to generate a problem report based on the report template and the violation items corresponding to the target check box.

[0179] In one embodiment, the FPGA software integrated test management platform 40 further includes:

[0180] An eighth acquisition module is used to acquire an error log file sent by the test tool server, wherein the error log file is generated by the target test tool when an exception occurs in the test process of the item under test, and is sent to the FPGA software integrated test management platform through the test tool server;

[0181] The log display module is used to display the content in the error log file through the task execution status monitoring interface.

[0182] The FPGA software integrated test management platform provided in the embodiment of the present disclosure can execute any test method based on the FPGA software integrated test management platform provided in the embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method. Contents not fully described in the embodiment of the device of the present disclosure can refer to the description in any method embodiment of the present disclosure.

[0183] An embodiment of the present disclosure also provides an electronic device, comprising: a processor; and a memory for storing a program, wherein the program includes instructions, and when the instructions are executed by the processor, the processor executes the steps of the test method based on the FPGA software integrated test management platform according to any of the aforementioned embodiments. To avoid repeated description, they are not repeated here.

[0184] The embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the test method based on the FPGA software integrated test management platform as described in any of the aforementioned embodiments are implemented. To avoid repeated description, they are not repeated here.

[0185] The embodiments of the present disclosure also provide a computer program product, including a computer program, wherein when the computer program is executed by a processor, the steps of the testing method based on the FPGA software integrated testing management platform as described in any of the aforementioned embodiments are implemented. To avoid repeated description, they are not repeated here.

[0186] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided by the present disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in various forms, such as static random access memory (SRAM) and dynamic random access memory (DRAM).

[0187] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0188] The above-mentioned embodiments only express several implementation methods of the present disclosure, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for ordinary technicians in this field, several variations and improvements can be made without departing from the concept of the present disclosure, and these all belong to the protection scope of the present disclosure. Therefore, the protection scope of the patent of the present disclosure shall be subject to the attached claims.

Claims

1. A testing method based on an FPGA software integrated test management platform, characterized in that: The FPGA software integrated test management platform adopts a B / S architecture and is connected to a test tool server in communication. The test tool server is pre-installed with different FPGA software test tools. The method includes: Obtaining the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform; Acquire target parameters configured by the user through the operation page that match the target test tool and the tested item; Generate a test script using the operation command of the target test tool according to the target parameters; Sending the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform; Receiving the test result file sent by the test tool server; The test result file is parsed to obtain a parsing result, and the parsing result is displayed through an interactive page.

2. The method according to claim 1, characterized in that The obtaining of target parameters configured by the user through the operation page and matching the target test tool and the tested item includes: Displaying parameter options associated with the target testing tool through the operation page; In response to receiving a parameter configuration operation performed by the user on at least one parameter option through the operation page, acquiring a parameter configured by the at least one parameter option as a target parameter; and / or Displaying a parameter template associated with the target test tool through the operation page; Determine the target parameter template selected by the user through the operation page; Determining a target parameter file based on the user's editing operation on the target parameter template; The parameters configured in the target parameter file are determined as target parameters.

3. The method according to claim 1, characterized in that The parsing result includes at least one violation entry, and each violation entry includes the following attributes: Rule name, used to identify the rule violated by the offending entry; Violating content, which indicates code snippets or design elements that violate the rules; Source file path and row and column position: used to indicate the location of the source file where the illegal content is located; Design unit: used to indicate the context information involved in the rule content; Violation Type: used to indicate the type of rule violated by the violation entry; Severity level and rule level: used to quantify the impact of violations and the importance of rules.

4. The method according to claim 3, characterized in that: The displaying of the analysis result through an interactive page includes: Extracting illegal entries from the parsing result, and obtaining the number of illegal entries contained in the parsing result; Obtaining a display threshold of the interactive page; In response to the number of the illegal entries being greater than the display threshold, the illegal entries are displayed in pages in the interactive page, wherein the number of illegal entries displayed on each page is not greater than the display threshold.

5. The method according to claim 4, characterized in that Each illegal entry displayed in the interactive page corresponds to a source code link; the method further includes: In response to receiving a click operation of the user on a target source code link, obtaining a target violation entry corresponding to the target source code link; Obtain the violation content of the target violation entry; The illegal content of the target illegal entry is displayed in the form of a pop-up window.

6. The method according to claim 4, characterized in that The method further comprises: Obtaining the screening conditions set by the user through the interactive page; Filtering the at least one illegal entry based on the filtering condition to determine illegal entries that meet the filtering condition; Violation entries that meet the screening conditions are displayed through the interactive page.

7. The method according to claim 4, characterized in that Each violation item displayed in the interactive page corresponds to a check box; the method further includes: In response to receiving a selection operation of the user on a target check box, obtaining a violation entry corresponding to the target check box; Get preset report templates; A problem report is generated based on the report template and the violation items corresponding to the target check boxes.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Obtaining an error log file sent by the test tool server, wherein the error log file is generated by the target test tool when an exception occurs during the test process of the item under test, and is sent to the FPGA software integrated test management platform through the test tool server; The content of the error log file is displayed through the task execution status monitoring interface.

9. An FPGA software integrated test management platform, characterized in that: The FPGA software integrated test management platform adopts a B / S architecture and is connected to a test tool server in communication. The test tool server is pre-installed with different FPGA software test tools. The FPGA software integrated test management platform includes: A first acquisition module is used to acquire the target test tool and the uploaded test item selected by the user through the operation page provided by the FPGA software integrated test management platform; A second acquisition module is used to acquire target parameters configured by the user through the operation page and matching the target test tool and the tested item; A script generation module, used to generate a test script according to the target parameters using the operation commands of the target test tool; A sending module, used to send the tested project and the test script to the test tool server, so that the test tool server starts the target test tool to execute the test script to test the tested project, and generates a test result file and returns it to the FPGA software integrated test management platform; A receiving module, used for receiving the test result file sent by the test tool server; A parsing module, used for parsing the test result file to obtain a parsing result; The display module is used to display the analysis results through an interactive page.

10. An electronic device, comprising: processor; as well as Memory for storing programs, Wherein, the program includes instructions, and when the instructions are executed by the processor, the processor executes the steps of the testing method based on the FPGA software integrated testing management platform according to any one of claims 1-8.

Citation Information

Patent Citations

  • Script code detection method, device, computer device, and storage medium

    CN109271315A

  • Network security test integrated device

    CN113055408A

  • Integrated test management platform for FPGA (Field Programmable Gate Array) test tool

    CN113706110A

Cited By

  • Test document generation method and device based on FPGA software test

    CN120448270A