Complete vehicle integration test case generation method and device, equipment and storage medium

Abstract

The invention relates to the technical field of test automation, in particular to a finished automobile integration test case generation method, device and equipment and a storage medium. Changes of function requirements are recognized through historical versions of finished automobile function implementation documents, and the changes are analyzed through an enterprise-level technology knowledge base and a function specification document; the method comprises the following steps of: acquiring an operation condition and an execution step of each function demand, generating an initial test case by combining a test case generation model with a test scene template, and finally checking the generated test case according to an enterprise-level technology knowledge base and a function specification document to form a final target test case. According to the scheme, through intelligent and automatic means, the efficiency and quality of whole vehicle testing are greatly improved, and powerful guarantee is provided for on-time delivery and successful online of whole vehicle development projects.

Description

Technical Field

[0001] The present invention relates to the technical field of test automation, and particularly to a method, device, equipment and storage medium for generating vehicle integration test cases. Background Art

[0002] With the rapid development of the automotive industry, the vehicle development cycle has been continuously shortened, and the functional complexity has increased significantly. Modern vehicles need to integrate various advanced electronic systems and intelligent functions, and the development and verification of these functions require a large amount of testing work to ensure the safety and reliability of the systems.

[0003] Test cases, as an important tool for verifying functional requirements, play a crucial role in the entire development cycle. During the vehicle development process, functional requirements change continuously as the project progresses, including the addition, deletion, and modification of functions. These changes require test cases to be updated in real time to ensure the comprehensiveness and effectiveness of testing. Traditional test case generation methods mainly rely on manual writing, which is not only inefficient but also prone to inconsistencies in test cases due to requirement changes. In addition, with the increase in functional complexity, the difficulty and workload of manually writing test cases also increase significantly.

[0004] Therefore, how to efficiently and accurately generate and manage test cases during the vehicle development process to adapt to frequent changes in functional requirements and ensure the comprehensiveness and reliability of testing has become a technical problem urgently to be solved in this industry. Summary of the Invention

[0005] The main purpose of the present invention is to provide a method, device, equipment and storage medium for generating vehicle integration test cases, aiming to solve the technical problem of how to efficiently and accurately generate and manage test cases during the vehicle development process to adapt to frequent changes in functional requirements and ensure the comprehensiveness and reliability of testing in the prior art.

[0006] To achieve the above purpose, the present invention provides a method for generating vehicle integration test cases, and the method includes the following steps: Determine the content of functional requirement changes according to the vehicle functional implementation document; Obtain test case generation instruction information according to the content of the functional requirement changes; Input the test case generation instruction information into a test case generation model to obtain an initial test case generation result; Review the initial test case generation result according to a test case review guidance document to obtain a target test case set.

[0007] Optionally, the step of determining the content of functional requirement changes according to the vehicle functional implementation document includes: Compare the function implementation document with the function implementation document of the historical version to obtain the changed content of the function document; Based on the changed content of the function document, obtain the newly added items of function requirements and the changed items of function requirements; Use the newly added items of function requirements and the changed items of function requirements as the changed content of the function requirements.

[0008] Optionally, obtaining the test case generation instruction information according to the changed content of the function requirements includes: Based on the enterprise-level technical knowledge base, analyze the changed content of the function requirements to obtain the operating conditions and execution steps of each function requirement; According to the function specification document, perform technical-level correction on the operating conditions and execution steps of each function requirement to obtain the operating conditions and execution steps of each function requirement after the correction is completed; According to the operating conditions and execution steps after the correction is completed, obtain the test case generation instruction information corresponding to the function requirement.

[0009] Optionally, analyzing the changed items of the function requirements based on the enterprise-level technical knowledge base to obtain the operating conditions and execution steps of each function requirement includes: Connect to the enterprise-level technical knowledge base through the encrypted API interface to obtain the real-time updated enterprise technical documents; Based on the preset information extraction rules, extract the technical support information corresponding to the changed items of the function requirements from the enterprise technical documents, and the extraction process follows the preset security desensitization rules of the enterprise technical documents; Perform semantic analysis on the changed items of the function requirements to obtain the function description information of the function requirements; Based on the technical support information, perform technical logic analysis on the function description information of the function requirements to obtain the operating conditions and execution steps of each function requirement; Among them, the function description information includes the function domain to which it belongs, the requirement ID, the requirement overview, and the function expected result, the operating conditions include the precondition, the trigger condition, and the exit condition, and the execution steps include the operation subject, the action, and the object of action.

[0010] Optionally, inputting the test case generation instruction information into the test case generation model to obtain the initial test case generation result includes: According to the function description information in the test case generation instruction information, determine the test scenario template, and the test scenario template includes the application scenario, the test boundary conditions, and the abnormal situations; Decompose the execution steps in the test case generation indication information to obtain structured implementation steps, where the fine granularity of the structured implementation steps is the smallest execution step for single execution. Input the test case generation indication information, the test scenario template, and the structured implementation steps into the test case generation model to obtain an executable automated test script, and use the automated test script as the initial test case generation result.

[0011] Optionally, the initial test case generation result is audited according to the test case audit guidance document to obtain a target test case set, including: Obtain industry-related standard documents and risk case determination rules according to the test case audit guidance document; According to the risk case determination rules, label the risk levels of each test case in the initial test case generation result to obtain a subset of high-risk test cases and a subset of low-risk test cases; According to the industry-related standard documents, conduct technical execution review and manual review on the high-risk test case set to obtain a reviewed test case set; According to the preset test case merging rules, de-duplicate and merge the low-risk test case subset and the reviewed test case set to obtain a test case set that complies with the execution specifications; Perform format normalization processing on the test case set that complies with the execution specifications to obtain the target test case set.

[0012] Optionally, the performing format normalization processing on the test case set that complies with the execution specifications to obtain the target test case set includes: Obtain the test case format specification according to the test case audit guidance document; Obtain the structured output rule according to the test case format specification; According to the structured output rule, perform format conversion processing on the test case set that complies with the execution specifications to obtain the target test case set.

