Management method and system for testing electronic control software of diesel engine

Abstract

The invention discloses a management method and system for testing electronic control software of a diesel engine. The management method comprises the following steps that S1, a user logs in a platform website and carries out authority verification; s2, a user submits defects and demands on the platform website; s3, calling an iteration plan configuration module to create an iteration plan; s4, establishing a database for training; s5, automatically associating the demand, the test case, the defect and the test report through a process association engine; s6, based on the test cases in the database, generating a multi-dimensional statistical chart through a chart statistics and analysis module; and S7, automatically integrating the associated data through a report generation and export module, and generating a PDF or Word format report. The problems that in the prior art, engine electric control software is low in testing efficiency, problem tracing is difficult, real-time monitoring and dynamic feedback of the testing process are difficult to achieve, and particularly the requirements of complex systems such as diesel engine electric control software for accuracy and timeliness of the testing process cannot be met can be solved.

Description

Technical Field

[0001] This invention relates to the field of diesel engine electronic control software testing technology, and in particular to a management method and system for testing diesel engine electronic control software. Background Technology

[0002] In the current field of diesel engine electronic control software test management, a distributed tool combination management model is generally adopted, which is mainly manifested in manually recording test requirements and defects through Excel spreadsheets, storing test cases in local documents, and relying on independent statistical software for data analysis.

[0003] Although existing technologies provide database-based test management systems that support the input of defects and requirements via a web interface, they still have three prominent technical shortcomings:

[0004] First, the relationship between test cases and requirements needs to be established manually, which leads to insufficient correlation strength and is prone to errors.

[0005] Secondly, the iterative planning and test execution phases are disconnected and lack an effective coordination mechanism;

[0006] Furthermore, the data analysis function is limited to basic table display and cannot achieve multi-dimensional visualization of test progress and quality trends.

[0007] This fragmented management model not only leads to low testing efficiency and difficulty in tracing problems, but also makes it difficult to achieve real-time monitoring and dynamic feedback of the testing process. In particular, it cannot meet the accuracy and timeliness requirements of complex systems such as diesel engine electronic control software. These technical deficiencies directly result in core problems such as isolated test data, weak correlation, and insufficient analytical capabilities. This leads to pain points in the test management process, such as information fragmentation, asynchronous status, and insufficient decision support. Therefore, there is an urgent need to build an integrated platform solution that can achieve unified data management, automatic status correlation, and intelligent analysis.

[0008] The information disclosed in this background section is intended only to enhance the understanding of the overall background of the invention and should not be construed as an admission or in any way implying that the information constitutes prior art known to those skilled in the art. Summary of the Invention

[0009] The purpose of this invention is to provide a management method and system for testing electronic control software of diesel engines, which can solve the problems in the background art.

[0010] To achieve the above objectives, this invention provides a management method for testing diesel engine electronic control software, comprising the following steps: S1: The user logs into the platform website and performs permission verification to obtain a user role. The system assigns operation permissions according to the user role; wherein, the user role includes, but is not limited to, tester and project manager; S2: The user opens the defect and requirement submission interface on the platform website, creates and stores defect and requirement information, and the system automatically generates a unique number based on the defect and requirement information; S3: The user role is that of the project manager, and calls the iteration planning configuration module to create an iteration plan, specifying the time range, target and requirement ID. The system automatically detects resource conflicts and provides a prompt; S4: A database is established for training, the database including test cases; the test cases are stored in a structured form in the database. The database records a number, name, steps, expected result, and associated requirement ID field for each test case. The database supports version management and reuse. S5: The process association engine automatically associates requirements, test cases, defects, and test reports. Requirements are associated with test cases via requirement IDs, and test case execution results are associated with defects via test case IDs. Changes in defect status trigger updates to associated requirement statuses. S6: Based on the test cases in the database, the chart statistics and analysis module generates multi-dimensional statistical charts, including defect trend charts, requirement completion pie charts, test case pass rate bar charts, and iteration progress burn-down charts. S7: The report generation and export module automatically integrates associated data to generate PDF or Word reports containing test execution summaries, defect statistics, and requirement coverage.