[0013] In addition, to achieve the above object, the present invention also proposes a vehicle integrated test case generation device, and the vehicle integrated test case generation device includes: A function requirement management module, which is used to determine the function requirement change content according to the vehicle function implementation document; A function requirement analysis module, which is used to obtain test case generation indication information according to the function requirement change content; A test case generation module, which is used to input the test case generation indication information into the test case generation model to obtain an initial test case generation result; A test case review module is used to review the results generated from the initial test cases according to the test case review guidance document to obtain a target test case set.

[0014] In addition, to achieve the above object, the present invention also provides a vehicle integrated test case generation device, which includes: a memory, a processor, and a vehicle integrated test case generation program stored on the memory and executable on the processor. The vehicle integrated test case generation program is configured to implement the steps of the vehicle integrated test case generation method as described above.

[0015] In addition, to achieve the above object, the present invention also provides a storage medium on which a vehicle integrated test case generation program is stored. When the vehicle integrated test case generation program is executed by a processor, it implements the steps of the vehicle integrated test case generation method as described above.

[0016] One or more technical solutions proposed in this application have at least the following technical effects: By comparing the function implementation documents of historical versions, this solution identifies changes in function requirements, extracts elements such as function domains and conditional constraints from the enterprise-level technical knowledge base to form test case generation indication information, combines multi-dimensional technical verification (function specification correction, semantic analysis, technical logic parsing) to generate structured implementation steps, and automatically converts them into automated scripts for specific scenarios using a test model; through a risk stratified review mechanism, the initial test cases are dynamically classified, and a standard file compliance review and deduplication and merging strategy are adopted, and finally a test case set that meets industry specifications is output in a structured format. This solution realizes full-process optimization in the aspects of change tracking, requirement mapping, test case generation, and review by constructing a knowledge-driven automated test generation link. Description of the Drawings

[0017] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0019] Figure 1 It is a flowchart of the first embodiment of the vehicle integrated test case generation method of the present invention; Figure 2 It is a system architecture diagram of the first embodiment of the vehicle integrated test case generation method of the present invention; Figure 3It is a schematic flowchart of the second embodiment of the method for generating vehicle integration test cases according to the present invention; Figure 4 It is a schematic flowchart of the third embodiment of the method for generating vehicle integration test cases according to the present invention; Figure 5 It is a structural block diagram of the first embodiment of the device for generating vehicle integration test cases according to the present invention; Figure 6 It is a schematic structural diagram of a vehicle integration test case generation device which is the hardware operating environment involved in the solution of the embodiment of the present invention.

[0020] The realization, functional features and advantages of the object of the present invention will be further described with reference to the embodiments and the accompanying drawings. Detailed Embodiments

[0021] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0022] In order to better understand the technical solutions of the present application, the following will be described in detail with reference to the accompanying drawings of the specification and specific embodiments.

[0023] The main solution of the embodiments of the present application is: determining the content of functional requirement changes according to the vehicle functional implementation document; obtaining test case generation instruction information according to the content of the functional requirement changes; inputting the test case generation instruction information into a test case generation model to obtain an initial test case generation result; and auditing the initial test case generation result according to a test case review guidance document to obtain a target test case set.

[0024] Currently, during the entire development cycle of a vehicle, the software and hardware debugging of each part requires corresponding test cases for actual testing to verify the correctness and reliability of functions. However, there are numerous functions during the vehicle development process, and the functional requirements are constantly changing, including the addition, deletion and modification of functions. Traditional test case generation methods are difficult to adaptively adjust in real time following the changes in functions, resulting in low efficiency in the generation and update of test cases. In addition, manually writing test cases is prone to errors due to understanding deviations or incomplete information, affecting the accuracy and reliability of test results. Therefore, how to efficiently and accurately generate and manage test cases during the vehicle development process is a technical problem that urgently needs to be solved at present.

[0025] This application identifies changes in functional requirements during the development process by comparing functional implementation documents of historical versions, extracts elements such as functional domains and conditional constraints from the enterprise-level technical knowledge base to form test case generation indication information, combines multi-dimensional technical verification (functional specification correction, semantic analysis, technical logic parsing) to generate structured implementation steps, and automatically converts them into automated scripts for specific scenarios using a test model; dynamically classifies initial test cases through a risk stratification review mechanism, adopts a standard document compliance review and duplicate removal and merging strategy, and finally outputs a test case set that complies with industry specifications in a structured format. This solution realizes full-process optimization in the aspects of change tracking, requirement mapping, test case generation, and review by constructing a knowledge-driven automated test generation link.

[0026] It should be noted that the execution entity of the present invention can be a vehicle integration test case generation device, or a computing service device with data processing, network communication, and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or a thermal management device of a vehicle integration test case generation device capable of implementing the above functions. This embodiment does not make specific limitations in this regard. The following takes the vehicle integration test case generation device as the execution entity as an example to illustrate this embodiment and the following embodiments.

[0027] Based on this, an embodiment of this application provides a method for generating vehicle integration test cases, referring to Figure 1 , Figure 1 which is a schematic flowchart of the first embodiment of the method for generating vehicle integration test cases of this application.

[0028] In this embodiment, the method for generating vehicle integration test cases includes steps S10 to S30: Step S10: Determine the content of functional requirement changes according to the vehicle functional implementation document.

[0029] It should be noted that the vehicle functional implementation document refers to a document used to describe in detail the vehicle functional requirements and their specific implementation details during the vehicle development process. Due to the large number and complexity of vehicle functions in the modern vehicle development process, functional requirements will continue to be dynamically adjusted as the development stage progresses, including the addition, deletion, or optimization of functions. In order to cope with this high-frequency change, a document system with time stamps or version stamps needs to be adopted to ensure the traceability, consistency, and management efficiency of functional requirements, so as to support the efficient progress of the development process.

[0030] In a feasible implementation manner, determining the changed content of the functional requirements according to the vehicle-level functional implementation document includes: comparing the functional implementation document with the functional implementation document of the historical version to obtain the changed content of the functional document; obtaining the newly added items of the functional requirements and the changed items of the functional requirements according to the changed content of the functional document; and using the newly added items of the functional requirements and the changed items of the functional requirements as the changed content of the functional requirements.