[0011] In one or more embodiments, in step S1: the step of obtaining user roles includes, but is not limited to: importing the company job database and assigning the user roles in a manner that takes precedence over the user's login to the platform website; or the user selects a role after logging into the platform website; in step S2: the defect and requirement information includes, but is not limited to: title, description, priority, and associated modules.

[0012] In one or more embodiments, in step S5, the association logic of the process association engine includes: S51: The system establishes a bidirectional association between the requirements and the test cases through the requirement ID, and automatically synchronizes the test cases when the requirement status changes; S52: The execution result of the test case is associated with the defect through the test case ID. If the execution fails, a defect record is automatically created and associated with the corresponding test case; S53: A change in the defect status triggers an update of the associated requirement status. When the defect is marked as "fixed", the completion rate of the associated requirement is automatically verified; S54: The test report is associated with the iteration plan through the iteration ID. The report content dynamically reflects the test progress and quality indicators of the current iteration.

[0013] In one or more embodiments, the operation of the chart statistics and analysis module in step S6 includes: S61: generating a defect trend chart based on defect submission time and module classification, supporting the display of changes in the number of newly added and closed defects by week, month, or iteration cycle; S62: visually displaying the proportion of implemented, in progress, and unprocessed requirements through a pie chart of requirement completion, with data derived from the correlation analysis between requirement status and test case coverage; S63: generating a pass rate bar chart based on the test case execution results, statistically analyzing the proportion of passed, failed, and blocked test cases by module or iteration stage; S64: dynamically displaying the relationship between remaining workload and time using an iteration progress burn-down chart, with data calculated in real time by the iteration planning configuration module and test execution results.

[0014] In one or more embodiments, the database functions as follows: the test cases are stored in a relational database in structured JSON or XML format, with fields including a globally unique ID, name, preconditions, execution steps, expected results, associated requirement ID, creation time, and last modification time; it supports test case version management, retaining historical version records for each modification, allowing rollback to any version and comparison of differences; it enables test case reuse through associated requirement IDs, recommending historical test cases with a matching degree higher than a threshold when a new requirement is similar to a historical requirement; and it provides a batch import / export interface for test cases, supporting the conversion of Excel templates into platform structured data.

[0015] Secondly, the present invention provides a management system for testing diesel engine electronic control software, based on a management method for testing diesel engine electronic control software as described in any one of claims 1-5, characterized in that it includes: a user login and permission verification module, used to verify user identity and assign operation permissions according to role; a defect and requirement submission module, providing a web version of the defect and requirement information interface for user input, and automatically generating a unique number to be stored in the database; an iteration planning configuration module, used to create the iteration plan and associate the defect and requirement information, integrating conflict detection and reminder functions; a test case storage and management module, realizing the storage, version management and reuse of structured test cases; a process association engine, realizing automatic association and status synchronization between requirements, test cases, defects and reports through the requirement ID, test case ID and iteration ID; a chart statistics and analysis module, extracting data from the database to generate defect trend charts, requirement completion pie charts, test pass rate bar charts and burn-down charts; and a report generation and export module, automatically integrating test data to generate PDF or Word format reports.

[0016] In one or more embodiments, the process association engine further includes: a requirement-use case association unit, which binds requirements and test cases through the requirement ID and automatically notifies the person in charge of the associated use case when the requirement changes; a use case-defect association unit, which automatically creates a defect record when a test case fails to execute and associates the defect ID with the original use case; a defect-requirement feedback unit, which adjusts the priority of associated requirements according to the defect status and triggers a requirement refactoring suggestion if the defect recurs; and an iteration-report synchronization unit, which dynamically updates the report content based on the iteration plan to ensure that the report reflects the test progress in real time.

[0017] In one or more embodiments, the chart statistics and analysis module includes: a data acquisition unit that periodically extracts defect, requirement, use case, and iteration data from the database; a trend analysis unit that statistically analyzes defect density and convergence speed over time to identify testing bottleneck stages; a coverage calculation unit that calculates requirement coverage and code coverage based on the correlation between use cases and requirements; and a visualization rendering unit that uses the ECharts or D3.js library to generate interactive charts and supports exporting chart data to CSV format.

[0018] In one or more embodiments, the test case storage and management module further includes: a test case template library, which pre-sets common test scenario templates for diesel engine electronic control software, such as fuel injection control and emission diagnosis; a fuzzy search component, which supports searching for test cases by keywords, modules, or states, with results sorted by matching degree; an access control unit, which restricts the modification permissions of different roles for test cases, allowing only the project manager to delete test cases; and an automated verification unit, which checks for logical conflicts in steps and the integrity of fields when test cases are saved.

[0019] Compared with existing technologies, this application integrates all aspects of test management through a unified platform website, achieving the organic integration of functional modules such as user permission verification, defect and requirement submission, iteration planning configuration, and test case management; it establishes an automatic association mechanism between requirements, test cases, defects, and test reports by utilizing related fields such as requirement ID, test case ID, and iteration ID; it uses JSON or XML format for structured storage of test cases, supporting version management and historical traceability; and it automatically generates various statistical charts such as defect trend charts, requirement completion pie charts, test case pass rate bar charts, and iteration progress burn-down charts based on test data in the database. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and are intended to explain the invention. They are intended to be seen as illustrative of various combinations of preferred embodiments and do not constitute an undue limitation of the invention. In the drawings:

[0021] Figure 1This is a schematic diagram of the overall process of a management method and system for testing diesel engine electronic control software provided by the present invention. Detailed Implementation

[0022] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings, but it should be understood that the scope of protection of the present invention is not limited to the specific embodiments.

[0023] Unless otherwise expressly stated, throughout the specification and claims, the term "comprising" or its variations such as "including" or "comprises" shall be understood to include the stated elements or components without excluding other elements or other components.

[0024] The purpose of this invention is to provide a management method and system for testing diesel engine electronic control software, which can solve the problems of low testing efficiency, difficulty in tracing problems, and difficulty in achieving real-time monitoring and dynamic feedback of the testing process in existing engine electronic control software, especially the inability to meet the requirements of accuracy and timeliness of testing process for complex systems such as diesel engine electronic control software.

[0025] Example 1:

[0026] like Figure 1As shown, the present invention preferably provides a management method for testing diesel engine electronic control software, comprising the following steps: S1: The user logs into the platform website and performs permission verification to obtain a user role. The system assigns operation permissions according to the user role; wherein, the user role includes, but is not limited to, tester and project manager; S2: The user opens the defect and requirement submission interface on the platform website, creates and stores defect and requirement information, and the system automatically generates a unique number according to the defect and requirement information; S3: The user role is that of the project manager, calls the iteration planning configuration module to create an iteration plan, specifies the time range, target and requirement ID, and the system automatically detects resource conflicts and provides a prompt; S4: A database is established for training, the database including test cases; the test cases are stored in the database in a structured form. Each test case record includes a number, name, steps, expected result, and associated requirement ID fields; the database supports version management and reuse; S5: Automatically associate requirements, test cases, defects, and test reports through the process association engine, wherein requirements are associated with test cases through requirement IDs, test case execution results are associated with defects through test case IDs, and defect status changes trigger associated requirement status updates; S6: Based on the test cases in the database, generate multi-dimensional statistical charts through the chart statistics and analysis module, including defect trend charts, requirement completion pie charts, test case pass rate bar charts, and iteration progress burn-down charts; S7: Automatically integrate associated data through the report generation and export module to generate PDF or Word format reports containing test execution summaries, defect statistics, and requirement coverage.

[0027] Specifically, this embodiment achieves standardization and digitization of diesel engine electronic control software testing by constructing a complete test management process system. The technical effects are reflected in three levels: First, the user permission verification mechanism ensures test data security and prevents data contamination caused by unauthorized operations; second, the automatic numbering function for defect and requirement submissions establishes a unique identification system, providing a basis for subsequent traceability; third, the conflict detection function of the iteration planning can provide early warning of resource allocation conflicts, avoiding test progress delays. In particular, the process association engine forms a data closed loop through multi-dimensional associations such as requirement IDs and use case IDs.

[0028] When a test case fails, the system automatically creates a defect record and reverse-marks the associated requirements. This automatic linkage mechanism solves the problems of lag and error caused by manual information transmission in traditional testing. Finally, the report generation module integrates all the data in the process, forming a visualized data management system and improving testing efficiency.

[0029] In a preferred embodiment, step S1 includes, but is not limited to: importing the company's job database and assigning the user role before the user logs into the platform website; or the user selecting a role after logging into the platform website.