[0031] It should be noted that by comparing the current version of the vehicle-level functional implementation document with the historical version, the changed content of the functional implementation document before and after the version can be determined. Generally, before generating the test cases in this embodiment, the system will first retrieve the functional implementation document stored locally in the test case database and confirm the version number of the document. If the version numbers do not match, the system will automatically pull the latest functional implementation document from the cloud or the version control system to ensure that the generation of test cases is based on the latest functional requirements.

[0032] It can be understood that according to the extracted changed content, the system will automatically map it to the corresponding test case template to generate or update test cases. For newly added functions, the system will automatically generate test cases based on the function description; for changed functions, the system will adjust the existing test cases to meet the new requirements; for deleted functions, the system will mark the relevant test cases as "abandoned" and remove them from the test case library.

[0033] Step S20: Obtain the test case generation instruction information according to the changed content of the functional requirements.

[0034] It should be noted that the changed content of the functional requirements refers to the newly added, deleted, or optimized changes in the functional requirements during the vehicle development process as the development stage progresses. These changed contents usually include multiple functional requirements, and corresponding test case generation instruction information needs to be generated for each functional requirement.

[0035] It can be understood that the test case generation instruction information is the guiding information generated based on the changed content of the functional requirements. This information is used to guide the generation of test cases, covering all aspects of the functional requirements comprehensively, including preconditions, trigger conditions, exit conditions, and specific execution steps. These instruction information not only guide the writing of test cases but also ensure that the test cases can accurately verify the changes in the functional requirements.

[0036] Step S30: Input the test case generation instruction information into the test case generation model to obtain the initial test case generation result.

[0037] It is understandable that the test case generation model is a rule - and algorithm - based system for automatically generating test cases. The test case generation model first parses the input indication information to identify the key elements of the functional requirement changes, such as the functional domain, requirement ID, requirement overview, and expected results. Then, the model uses structured prompt design to transform these elements into specific test scenarios and steps. Through the Chain of Thought (CoT) generation strategy, the model constructs logically coherent test cases to ensure that each test case can cover all aspects of the functional requirements, including pre - conditions, trigger conditions, exit conditions, and execution steps. In addition, the model also verifies the consistency between the test cases and the functional requirements to ensure that the generated test cases can accurately reflect the changes in the functional requirements and meet industry standards and enterprise specifications. Finally, the generated test cases will be output as the initial test case generation result, providing a basis for subsequent review and optimization.

[0038] Step S40: Review the initial test case generation result according to the test case review guidance document to obtain the target test case set.

[0039] It should be noted that the test case review guidance document is a document formulated by the enterprise according to industry standards and its own technical specifications to guide the test case review process. This document integrates industry - related standard documents and the enterprise's internal review rules to ensure the comprehensiveness and accuracy of the test cases.

[0040] It is understandable that the test case review guidance document provides the technical specifications and safety requirements that the test cases need to follow, helping to identify and correct problems in the test cases.

[0041] In a feasible implementation manner, step S30 may include steps A11 - A13: Step A11: Determine the test scenario template according to the function description information in the test case generation indication information.

[0042] It should be noted that the function description information includes, but is not limited to, the functional domain to which the functional requirement belongs, requirement ID, requirement overview, and functional expected results.

[0043] It is understandable that the test scenario template is the basic framework for test case generation. This framework defines the specific test scenarios, boundary conditions, and exception situations. The test scenario template is retrieved from a pre - defined template library. The template library stores multiple test scenario templates, and each template corresponds to different types of functional requirements. By analyzing the function description information, the system can identify the key elements of the test scenario, thus quickly matching the test scenario template that meets the functional requirements.

[0044] It should be understood that the test scenario template here includes the application scenario, test boundary conditions, and abnormal situations. The application scenario describes the typical scenarios of the function in actual use; the test boundary conditions define the behavior of the function in extreme or boundary situations; and the abnormal situations cover the performance of the function under abnormal conditions. These elements together ensure that the test cases can comprehensively verify the function requirements.

[0045] Step A12: Decompose the execution steps in the test case generation indication information to obtain structured implementation steps.

[0046] It can be understood that the structured implementation steps are to decompose complex execution steps into simple and executable single steps. This decomposition process ensures the accuracy and operability of the test cases, enabling the test cases to accurately verify every detail of the function requirements.

[0047] It should be understood that the fine granularity of the structured implementation steps is the smallest execution step for a single execution. For example, for the function requirement "when the rain sensor triggers the threshold, close the sunroof servo motor", the structured implementation steps may include two independent steps: "detect the rain sensor triggering the threshold" and "close the sunroof servo motor". This fine-grained decomposition helps improve the accuracy and coverage of the test.

[0048] Step A13: Input the test case generation indication information, test scenario template, and structured implementation steps into the test case generation model to obtain executable automated test scripts, and use the automated test scripts as the initial test case generation result.

[0049] It should be noted that when inputting the test case generation indication information, test scenario template, and structured implementation steps into the test case generation model, the model generates executable automated test scripts based on the input information. These scripts not only contain the specific steps of the test but also define the expected results and verification conditions of the test. The generated automated test scripts are output as the initial test case generation result and can be directly used in the automated test platform. This automated generation of test scripts not only reduces human errors but also ensures the comprehensiveness and consistency of the test cases, supporting the development team to collaborate in a complex system environment.

[0050] As Figure 2 shown, Figure 2 is the system architecture schematic diagram of the first embodiment of the vehicle integration test case generation method of the present invention.

[0051] It should be noted that Figure 2The test case generation model in it introduces domain background knowledge and functional specification documents through specific API interfaces to ensure that the test case generation model can understand industry standards and enterprise specifications. Then, it performs automated data processing according to the functional implementation document, decomposes the functional requirements into structured inputs, and provides a basis for subsequent test case generation. In addition, the model adopts a step-by-step reasoning (Chain of Thought, CoT) generation strategy to ensure the logic and integrity of the test case generation process. Then, it conducts a functional consistency review to ensure that the generated test cases are consistent with the functional requirements, avoiding omissions or errors. And it continuously conducts traceability verification for each test case to ensure that the test cases can cover changes in functional requirements and support the traceability of enterprise distributed development. For test cases that require manual review, a manual review mechanism is provided. After review and optimization, the final version of the test cases is output to ensure the quality and usability of the test cases.