[0030] In step S2: the defect and requirement information includes, but is not limited to: title, description, priority and associated modules.

[0031] In a preferred embodiment, in step S5, the association logic of the process association engine includes:

[0032] S51: The system establishes a bidirectional association between the requirements and the test cases through the requirement ID, and automatically synchronizes the test cases when the requirement status changes;

[0033] S52: The test case execution result is associated with the defect through the test case ID. If the execution fails, a defect record is automatically created and associated with the corresponding test case.

[0034] S53: Defect status changes trigger associated requirement status updates. When a defect is marked as "fixed", the completion rate of associated requirements is automatically verified.

[0035] S54: The test report and iteration plan are associated through the iteration ID, and the report content dynamically reflects the test progress and quality indicators of the current iteration.

[0036] This implementation refines the association engine by using a two-way association between requirements and use cases. When requirements change, the status of associated use cases is automatically updated, preventing test cases from becoming disconnected from requirements. The association between use cases and defects enables automatic archiving of faults, reducing the workload of manual data entry. The defect-requirement feedback mechanism establishes a quality closed loop. When defects recur, they can be retrieved and insights can be provided for the correction of requirements, preventing the recurrence of problems from the source.

[0037] In a preferred embodiment, step S6 includes the following operations of the chart statistics and analysis module:

[0038] S61: Generate a defect trend chart based on defect submission time and module category, supporting the display of changes in the number of new and closed defects by week, month or iteration cycle;

[0039] S62: The pie chart visually displays the percentage of implemented, ongoing, and unprocessed requirements. The data comes from the correlation analysis between the requirement status and the test case coverage.

[0040] S63: Generate a pass rate histogram based on the test case execution results, and statistically analyze the proportion of pass, failure and blocking test cases by module or iteration stage;

[0041] S64: The remaining workload and time relationship are dynamically displayed using the iteration progress burn-down chart. The data is calculated in real time by the iteration planning configuration module and the test execution results.

[0042] The chart analysis module in this implementation provides multi-dimensional management value: the defect trend chart displays the convergence of issues over time, helping managers identify testing bottlenecks; the requirement completion pie chart intuitively reflects the health status of the project, providing a basis for resource allocation; the test pass rate bar chart breaks down quality status by module, accurately locating weak links; and the burn-down chart dynamically monitors iteration progress, accurately measuring test completion time and serving as a reference for subsequent planning.

[0043] In one preferred embodiment, the database includes the following functions:

[0044] The test cases are stored in a relational database in structured JSON or XML format, with fields including a globally unique ID, name, preconditions, execution steps, expected results, associated requirement ID, creation time, and last modification time.

[0045] Supports use case version management, retains historical version records for each modification, and allows rollback to any version and comparison of differences;

[0046] Use case reuse is achieved by associating requirement IDs. When a new requirement is similar to a historical requirement, the system recommends historical use cases with a matching degree higher than a threshold.

[0047] Provides a batch import / export interface for test cases, supporting the conversion of Excel templates into platform-structured data.

[0048] Specifically, the version management function can retain modification history, enabling rapid identification of the impact of changes when test regressions occur; the test case reuse mechanism reduces repetitive design work through similarity matching; and the batch import / export interface improves compatibility with traditional testing tools. These features collectively build a continuously accumulating test knowledge base, which is beneficial for the long-term iterative development of diesel engine electronic control software.

[0049] Example 2:

[0050] A management system for testing diesel engine electronic control software, based on the same concept as the management method for testing diesel engine electronic control software described in Embodiment 1, is characterized by comprising: a user login and permission verification module for verifying user identity and assigning operation permissions according to roles; a defect and requirement submission module for providing a web-based interface for user input of defect and requirement information, and automatically generating unique numbers for storage in a database; an iteration planning configuration module for creating the iteration plan and associating it with the defect and requirement information, integrating conflict detection and reminder functions; a test case storage and management module for storing, versioning, and reusing structured test cases; a process association engine for automatically associating and synchronizing the status of requirements, test cases, defects, and reports through requirement IDs, test case IDs, and iteration IDs; a chart statistics and analysis module for extracting data from the database to generate defect trend charts, requirement completion pie charts, test pass rate bar charts, and burn-down charts; and a report generation and export module for automatically integrating test data to generate PDF or Word format reports.

[0051] As a preferred embodiment, the process association engine further includes:

[0052] The requirement-test case association unit binds requirements and test cases through the requirement ID, and automatically notifies the person in charge of the associated test case when the requirement changes.

[0053] The test case-defect association unit automatically creates a defect record and associates the defect ID with the original test case when the test case fails to execute.

[0054] The defect-requirement feedback unit adjusts the priority of associated requirements based on the defect status, and triggers requirement refactoring suggestions if the defect recurs.

[0055] The iteration-report synchronization unit dynamically updates the report content based on the iteration plan, ensuring that the report reflects the test progress in real time.

[0056] In a preferred embodiment, the chart statistics and analysis module includes:

[0057] The data acquisition unit periodically extracts defect, requirement, use case, and iteration data from the database.

[0058] The trend analysis unit statistically analyzes defect density and convergence speed over time to identify testing bottleneck stages.

[0059] The coverage calculation unit calculates requirement coverage and code coverage based on the relationship between use cases and requirements;

[0060] The visualization rendering unit uses the ECharts or D3.js library to generate interactive charts and supports exporting chart data to CSV format.

[0061] In a preferred embodiment, the test case storage and management module further includes:

[0062] The test case template library contains pre-set templates for common test scenarios in diesel engine electronic control software, such as fuel injection control and emission diagnostics.

[0063] Fuzzy search component, supports searching for use cases by keywords, modules or status, with results sorted by matching degree;

[0064] The access control unit restricts the modification permissions of different roles for test cases; only the project manager can delete test cases.

[0065] The automated validation unit checks for logical conflicts in steps and the integrity of fields when saving test cases.

[0066] The foregoing description of specific exemplary embodiments of the invention is for illustrative and explanatory purposes. These descriptions are not intended to limit the invention to the precise forms disclosed, and it will be apparent that many changes and variations can be made in accordance with the foregoing teachings. The exemplary embodiments were chosen and described in order to explain the specific principles of the invention and its practical application, thereby enabling those skilled in the art to implement and utilize various different exemplary embodiments of the invention, as well as various different choices and variations. The scope of the invention is intended to be defined by the claims and their equivalents.

Claims

1. A management method for testing diesel engine electronic control software, characterized in that, Includes the following steps: S1: Users log in to the platform website and complete permission verification to obtain user roles. The system assigns operation permissions according to the user roles; wherein, the user roles include, but are not limited to: tester, project manager; S2: The user opens the defect and requirement submission interface on the platform website, creates and stores defect and requirement information, and the system automatically generates a unique number based on the defect and requirement information; S3: The user role is that of the project manager. The user calls the iteration planning configuration module to create an iteration plan, specifying the time range, target and requirement ID. The system automatically detects resource conflicts and prompts. S4: Establish a database for training, the database including test cases; the test cases are stored in the database in a structured form, and each test case record includes a number, name, steps, expected result, and associated requirement ID field; the database supports version management and reuse; S5: Automatically associate requirements, test cases, defects, and test reports through the process association engine. Requirements are associated with test cases through requirement IDs, test case execution results are associated with defects through test case IDs, and defect status changes trigger associated requirement status updates. S6: Based on the test cases in the database, generate multi-dimensional statistical charts through the chart statistics and analysis module, including a defect trend chart, a requirement completion pie chart, a bar chart of the test case pass rate, and an iteration progress burn-down chart; S7: Automatically integrates related data through the report generation and export module to generate PDF or Word reports containing test execution summaries, defect statistics, and requirement coverage.

2. The management method for testing diesel engine electronic control software according to claim 1, characterized in that, In step S1: The steps for obtaining user roles include, but are not limited to: importing the company's job database and assigning the user roles in a manner that takes precedence over the user's login to the platform website; or the user selecting a role after logging into the platform website. In step S2: the defect and requirement information includes, but is not limited to: title, description, priority and associated modules.