[0052] It can be understood that in the entire system architecture, a one-to-many association is established between each functional requirement and the test case library. Specifically, one functional requirement corresponds to at least one test case. This operation of associating with the test case library can support the rapid response to requirement changes and the dynamic update of test cases. In addition, modular management of the generated test cases according to their belonging functional modules can maintain the lifecycle of any test case in the long term. On this basis, through the version management and traceability mechanism, it is ensured that the historical records and changes of each test case can be traced, supporting the transparency and consistency of the development process.

[0053] In this embodiment, the content of the functional requirement change is determined through the vehicle function implementation document; according to the content of the functional requirement change, test case generation indication information is obtained; the test case generation indication information is input into the test case generation model to obtain an initial test case generation result; and the initial test case generation result is reviewed according to the test case review guidance document to obtain a target test case set.

[0054] To sum up, this technical solution significantly improves the efficiency and quality of test case generation through an automated process. First, the dynamic update of the vehicle function implementation document ensures that changes in functional requirements are promptly reflected in the test cases, reducing repeated modifications and shortening the development cycle. Second, the test case generation model combines semantic analysis and step-by-step reasoning to ensure that the test cases are logically complete and comprehensively covered, improving the test coverage rate and quality. The functional consistency review and traceability verification ensure that the test cases meet industry standards and avoid omissions and errors. Modular management and version control support the long-term maintenance and historical traceability of test cases, ensuring development transparency and consistency. Automated test scripts reduce human errors and improve test efficiency. Overall, this solution optimizes the test process, provides an efficient and reliable test verification mechanism, and enhances the vehicle performance and competitiveness.

[0055] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar content as in the above-mentioned first embodiment can be referred to the above introduction and will not be repeated hereinafter. On this basis, please refer to Figure 3 , in step S20 of the vehicle integration test case generation method, it includes steps S201 to S203: Step S201: Based on the enterprise-level technical knowledge base, analyze the content of the functional requirement changes to obtain the operating conditions and execution steps of each functional requirement.

[0056] It should be noted that by integrating information such as professional technical knowledge, functional specification documents, and ECU design standards in the enterprise-level technical knowledge base, the test case generation model can accurately understand and process each functional requirement change item. This process not only includes the syntax and semantic analysis of functional requirements, but also includes in-depth mining and logical verification of technical support information, so as to construct a complete causal chain of operating conditions - execution actions.

[0057] It can be understood that the mapping relationship between the operating conditions and execution steps of each functional requirement can be obtained through logical reasoning, specifically including the compliance verification of condition parameters, the resource dependency analysis and conflict detection of execution steps, and finally generating an operation process that meets the functional safety standards.

[0058] Step S202: According to the functional specification document, perform technical-level corrections on the operating conditions and execution steps of each functional requirement to obtain the operating conditions and execution steps of each functional requirement after the correction is completed.

[0059] It should be noted that the technical-level correction includes the following core contents: comparing and adjusting the parameter thresholds in the operating conditions (such as the rain trigger threshold, timeout interruption duration) with the technical indicators in the enterprise functional specification document to ensure that they meet the error requirements; secondly, through static code analysis, detecting and eliminating potential resource competition (such as CAN bus contention) or timing contradictions (such as the hardware response times corresponding to multiple consecutive steps do not match) in the execution steps.

[0060] It can be understood that the correction process realizes the iterative optimization of technical indicators through an automated tool chain, avoids the subjective deviation of manual adjustment, and each correction result generates a version record and attaches a digital signature to ensure the traceability of the correction history.

[0061] Step S203: According to the operating conditions and execution steps after the correction is completed, obtain the test case generation indication information corresponding to the functional requirement.

[0062] It is understandable that the test case generation instruction information is guiding information generated based on the operating conditions and execution steps of the functional requirements. This information ensures that the test cases can comprehensively cover all aspects of the functional requirements, including preconditions, trigger conditions, exit conditions, and specific execution steps. These instruction information not only guide the writing of test cases but also ensure that the test cases can accurately verify changes in functional requirements.

[0063] It should be understood that the generation process of the test case generation instruction information needs to ensure logical integrity and technical accuracy. The system first verifies the operating conditions to ensure that all preconditions, trigger conditions, and exit conditions are clear and there are no logical conflicts; secondly, it refines the execution steps, decomposing the execution steps into specific test operations to ensure that each step is executable and verifiable; then it integrates technical support information, combining the technical support information extracted from the enterprise technical knowledge base to ensure that the test case generation instruction information complies with industry specifications and enterprise standards; finally, it integrates the above information into structured test case generation instruction information to guide the writing and execution of test cases.

[0064] In a feasible implementation manner, step S201 may include steps B11 to B14: Step B11: Connect to the enterprise-level technical knowledge base through the encrypted API interface to obtain real-time updated enterprise technical documents.

[0065] It should be noted that the enterprise-level technical knowledge base integrates key information such as professional technical knowledge in the automotive electrical field, functional specification documents, and ECU design standards. Part of this information will be embedded in the hidden layer of the test case generation model to ensure that the generated test cases comply with industry specifications and enterprise standards.

[0066] It is understandable that connecting to the enterprise internal technical document library through a specific API interface can ensure that the test case generation model can obtain the latest technical document information in real time, guaranteeing the effectiveness of the generated test cases. To ensure data security, an encryption protocol and a permission verification mechanism can be designed for the API interface, allowing only authorized devices or users to access and preventing the leakage of sensitive information in enterprise development.

[0067] Step B12: Extract the technical support information corresponding to the functional requirement change items from the enterprise technical documents based on the preset information extraction rules.

[0068] It should be noted that the preset information extraction rules refer to a set of rules predefined by an enterprise for extracting information related to functional requirement change items from technical documents. These rules generally include methods such as keyword matching, pattern recognition, and semantic analysis to ensure the accuracy and relevance of the extracted information. The preset information extraction rules may also include data format conversion and standardization processing so that the extracted information can be directly used in the test case generation model.

[0069] It can be understood that the technical support information refers to the specific information extracted from the enterprise's technical documents and related to the functional requirement change items. Such information includes, but is not limited to, functional descriptions, design parameters, interface specifications, test standards, and safety requirements. The technical support information provides the necessary technical background and implementation details for test case generation, ensuring that the system can accurately understand the meaning of each technical detail of the functional requirements during the process of generating test cases.

[0070] It should be understood that the extraction process of the above steps follows the security desensitization rules predefined by the enterprise to prevent the original enterprise document information from being accessed or misused without authorization after extraction. These rules include encryption processing of sensitive data, access control over the extracted information, and anonymization processing of data, ensuring that the extracted information is only used for test case generation and does not disclose the enterprise's core technologies and business secrets.

[0071] Step B13: Conduct semantic analysis on the functional requirement change item to obtain the functional description information of the functional requirement.

[0072] It can be understood that the functional description information includes, but is not limited to, the functional domain to which the functional requirement belongs, requirement ID, requirement overview, and functional expected results. Specifically, the functional description information provides clear functional goals and verification criteria for test case generation, reduces modifications and tests caused by unclear requirements, and also facilitates the traceability and consistency management of functional requirements.

[0073] Step B14: Based on the technical support information, conduct technical logic analysis on the functional description information of the functional requirement to obtain the operating conditions and execution steps of each functional requirement.

[0074] It should be noted that for a specific functional requirement, such as "when the rain sensor triggers the threshold, close the sunroof servo motor", taking this as an example, the system will first analyze its grammatical structure to determine all elements of a single operation step, including the operation subject, action, and object of action. It is also necessary to further extract relevant information such as hardware components (such as rain sensors, servo motors) and signal parameters associated with the function, so as to construct a complete causal chain of operating conditions - execution actions.

[0075] It can be understood that in addition to establishing the causal chain of operating conditions - execution actions through basic syntactic structure analysis, the system also needs to conduct technical-level analysis on some functional requirements to ensure the logical integrity of the execution steps. For example, the servo motor rotation angle command must carry a CRC check code. If this part is missing in actual tests, it is still regarded as a failure in command generation. Secondly, it is also necessary to detect conflicts between operating conditions and system resources. For example, the system resource competition relationship between "reverse radar activation" and "automatic parking path planning". Therefore, these test cases need to further explore relevant operating conditions based on their technical principles before executing the tests.

[0076] It should be understood that according to different functional requirements, operating conditions can be roughly divided into three categories: preconditions, trigger conditions, and exit conditions. Preconditions ensure that the system is in the correct state before the function is executed. Trigger conditions define specific events or conditions for the function to start, while exit conditions clarify the conditions for the function to complete or interrupt. This classification helps the system accurately verify the function behavior in different test scenarios and ensure that the function works as expected in various situations.

[0077] In this embodiment, based on the enterprise-level technical knowledge base, the changed content of the functional requirements is analyzed to obtain the operating conditions and execution steps of each functional requirement; according to the function specification document, the operating conditions and execution steps of each functional requirement are corrected at the technical level to obtain the operating conditions and execution steps of each functional requirement after the correction is completed; according to the operating conditions and execution steps after the correction is completed, the test case generation indication information corresponding to the functional requirement is obtained.

[0078] In summary, through the enterprise-level technical knowledge base and the automated tool chain in this embodiment, the efficiency and quality of functional requirement change processing and test case generation are improved. The real-time updated knowledge base and semantic analysis ensure that requirement changes are accurately understood, thus shortening the development cycle. Technical-level correction realizes parameter tuning and resource conflict detection through automated tools, avoiding manual deviation. The generated test case indication information provides clear goals and verification criteria to ensure comprehensive test coverage. Modular management and version control support long-term maintenance and traceability to ensure development transparency. Overall, this solution optimizes the test process, provides an efficient and reliable verification mechanism, and improves the vehicle performance and competitiveness.

[0079] Based on the first embodiment of this application, in the third embodiment of this application, the same or similar content as in the above-mentioned first embodiment can be referred to the above introduction and will not be elaborated hereinafter. On this basis, please refer to Figure 4 , step S40 in the vehicle integration test case generation method includes steps S401 to S405: Step S401: Obtain industry-related standard documents and risk case determination rules according to the test case review guidance document.

[0080] It should be noted that the test case review guidance document is a document formulated by the enterprise according to industry standards and its own technical specifications, and is used to guide the review process of test cases. It integrates industry-related standard documents (such as ISO 26262, AUTOSAR, etc.) and the enterprise's internal risk management rules to ensure the comprehensiveness and accuracy of test cases.

[0081] It can be understood that industry-related standard documents provide the technical specifications and safety requirements that test cases need to follow, while the risk case determination rules are used to help identify high-risk items in test cases. For example, the ISO 26262 standard details the test requirements for automotive functional safety, and the enterprise's internal risk management rules may include additional test requirements for critical functions. For example, tests involving power operation or energy storage devices need to be reviewed to ensure that no unexpected situations occur during the test. Through the above steps, the system can ensure that the generation and review processes of test cases comply with industry standards and enterprise specifications, thereby improving the quality and reliability of test cases and supporting the development team to collaborate and innovate efficiently in a complex system environment.

[0082] Step S402: According to the risk case determination rules, label the risk levels of each test case in the initial test case generation result to obtain a subset of high-risk test cases and a subset of low-risk test cases.

[0083] It should be noted that the risk case determination rules are a set of rules predefined by the enterprise for evaluating the risk levels of test cases. These rules usually include factors such as the coverage, complexity, and associated functions of test cases.

[0084] It can be understood that the subset of high-risk test cases contains those test cases that have a significant impact on functional safety and reliability, while the subset of low-risk test cases contains those test cases with less impact. For example, test cases involving safety functions (such as automatic emergency braking) are usually labeled as high-risk, while test cases involving the infotainment system may be labeled as low-risk.

[0085] It should be understood that the system can give priority to processing high-risk test cases to ensure the test coverage and quality of critical functions, thereby improving test efficiency and development efficiency.