3. The management method for testing diesel engine electronic control software according to claim 2, characterized in that, In step S5, the association logic of the process association engine includes: S51: The system establishes a bidirectional association between the requirements and the test cases through the requirement ID, and automatically synchronizes the test cases when the requirement status changes; S52: The test case execution result is associated with the defect through the test case ID. If the execution fails, a defect record is automatically created and associated with the corresponding test case. S53: Defect status changes trigger associated requirement status updates. When a defect is marked as "fixed", the completion rate of associated requirements is automatically verified. S54: The test report and iteration plan are associated through the iteration ID, and the report content dynamically reflects the test progress and quality indicators of the current iteration.

4. The management method for testing diesel engine electronic control software according to claim 3, characterized in that, In step S6, the operations of the chart statistics and analysis module include: S61: Generate a defect trend chart based on defect submission time and module category, supporting the display of changes in the number of new and closed defects by week, month or iteration cycle; S62: The pie chart visually displays the percentage of implemented, ongoing, and unprocessed requirements. The data comes from the correlation analysis between the requirement status and the test case coverage. S63: Generate a pass rate histogram based on the test case execution results, and statistically analyze the proportion of pass, failure and blocking test cases by module or iteration stage; S64: The remaining workload and time relationship are dynamically displayed using the iteration progress burn-down chart. The data is calculated in real time by the iteration planning configuration module and the test execution results.

5. The management method for testing diesel engine electronic control software according to claim 4, characterized in that, The functions of the database include: The test cases are stored in a relational database in structured JSON or XML format, with fields including a globally unique ID, name, preconditions, execution steps, expected results, associated requirement ID, creation time, and last modification time. Supports use case version management, retains historical version records for each modification, and allows rollback to any version and comparison of differences; Use case reuse is achieved by associating requirement IDs. When a new requirement is similar to a historical requirement, the system recommends historical use cases with a matching degree higher than a threshold. Provides a batch import / export interface for test cases, supporting the conversion of Excel templates into platform-structured data.

6. A management system for testing diesel engine electronic control software, based on a management method for testing diesel engine electronic control software as described in any one of claims 1-5, characterized in that, include: The user login and permission verification module is used to verify user identity and assign operation permissions according to roles; The defect and requirement submission module provides a web-based interface for users to input defect and requirement information, and automatically generates a unique number to be stored in the database. The iterative planning configuration module is used to create the iterative plan and associate the defect and requirement information, and integrate conflict detection and reminder functions; The test case storage and management module enables the storage, version management, and reuse of structured test cases; The process association engine enables automatic association and status synchronization between requirements, use cases, defects, and reports through the requirement ID, use case ID, and iteration ID. The chart statistics and analysis module extracts data from the database to generate defect trend charts, requirement completion pie charts, test pass rate bar charts, and burn-down charts. The report generation and export module automatically integrates test data to generate PDF or Word reports.

7. The management system for testing diesel engine electronic control software according to claim 6, characterized in that, The process association engine further includes: The requirement-test case association unit binds requirements and test cases through the requirement ID, and automatically notifies the person in charge of the associated test case when the requirement changes. The test case-defect association unit automatically creates a defect record and associates the defect ID with the original test case when the test case fails to execute. The defect-requirement feedback unit adjusts the priority of associated requirements based on the defect status, and triggers requirement refactoring suggestions if the defect recurs. The iteration-report synchronization unit dynamically updates the report content based on the iteration plan, ensuring that the report reflects the test progress in real time.

8. The management system for testing diesel engine electronic control software according to claim 7, characterized in that, The chart statistics and analysis module includes: The data acquisition unit periodically extracts defect, requirement, use case, and iteration data from the database. The trend analysis unit statistically analyzes defect density and convergence speed over time to identify testing bottleneck stages. The coverage calculation unit calculates requirement coverage and code coverage based on the relationship between use cases and requirements; The visualization rendering unit uses the ECharts or D3.js library to generate interactive charts and supports exporting chart data to CSV format.

9. The management system for testing diesel engine electronic control software according to claim 8, characterized in that, The test case storage and management module also includes: The test case template library contains pre-set templates for common test scenarios in diesel engine electronic control software, such as fuel injection control and emission diagnostics. Fuzzy search component, supports searching for use cases by keywords, modules or status, with results sorted by matching degree; The access control unit restricts the modification permissions of different roles for test cases; only the project manager can delete test cases. The automated validation unit checks for logical conflicts in steps and the integrity of fields when saving test cases.

Images