[0086] Step S403: According to the industry-related standard documents, conduct technical execution review and manual review on the high-risk test case set to obtain a test case set after the review is completed.

[0087] It should be noted that technical execution review refers to verifying test cases through automated tools to quickly identify technical issues in test cases, such as syntax errors or non-standard test steps, and ensuring compliance with the technical specifications of industry-related standard documents. Secondly, technical execution review will, to a certain extent, pre-enact the test process to determine whether the test case is technically feasible or verify its compliance with test safety conditions. Manual review is performed by test engineers manually examining test cases. Manual review can discover logical issues that may be overlooked by automated tools or potential problems in actual testing based on technical experience, thereby ensuring the practical feasibility of the generated test cases.

[0088] Step S404: According to the preset test case merging rules, deduplicate and merge the low-risk test case subset and the reviewed test case set to obtain a test case set that complies with the execution specifications.

[0089] It can be understood that the preset test case merging rules refer to a set of rules predefined by an enterprise for merging test cases to ensure the integrity and consistency of the test case set. These rules usually include deduplication, merging similar test cases, ensuring test coverage, etc. The deduplication and merging process can reduce redundant test cases and improve test efficiency. For example, if multiple test cases test the same function point, the system will retain a representative test case and delete other duplicates.

[0090] It should be understood that through the above operations, the system can generate a test case set that complies with the execution specifications, ensuring the comprehensiveness and efficiency of the test cases, and supporting the development team to collaborate and innovate efficiently in a complex system environment.

[0091] Step S405: Perform format normalization processing on the test case set that complies with the execution specifications to obtain the target test case set.

[0092] It can be understood that format normalization processing refers to converting the test case set into an internal enterprise or industry-standard format to ensure the unity and readability of the test cases. The format-normalized test cases include unified naming rules, structured test steps, standardized expected results, etc.

[0093] It should be understood that format normalization processing can improve the maintainability and readability of test cases, facilitating the sharing and use of test cases by the test team among different stages and different tools. For example, unified naming rules can help testers quickly locate specific test cases, and structured test steps can ensure the clarity and consistency of the test process.

[0094] In a feasible implementation manner, step S405 may include steps C11 to C13: Step C11: Obtain the test case format specification according to the test case review guidance document.

[0095] Step C12: Obtain the structured output rules according to the test case format specification.

[0096] Step C13: Perform format conversion processing on the test case set that complies with the execution specification according to the structured output rules to obtain the target test case set.

[0097] It should be noted that the test case format specification defines the structure, naming rules, description methods of test steps, formats of expected results, and other contents. The structured output rules refer to the rules for organizing and presenting test cases in a predefined format and structure, which ensure the consistency and interoperability of test cases among different tools and teams.

[0098] It can be understood that the structured output rules may include naming specifications, field definitions, data types, output formats, etc. of test cases. For example, the output of test cases may need to be presented in JSON or XML format for easy reading and execution by automated test tools.

[0099] It should be understood that format conversion processing refers to the process of converting test cases from one format to another. This usually involves reorganizing and formatting each part of the test case (such as test steps, expected results) according to the structured output rules. Through the above steps, the system can generate a target test case set that complies with the structured output rules, ensuring the format specification and content integrity of the test cases, thereby improving test efficiency and quality, and supporting the development team to carry out efficient collaboration and innovation in a complex system environment.

[0100] In this embodiment, industry-related standard documents and risk case determination rules are obtained through the test case review guidance document; according to the risk case determination rules, risk level labels are assigned to each test case in the initial test case generation result to obtain a subset of high-risk test cases and a subset of low-risk test cases; according to the industry-related standard documents, technical execution review and manual review are performed on the high-risk test case set to obtain a reviewed test case set; according to the preset test case merging rules, the low-risk test case subset and the reviewed test case set are de-duplicated and merged to obtain a test case set that complies with the execution specification; format normalization processing is performed on the test case set that complies with the execution specification to obtain the target test case set.

[0101] In summary, in this embodiment, by deeply integrating the enterprise technology knowledge base with the automated tool chain, the efficiency and accuracy of test case generation are significantly improved. First, the dynamic API interface and the preset extraction rules ensure that the requirements analysis process is always synchronized with the latest technical standards, solving the lag problem caused by traditional manual updates. The unique security desensitization rules and encryption protocols of the solution support multi-domain collaborative development while ensuring the confidentiality of enterprise sensitive data (such as ECU firmware parameters), especially suitable for the efficient collaboration of distributed teams. Second, the construction of the causal chain based on semantic parsing combined with static code analysis can accurately identify resource competition and timing conflicts across functional modules, thereby improving the logic of test case generation. Combined with structured test indication information, it can directly drive the automated test platform, reducing the manual writing error rate and shortening the time for test case generation. While protecting enterprise sensitive data, it supports multi-domain collaborative development, especially suitable for the efficient collaboration of distributed teams. The overall solution realizes the seamless connection from vehicle system requirement changes to test verification, conforms to the development process specifications, and has good economy in actual enterprise applications.

[0102] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the vehicle integration test case generation method of this application. Based on this technical concept, more forms of simple transformations are within the protection scope of this application.

[0103] This application also provides a vehicle integration test case generation device. Please refer to Figure 5 , the vehicle integration test case generation device includes: A function requirement management module 10, configured to determine function requirement change content according to the vehicle function implementation document; A function requirement analysis module 20, configured to obtain test case generation indication information according to the function requirement change content; A test case generation module 30, configured to input the test case generation indication information into a test case generation model to obtain an initial test case generation result; A test case review module 40, configured to review the initial test case generation result according to a test case review guidance document to obtain a target test case set.

[0104] In one embodiment, the function requirement management module 10 is further configured to compare the function implementation document with the function implementation document of the historical version to obtain function document change content; obtain function requirement new items and function requirement change items according to the function document change content; and use the function requirement new items and function requirement change items as the function requirement change content.

[0105] In one embodiment, the functional requirement analysis module 20 is further configured to analyze the functional requirement change content based on the enterprise-level technical knowledge base to obtain the operating conditions and execution steps of each functional requirement; perform technical-level correction on the operating conditions and execution steps of each functional requirement according to the functional specification document to obtain the operating conditions and execution steps of each functional requirement after the correction is completed; and obtain the test case generation indication information corresponding to the functional requirement according to the operating conditions and execution steps after the correction is completed.

[0106] In one embodiment, the functional requirement analysis module 20 is further configured to connect to the enterprise-level technical knowledge base through an encrypted API interface to obtain real-time updated enterprise technical documents; extract the technical support information corresponding to the functional requirement change items from the enterprise technical documents based on a preset information extraction rule, and the extraction process follows the preset security desensitization rule of the enterprise technical documents; perform semantic analysis on the functional requirement change items to obtain the functional description information of the functional requirements; and perform technical logic analysis on the functional description information of the functional requirements based on the technical support information to obtain the operating conditions and execution steps of each functional requirement. Wherein, the functional description information includes the functional domain to which it belongs, the requirement ID, the requirement overview, and the functional expected result, the operating conditions include the preconditions, trigger conditions, and exit conditions, and the execution steps include the operation subject, the behavior action, and the action object.

[0107] In one embodiment, the test case generation module 30 is further configured to determine a test scenario template according to the functional description information in the test case generation indication information, where the test scenario template includes the application scenario, test boundary conditions, and abnormal situations; disassemble the execution steps in the test case generation indication information to obtain structured implementation steps, where the fine granularity of the structured implementation steps is the smallest execution step for a single execution; input the test case generation indication information, the test scenario template, and the structured implementation steps into the test case generation model to obtain an executable automated test script, and use the automated test script as the initial test case generation result.

[0108] In one embodiment, the test case review module 40 is further configured to obtain industry-related standard documents and risk case determination rules according to the test case review guidance document; label the risk levels of each test case in the initial test case generation result according to the risk case determination rules to obtain a high-risk test case subset and a low-risk test case subset; perform technical execution review and manual review on the high-risk test case set according to the industry-related standard documents to obtain a reviewed test case set; perform deduplication and merging on the low-risk test case subset and the reviewed test case set according to the preset test case merging rules to obtain a test case set that complies with the execution specifications; and perform format standardization processing on the test case set that complies with the execution specifications to obtain the target test case set.

[0109] In one embodiment, the test case review module 40 is further configured to obtain the test case format specification according to the test case review guidance document; obtain the structured output rule according to the test case format specification; and perform format conversion processing on the test case set that complies with the execution specifications according to the structured output rule to obtain the target test case set.

[0110] In this embodiment, the changes in functional requirements are identified by comparing the functional implementation documents of historical versions. Based on the enterprise-level technical knowledge base, elements such as functional domains and conditional constraints are extracted to form test case generation indication information. Combined with multi-dimensional technical verification (functional specification correction, semantic analysis, technical logic parsing), structured implementation steps are generated and automatically converted into automated scripts for specific scenarios using a test model; the initial cases are dynamically classified through a risk stratification review mechanism, and a compliance review and deduplication and merging strategy of standard documents are adopted, and finally a test case set that complies with industry specifications is output in a structured format. This solution realizes full-process optimization in the aspects of change tracking, requirement mapping, use case generation and review by constructing a knowledge-driven automated test generation link.

[0111] The vehicle integration test case generation device provided in this application adopts the vehicle integration test case generation method in the above embodiment, and can solve the technical problem of how to efficiently and accurately generate and manage test cases during the vehicle development process to adapt to the frequent changes in functional requirements and ensure the comprehensiveness and reliability of testing. Compared with the prior art, the beneficial effects of the vehicle integration test case generation device provided in this application are the same as those of the vehicle integration test case generation method provided in the above embodiment, and other technical features in the vehicle integration test case generation device are the same as those disclosed in the above embodiment method, and will not be elaborated here.

[0112] The present application provides a vehicle integration test case generation device. The vehicle integration test case generation device includes: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor is enabled to execute the vehicle integration test case generation method in the first embodiment above.

[0113] Reference is made below Figure 6 , which shows a schematic structural diagram of a vehicle integration test case generation device suitable for implementing the embodiments of the present application. The vehicle integration test case generation device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description: tablet computers), PMPs (Portable Media Player: portable multimedia players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The vehicle integration test case generation device shown is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0114] As Figure 6As shown, the vehicle integration test case generation device may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM: Random Access Memory) 1004. In the RAM 1004, various programs and data required for the operation of the vehicle integration test case generation device are also stored. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle integration test case generation device to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a vehicle integration test case generation device having various systems, it should be understood that it is not required to implement or have all the shown systems. More or fewer systems may be implemented or had alternatively.

[0115] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device, or installed from the storage device 1003, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the methods of the embodiments disclosed in the present application are executed.

[0116] The vehicle integration test case generation device provided by this application adopts the vehicle integration test case generation method in the above-mentioned embodiment, and can solve the technical problem of how to efficiently and accurately generate and manage test cases during the vehicle development process to adapt to the frequent changes in functional requirements and ensure the comprehensiveness and reliability of testing. Compared with the prior art, the beneficial effects of the vehicle integration test case generation device provided by this application are the same as those of the vehicle integration test case generation method provided by the above-mentioned embodiment, and other technical features in this vehicle integration test case generation device are the same as the features disclosed in the method of the previous embodiment, and will not be elaborated here.

[0117] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0118] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0119] This application provides a computer-readable storage medium with computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle integration test case generation method in the above-mentioned embodiment.

[0120] The computer-readable storage medium provided by this application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory, optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, device, or component. The program code contained on the computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0121] The above computer-readable storage medium can be included in the vehicle integration test case generation device; it can also exist separately and not be assembled into the vehicle integration test case generation device.

[0122] The above computer-readable storage medium carries one or more programs. When the one or more programs are executed by the vehicle integration test case generation device, the vehicle integration test case generation device is caused to: determine the content of the functional requirement change according to the vehicle function implementation document; obtain the test case generation instruction information according to the content of the functional requirement change; input the test case generation instruction information into the test case generation model to obtain the initial test case generation result; and review the initial test case generation result according to the test case review guidance document to obtain the target test case set.

[0123] Computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, by connecting through an Internet service provider using the Internet).

[0124] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and this module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks can occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0125] The modules described in the embodiments of this application can be implemented in software or in hardware. Among them, the name of the module does not constitute a limitation to the unit itself in some cases.

[0126] The readable storage medium provided by this application is a computer-readable storage medium. The computer-readable storage medium stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle integration test case generation method, and can solve the technical problem of how to efficiently and accurately generate and manage test cases during the vehicle development process to adapt to the frequent changes in functional requirements and ensure the comprehensiveness and reliability of testing. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by this application are the same as those of the vehicle integration test case generation method provided by the above embodiment, and will not be elaborated here.

[0127] The computer program product provided by this application can solve the technical problem of vehicle integration test case generation. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as those of the vehicle integration test case generation method provided by the above embodiment, and will not be elaborated here.

[0128] The above are only some embodiments of this application, and do not limit the patent scope of this application accordingly. Any equivalent structural transformation made by using the content of the specification and drawings of this application under the technical concept of this application, or direct / indirect application in other related technical fields, is included in the patent protection scope of this application.

Claims

1. A method for generating vehicle integration test cases, characterized in that The method for generating vehicle integration test cases includes: Determine the content of functional requirement changes according to the vehicle functional implementation document; Obtain test case generation instruction information according to the content of the functional requirement changes; Input the test case generation instruction information into a test case generation model to obtain an initial test case generation result; Review the initial test case generation result according to the test case review guidance document to obtain a target test case set.

2. The method for generating an integrated vehicle test case according to claim 1, wherein The step of determining the content of functional requirement changes according to the vehicle functional implementation document includes: Compare the functional implementation document with the functional implementation document of the historical version to obtain the content of the functional document changes; Obtain the newly added items of functional requirements and the changed items of functional requirements according to the content of the functional document changes; Use the newly added items of functional requirements and the changed items of functional requirements as the content of the functional requirement changes.

3. The method for generating an integrated vehicle test case according to claim 1, wherein The step of obtaining test case generation instruction information according to the content of the functional requirement changes includes: Based on the enterprise-level technical knowledge base, analyze the content of the functional requirement changes to obtain the operating conditions and execution steps of each functional requirement; According to the functional specification document, perform technical-level corrections on the operating conditions and execution steps of each functional requirement to obtain the operating conditions and execution steps of each functional requirement after the correction is completed; Obtain the test case generation instruction information corresponding to the functional requirement according to the operating conditions and execution steps after the correction is completed.

4. The method for generating an integrated vehicle test case according to claim 3, wherein The step of analyzing the functional requirement change items based on the enterprise-level technical knowledge base to obtain the operating conditions and execution steps of each functional requirement includes: Connect to the enterprise-level technical knowledge base through an encrypted API interface to obtain real-time updated enterprise technical documents; Based on a preset information extraction rule, extract the technical support information corresponding to the functional requirement change items from the enterprise technical documents, and the extraction process follows the preset security desensitization rule of the enterprise technical documents; Perform semantic analysis on the functional requirement change items to obtain the functional description information of the functional requirements; Based on the technical support information, perform technical logic analysis on the functional description information of the functional requirements to obtain the operating conditions and execution steps of each functional requirement; Among them, the functional description information includes the functional domain to which it belongs, the requirement ID, the requirement overview, and the functional expected result, the operating conditions include the precondition, the trigger condition, and the exit condition, and the execution steps include the operation subject, the action, and the object of action.

5. The method for generating an integrated vehicle test case according to claim 1, wherein The step of inputting the test case generation instruction information into a test case generation model to obtain an initial test case generation result includes: Determine a test scenario template according to the functional description information in the test case generation instruction information, and the test scenario template includes the application scenario, the test boundary conditions, and the abnormal conditions; Decompose the execution steps in the test case generation instruction information to obtain structured implementation steps, where the fine granularity of the structured implementation steps is the smallest execution step for a single execution; Input the test case generation indication information, the test scenario template, and the structured implementation steps into the test case generation model to obtain an executable automated test script, and use the automated test script as the initial test case generation result.

6. The method for generating an integrated vehicle test case according to claim 1, wherein Review the initial test case generation result according to the test case review guidance document to obtain a target test case set, including: Obtain industry-related standard documents and risk case determination rules according to the test case review guidance document; According to the risk case determination rules, label the risk levels of each test case in the initial test case generation result to obtain a subset of high-risk test cases and a subset of low-risk test cases; According to the industry-related standard documents, conduct technical execution review and manual review on the high-risk test case set to obtain a reviewed test case set; According to the preset test case merging rules, perform deduplication and merging on the subset of low-risk test cases and the reviewed test case set to obtain a test case set that complies with the execution specifications; Perform format normalization processing on the test case set that complies with the execution specifications to obtain the target test case set.

7. The method for generating the vehicle integration test cases according to claim 6, wherein The performing format normalization processing on the test case set that complies with the execution specifications to obtain the target test case set includes: Obtain the test case format specification according to the test case review guidance document; Obtain the structured output rule according to the test case format specification; According to the structured output rule, perform format conversion processing on the test case set that complies with the execution specifications to obtain the target test case set.

8. An integrated vehicle test case generation device, characterized in that, The vehicle integration test case generation device includes: A function requirement management module for determining function requirement change content according to the vehicle function implementation document; A function requirement analysis module for obtaining test case generation indication information according to the function requirement change content; A test case generation module for inputting the test case generation indication information into the test case generation model to obtain an initial test case generation result; A test case review module for reviewing the initial test case generation result according to the test case review guidance document to obtain a target test case set.

9. An integrated vehicle test case generation device, characterized in that The vehicle integration test case generation device includes: a memory, a processor, and a vehicle integration test case generation program stored on the memory and executable on the processor. The vehicle integration test case generation program is configured to implement the steps of the vehicle integration test case generation method according to any one of claims 1 to 7.

10. A storage medium, characterized in that, The vehicle integration test case generation program is stored on a storage medium. When the vehicle integration test case generation program is executed by a processor, it implements the steps of the vehicle integration test case generation method according to any one of claims 1 to 7.

Images