Vehicle embedded software automatic test management system

Abstract

The invention relates to the technical field of computers, and discloses a vehicle embedded software automatic test management system, which is characterized in that an automatic test management module in the system calls a continuous integration continuous test module according to an acquired test task; and the continuous integration and continuous test module pulls target test assets in the preset warehouse, deploys the target test assets to the test asset module, calls the test asset module, deploys the target test assets in the test asset module to corresponding target test resources, executes a test task, stores a test product result of the test task to a preset product library, and stores the test product result in the preset product library. According to the vehicle embedded software testing system, centralized management of testing assets, testing resources, testing data, testing products and testing processes is achieved, unified management can be achieved, testing resource deployment of multiple testing items is supported, testing of multiple pieces of vehicle embedded software is achieved, and the testing efficiency is improved. The development cost and the maintenance cost are reduced, and the operation is more convenient.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to an automated test management system for vehicle embedded software. Background Art

[0002] In related technologies, there are various management systems serving testing, such as systems for task management and test asset management, systems for separately managing test assets, test project and task management systems, and management systems that combine test processes and assets, management systems focusing on test resources, and systems for separately managing test products. When performing specific test management based on these management systems serving testing, in order to obtain test assets, test resources, test data, test products, and test processes, it is often necessary to separately obtain scattered content, and this content is often not interoperable, thereby making it difficult to achieve unified management for testing.

[0003] In the field of development of automotive embedded controller nodes, due to differences in customer requirements, it is difficult to achieve unified management of assets and resources. Some basic characteristics of the embedded software under test, such as software kernels, flashing methods, software features, etc., are difficult to be consistent. It is difficult to achieve unified deployment of test resources for different projects. When multiple systems are used for collaborative deployment management, corresponding secondary development and subsequent maintenance need to be carried out for different test projects, resulting in high costs and poor convenience. Summary of the Invention

[0004] The present invention provides an automated test management system for vehicle embedded software to solve the technical problems in related technologies that it is difficult to achieve unified deployment of test resources for different projects, and multiple systems need to be used for collaborative deployment management, which may require corresponding secondary development and subsequent maintenance for different test projects, resulting in high costs and poor convenience.

[0005] An embodiment of the present invention provides a vehicle embedded software automated test management system. The vehicle embedded software automated test management system includes an automated test management module, a continuous integration and continuous testing module, a test asset module, and a test resource module, where: The automated test management module is configured to call the continuous integration and continuous testing module to execute the test task according to the obtained test task, and the test task is a task for automatically testing vehicle embedded software; The continuous integration and continuous testing module is configured to pull target test assets from a preset repository and deploy the target test assets to the test asset module, and the target test assets are test assets corresponding to the test task; The continuous integration and continuous testing module is further configured to call the test asset module to deploy the target test assets in the test asset module on the target test resources corresponding to the test task in the test resource module to execute the test task; The continuous integration and continuous testing module is further configured to store the test product results of the test task in a preset artifact repository; The automated test management module is further configured to obtain the test product results in the preset artifact repository and to display and review the test product results.

[0006] In an embodiment of the present invention, the automated test management module is further configured to determine the automatic determination case execution status of the test case according to the test product results. If the automatic determination case execution status is the target status, a prompt message is generated and displayed based on the target status for a first target user to determine the manual review confirmation case execution status based on the prompt message. If the manual review confirmation case execution status is case failure, the automated test management module is triggered to create a basic defect form for a second target user to add a defect description based on the basic defect form to obtain defect data and complete the creation of the defect form; If the manual review confirmation case execution status is case success and the prompt message is a defect closure prompt, when the defect of the test case has been repaired and meets the preset conditions for closing the defect problem of the test case, it is confirmed that the defect needs to be closed, and the automated test management module is triggered to pull the basic defect form of the test case for the second target user to add a defect description based on the basic defect form to complete the creation of the defect form. After the process confirmation is completed, the defect of the test case is closed; Wherein, if the target status is case failure, the prompt message is a defect creation prompt message; If the target status is case success, and the historical test result of the test case is test failure, the test case has an associated defect item, and the test case is in a pending verification state, the prompt message is a defect closure prompt.

[0007] In an embodiment of the present invention, the automated test management module creates a basic defect form as follows: The automated test management module obtains relevant basic information of the test task to determine pre-filled information, and fills the pre-filled information into a preset form to obtain the basic defect form.

[0008] In an embodiment of the present invention, the automated test management module is communicatively connected to the defect management module; the defect management module is used to store the defect data; the automated test management module is further used for at least one of the following: obtaining a defect data acquisition instruction, the defect data acquisition instruction including an identifier of the defect data to be acquired, acquiring the corresponding defect data to be acquired from the defect management module based on the identifier of the defect data to be acquired, and storing the defect data to be acquired in a preset storage space; obtaining a defect data display instruction, the defect data display instruction including an identifier of the defect data to be displayed, and displaying the defect data to be displayed stored in the preset storage space of the automated test management module based on the identifier of the defect data to be displayed.

[0009] In an embodiment of the present invention, the automated test management module includes a data dashboard sub-module, and the data dashboard sub-module is used to generate dashboard data based on at least one of the test assets, test product results, defect data, and test requirements according to preset data rules, and display the dashboard data through the automated test management module.

[0010] In an embodiment of the present invention, before the automated test management module calls the continuous integration and continuous testing module to execute the test task according to the obtained test task, the automated test management module is configured to: distribute the input test task items to the corresponding test personnel user interfaces, the test task items including one or more test tasks, and the automated test management module including one or more test personnel user interfaces; display the received test tasks through the test personnel user interfaces, and confirm the received test task form through the test personnel user interfaces, or modify the received test task form through the test personnel user interfaces and confirm the modified test task form, the test task form being generated based on the test task; make a test reservation based on the confirmed test task form, the confirmed test task form at least including the test task and the reserved test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the test task at the reserved test time.

[0011] In an embodiment of the present invention, the automated test management module displays and reviews the test product results, including: displaying the test product results through the tester user interface and receiving the first review result of the first review of the test product results input by the tester user interface; if the first review result is passed, submitting the test product results to the task recycling sub-module of the automated test management module; the task recycling sub-module transfers the test product results to the test management staff user interface, receives the delivery review instruction input by the test management staff user interface, and transmits the test product results to the delivery review user interface for display; the delivery review user interface receives the second review result of the second review of the test product results, if the second review result is passed, the test product results are delivered for the project, if the second review result is not passed, generating a task re-optimization message and transmitting it to the test management staff user interface; the test management staff user interface receives the corrected test task items generated based on the task re-optimization message, the corrected test task items include the test tasks to be modified and / or the test tasks to be retested, and uses the corrected test task items as the newly input test task items, repeating the repeated test steps until the newly obtained second review result is passed, and triggering the call of the continuous integration and continuous testing module to execute the corrected test task; wherein, the automated test management module further includes the task recycling sub-module, the test management staff user interface and the delivery review user interface; the repeated test steps include: distributing the newly input test task items to the corresponding tester user interface, the newly input test task items include one or more new test tasks; displaying the received new test tasks through the tester user interface and confirming the received new test task form through the tester user interface, or modifying the received new test task form through the tester user interface and confirming the newly modified test task form, the new test task form is generated based on the new test task; making a test reservation based on the newly confirmed test task form, the newly confirmed test task form at least includes the new test task and the newly reserved test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the new test task at the newly reserved test time; the continuous integration and continuous testing module pulls the new target test assets in the preset repository and deploys the new target test assets to the test asset module, the new target test assets are the test assets corresponding to the new test tasks; the continuous integration and continuous testing module calls the test asset module to deploy the new target test assets in the test asset module on the new target test resources corresponding to the new test tasks in the test resource module to execute the new test task;The continuous integration and continuous testing module stores the new test product results of the new test tasks into the preset artifact repository; the automated test management module obtains the new test product results in the preset artifact repository; displays the new test product results through the tester user interface, and receives the new first review result of the first review of the new test product results input through the tester user interface; if the new first review result is passed, submits the new test product results to the task recycling sub-module of the automated test management module; the task recycling sub-module transfers the new test product results to the test manager user interface, receives the new delivery review instruction input through the test manager user interface, and transmits and displays the new test product results to the delivery review user interface; the delivery review user interface receives the new second review result of the second review of the new test product results.

[0012] In an embodiment of the present invention, the continuous integration and continuous testing module deploys a plurality of preset pipelines that have completed modular integration, and the preset pipelines are used to perform at least one of continuous integration, continuous deployment, and continuous testing.

[0013] In an embodiment of the present invention, the vehicle embedded software automated test management system is further configured with an artificial intelligence data interface for the artificial intelligence system to obtain artificial intelligence requirement data through the artificial intelligence data interface, and process the artificial intelligence requirement data through the artificial intelligence system to obtain artificial intelligence processing results, and the artificial intelligence requirement data includes at least one of the test assets, test product results, defect data, and test requirements.

[0014] In an embodiment of the present invention, the automated test management module is further configured to: input a baseline release process item through the test manager user interface, and the baseline release process item includes a baseline identifier and the content of the asset to be marked; transfer the baseline release process item to the corresponding tester user interface according to the content of the asset to be marked to prompt for test asset sorting; the tester user interface receives the sorted test assets input, stores the sorted test assets into the preset repository, and performs confirmation of the baseline to be marked and the content of the asset to be marked through the tester user interface, and performs one-key confirmation marking; after the test manager user interface receives the one-key confirmation marking completion messages feedback by all tester user interfaces, completes the baseline marking; wherein, the automated test management module includes the tester user interface and the test manager user interface.

[0015] In an embodiment of the present invention, the automated test management module further includes a test management personnel user interface, a system management personnel user interface, and a tester user interface; the test management personnel user interface is used to input the basic project information of a project and transmit the basic project information to the system management personnel user interface; the system management personnel user interface is used to create a project space according to the basic project information and allocate the management authority of the project space to the test management personnel account; when the test management personnel account of the test management personnel user interface is in a logged-in state, the test management personnel user interface is used to input at least one of the sorted project assets, sorted project resources, and sorted project software features; the test management personnel user interface is further used to define the project modules of the project and the system function allocation of the project member accounts; when the test management personnel user interface is used to input the sorted project software features, the test management personnel user interface is further used to configure the software refresh method and configure the preset pipeline of the project; when the project member account of the tester user interface is in a logged-in state, the tester user interface is used to initiate a test reservation for the project in response to a test reservation instruction.

[0016] In the solution implemented by the vehicle embedded software automated test management system provided above, the automated test management module in the system calls the continuous integration and continuous testing module according to the obtained test task. The continuous integration and continuous testing module pulls the target test assets in the preset repository, deploys the target test assets to the test asset module, and calls the test asset module to deploy the target test assets in the test asset module on the target test resources corresponding to the test task in the test resource module to execute the test task. The test product results of the test task are stored in the preset artifact repository. The test product results in the preset artifact repository are obtained through the automated test management module, and the test product results are displayed and audited. The system realizes the integration of the continuous integration and continuous testing module, test assets, and test resources, and can also associate the preset repository with the preset artifact repository, thereby realizing the centralized management of test assets, test resources, test data, test products, and test processes, enabling unified management of test management. The system can also support the deployment of test resources for multiple test projects to implement automated testing of multiple vehicle embedded software, reducing development costs and maintenance costs, and being more convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required to be used in the description of the embodiments of the present invention. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0018] Figure 1 A schematic diagram showing an exemplary system architecture to which the technical solutions in one or more embodiments of the present application can be applied;

[0019] Figure 2 A schematic structural diagram of a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0020] Figure 3 A schematic flowchart of creating and closing a defect process executed by a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0021] Figure 4 An exemplary schematic diagram of a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0022] Figure 5 A schematic flowchart of a task flow process of a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0023] Figure 6 A schematic flowchart of a baseline management process of a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0024] Figure 7 A schematic flowchart of a configuration process of project asset deployment of a vehicle embedded software automated test management system provided by an embodiment of the present invention;

[0025] Figure 8 A schematic flowchart of a test execution and test development process of a vehicle embedded software automated test management system provided by an embodiment of the present invention. Detailed implementation manners

[0026] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without making creative efforts fall within the protection scope of the present invention.

[0027] Figure 1 A schematic diagram showing an exemplary system architecture to which the technical solutions in one or more embodiments of the present application can be applied. As Figure 1As shown, the system architecture 100 may include a terminal device 110, a network 120, and a server 130. The terminal device 110 may include various electronic devices such as a smart phone, a tablet computer, a laptop computer, and a desktop computer. The server 130 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The network 120 may be a communication medium of various connection types that can provide a communication link between the terminal device 110 and the server 130, such as a wired communication link or a wireless communication link.

[0028] According to the implementation requirements, the system architecture in the embodiment of the present application can have any number of terminal devices, networks and servers. For example, the server 130 can be a server group composed of multiple server devices. In addition, the technical solution provided in the embodiment of the present application can be applied to the terminal device 110, can also be applied to the server 130, or can be implemented by the terminal device 110 and the server 130 together, and the present application does not make any special restrictions on this.

[0029] The inventors found that there are many management systems serving testing in the related art, such as systems for task management and test asset management, systems for managing test assets alone, test project and task management systems, and management systems combining test processes and assets, management systems that focus on test resources, and systems that manage test products alone. When performing specific test management, in order to obtain test assets, test resources, test data, test products, and test processes, it is often necessary to obtain scattered content separately, and these contents are often not interoperable, making it difficult to unify the management of testing. There is no system in the related art that can manage both technical assets and physical resources, both test project management and test execution, both internal automated test execution and external product delivery, both management data and product maintenance, both test process and test process management.

[0030] In addition, due to the differences in customer needs, it is difficult to unify the management of assets and resources in the current development of automotive embedded controller nodes, including some basic characteristics of the embedded software under test, such as software kernel, refresh mode, software characteristics, etc., which makes it difficult to achieve consistency, resulting in the difficulty of unifying the deployment of test resources for different projects. Therefore, the scalability is poor when deploying and managing the same system. The relevant technology does not provide a system that can well accommodate the management and operation of assets of multiple products and different types of projects.

[0031] In addition, the test development and management of future automotive embedded software will inevitably integrate artificial intelligence elements. However, it is very difficult to achieve an ideal integration of AI tools in a scattered and non-unified asset and data environment. There is no system that can include all the above-mentioned content items while considering the later integration with artificial intelligence, paving the way for AI service testing. There is no reference example in this regard in the industry.

[0032] Therefore, there are multiple technical problems that are difficult to overcome in achieving centralized management of test assets, test resources, test data, test products, and test processes, as well as compatible deployment of multiple projects.

[0033] Based on the disadvantages of the automotive embedded controller software automated test management system in the related technologies mentioned above, the embodiments of this application provide an integrated test resource and test asset, combined with a continuous integration and continuous testing system, and provide corresponding functions through a user interface to solve the above problems.

[0034] In an embodiment of this application, the terminal device 110 or the server 130 of this application can be deployed with the vehicle embedded software automated test management system alone or in cooperation. For example, the vehicle embedded software automated test management system can be deployed in the server and the terminal device. Except for the user interface part of the automated test management module, the continuous integration and continuous testing module, the test asset module, and the test resource module are deployed in the server, and the relevant user interface in the automated test management module is deployed in the terminal device. Then, relevant users can input, view, and input call instructions for relevant data through the relevant user interface of the terminal device. Through the vehicle embedded software automated test management system, the integration of the continuous integration and continuous testing system, test assets, and test resources is achieved, and the preset repository for storing test assets and the preset artifact library for storing test product results can also be associated, thereby realizing centralized management of test assets, test resources, test data, test products, and test processes, enabling unified management of test management. Through this vehicle embedded software automated test management system, the test resource deployment of multiple test projects can be carried out to automate the testing of multiple vehicle embedded software, eliminating the need to develop and maintain a test system for each test project separately, reducing costs and being more convenient.

[0035] The above part introduced the content of the exemplary system architecture applying the technical solution of this application. Next, continue to introduce the vehicle embedded software automated test management system of this application. The solution provided by the present invention will be described in detail through specific embodiments below.

[0036] Please refer to Figure 2 as shown Figure 2FIG. 0 is a schematic structural diagram of a vehicle embedded software automated test management system provided by an embodiment of the present invention. The vehicle embedded software automated test management system 200 includes an automated test management module 210, a continuous integration and continuous testing module 220, a test asset module 230, and a test resource module 240, where: The automated test management module 210 is configured to call the continuous integration and continuous testing module 220 to execute a test task according to the obtained test task, and the test task is a task for automatically testing vehicle embedded software; The continuous integration and continuous testing module 220 is configured to pull the target test assets in the preset repository 250 and deploy the target test assets to the test asset module 230, and the target test assets are test assets corresponding to the test task; The continuous integration and continuous testing module 220 is further configured to call the test asset module 230 to deploy the target test assets in the test asset module 230 on the target test resources corresponding to the test task in the test resource module 240 to execute the test task; The continuous integration and continuous testing module 220 is further configured to store the test product results of the test task in the preset artifact repository 260; The automated test management module 210 is further configured to obtain the test product results in the preset artifact repository 260, and to display and review the test product results.

[0037] As an example, the test task obtained by the automated test management module may be a pre-set test task, which is used as the current test task to be executed after certain review, reservation, etc. The generation method of the test task may be input from outside the vehicle embedded software automated test management system, or generated by the vehicle embedded software automated test management system.

[0038] The preset repository may be a cloud repository or other preset local repositories, which pre-store relevant test assets to assist in the execution of the test task. All test asset contents are stored in the preset repository. The test assets in the preset repository can be pulled by the continuous integration and continuous testing module and deployed to the test resource module, or directly associated with the user interface of the automated test management module to enable users to view the test assets. The test assets here include, but are not limited to, at least one of software layer resources such as test cases, test scripts, test projects, and test data traceability relationships.

[0039] Since the preset repository may store test assets supporting multiple test tasks, when executing this test task, the test assets supporting the execution of this test task can be called as target test assets in a manner known to those skilled in the art.

[0040] The test asset module within the vehicle embedded software automated test management system may not have previously deployed the target test asset. By pulling the corresponding target test asset from a preset repository after obtaining the test task to be executed, the vehicle embedded software automated test management system can be equipped with the test asset for testing this test task. This allows the test assets for different projects to be deployed in the same vehicle embedded software automated test management system without the need for separate corresponding system development. As an example, before executing a new test project, the relevant test assets can be prepared in advance and stored in the preset repository to support the testing of the test tasks corresponding to this new test project.

[0041] The test resource module includes physical devices that support the hardware for various test tasks. Appropriate physical devices can be selected as the target test resources according to the needs of the test tasks, and the test tasks are executed after the target test assets are deployed on the target test resources.

[0042] The preset artifact repository can be a cloud-based artifact repository, a local artifact repository, or a combination of both, which can be specifically selected according to the needs of those skilled in the art. The preset artifact repository is used to store the test product results executed by the test resources. The test product results in this preset artifact repository are managed and stored by the continuous integration and continuous testing module, and can also be directly associated with the user interface of the automated test management module to enable users to view the test product results and subsequent reviews. The test product results here include but are not limited to at least one of test reports, test data, etc.

[0043] In one embodiment, the continuous integration and continuous testing module deploys multiple preset pipelines that have completed modular integration. The preset pipelines are used to execute at least one of continuous integration (CI, Continuous Integration), continuous deployment (CD, Continuous Deployment), and continuous testing (CT, Continous Test).

[0044] As an example, the preset pipeline can be created according to the preset configuration data of the project, which includes at least one of, but is not limited to, the verification level, verification scope, refresh method, etc. In this way, when a new project needs to be added, that is, when there may be new vehicle embedded software (or perhaps a new version of the software) that needs to be tested, the preset configuration data can be obtained based on the relevant data of the project for pre-configuration and the creation of the preset pipeline, enabling the system to execute the test of the new project. This enables the system to support the testing of different vehicle embedded software. When users need to conduct tests on new projects, they no longer need to separately develop and maintain secondary items such as continuous integration and continuous testing systems, test assets, and test resources. Instead, on the basis of this system, corresponding preset pipelines can be added to achieve this, which can effectively reduce the development and maintenance costs and is more convenient. The creation of modular preset pipelines is relatively less difficult, which can also effectively lower the usage threshold of this system, making it easier to use and reducing the technical requirements for users.

[0045] Multiple CX Pipelines (preset pipelines, such as CIPipeline, CD Pipeline, CT Pipeline, etc.) are deployed within the continuous integration and continuous testing system to implement various necessary functions of this system. The continuous integration and continuous testing module can call test assets and deploy the test assets on the specified test resources for specific test execution. The continuous integration and continuous testing module has rich, cross-project applicable, and decoupled CX Pipelines, which can achieve the system deployment of different projects, enabling the continuous integration and continuous testing module of the system to handle diverse project automated tests. At the same time, it supports the extended deployment of CX Pipelines and can continuously expand the automated service functions. In addition, the CX Pipelines within the continuous integration and continuous testing module have completed modular integration, without requiring users to have professional knowledge. It supports the front-end configuration and deployment of users, enabling rapid deployment and convenient application. At the same time, the configured CX Pipelines can be directly associated with projects for project application.

[0046] In one embodiment, the automated test management module is further configured to determine the execution status of the test case automatically determined by the test case based on the test product result. If the automatically determined execution status of the test case is the target status, a prompt message is generated and displayed based on the target status for the first target user to determine the execution status of the test case manually reviewed and confirmed based on the prompt message. If the execution status of the test case manually reviewed and confirmed is a test case failure, the automated test management module is triggered to create a basic defect form for the second target user to add a defect description based on the basic defect form to obtain defect data and complete the creation of the defect form. If the execution status of the test case manually reviewed and confirmed is a test case success and the prompt message is a defect closure prompt, when the defect of the test case has been repaired and the preset condition for closing the defect problem of the test case is met, it is confirmed that the defect needs to be closed, and the automated test management module is triggered to pull the basic defect form of the test case for the second target user to add a defect description based on the basic defect form to complete the creation of the defect form. After the process confirmation is completed, the defect of the test case is closed. Among them, if the target status is a test case failure, the prompt message is a defect creation prompt message. If the target status is a test case success, the historical test result of the test case is a test failure, the test case has an associated defect item, and the test case is in a pending verification state, the prompt message is a defect closure prompt.

[0047] It can be understood that taking the first target user and the second target user as testers as an example, first, an automated judgment is made on the test product result to obtain the execution status of the automated judgment test case. If the execution status of the automated judgment test case is test success (the test case is successful and the test result is test success), then it is necessary to query whether the historical test result (the previous test product result) of this test case is test failure. If the previous test result of this test case is test failure, then it is necessary to query whether there are any defect items that have been completed and associated with this test case. If there are associated defect items for this test case and this test case is in a pending verification state, then the generated prompt message is a defect closure prompt, which is displayed on the tester's user interface, and the tester is prompted to manually review and confirm the execution status of this test case. If the manually reviewed and confirmed execution status of the test case is case success, then it is judged whether the defect of this test case has been repaired, meeting the preset conditions for closing the defect problem of this test case. If the defect of the test case has been repaired, meeting the preset conditions for closing the defect problem of the test case, then it is confirmed that the defect needs to be closed, and the basic defect form created before for this test case is pulled. Then the tester adds relevant descriptions (such as the reasons for closing the defect, etc.) to complete the creation of the defect form for this test case. After the subsequent process confirmation is completed, the defect of this test case is closed, and the testing of this test case is completed. If the execution status of the automated judgment test case is test failure (the test case fails), then the prompt message is a defect creation prompt message. After the manually reviewed and confirmed execution status of the test case is case failure after manual review, a basic defect form will be created. Then the tester adds a defect description (such as the reason for the defect occurrence, etc.) based on this basic defect form to obtain defect data and complete the creation of the defect form for this test case.

[0048] The purpose of manual review and confirmation is to solve the problem that once the execution result of a test case fails or was previously failed but is now successful, in addition to the possibility that there may indeed be defects in the software under test or the defects have indeed been repaired, there will inevitably be other reasons. For example, the test script used to verify the test case may have problems, or there may be problems with the current test environment (test resources). This is inevitable in actual testing. Therefore, after the automated determination is completed, in order to ensure the reliability of defect closure or creation, it is necessary to have manual review and control, and the reviewers are generally testers.

[0049] The defect description can be a description obtained by the tester through analyzing the test report and detailed test data to get the detailed reasons for the success or failure of this test case.

[0050] The first target user and the second target user can be the same user or different users, which can be set according to the needs of those skilled in the art here.

[0051] Continuing from the above embodiments, the automated test management module creates a basic defect form as follows: The automated test management module obtains relevant basic information of the test task to determine pre-filled information, and fills the pre-filled information into a preset form to obtain a basic defect form. The relevant basic information includes, but is not limited to, the configured project information and the test reservation information for the current test execution, etc. Please refer to Figure 3 , Figure 3 FIG. is a schematic flowchart of the creation and closing of the defect process executed by the vehicle embedded software automated test management system provided by the embodiment of the present invention. As Figure 3 shown, after each test execution process is completed, the test result data (test product result) is parsed to obtain the result status of each test case and the defect status (automatically determine the execution status of the use case). For a single test case, if the use case is executed successfully (a manifestation form of the target state), it will further check whether there is an associated defect in this test case (that is, determine whether the use case has a defect). If there is no defect (no), all processes of this test case will be directly skipped and the process will end. If there is a defect (yes), the system will further confirm whether this defect is in the to-be-verified state. If it is in the to-be-verified state (that is, another manifestation form of the target state), the system will display a defect closing prompt through the user interface, otherwise the subsequent processes of this use case will be skipped. That is, if it is not in the to-be-verified state, the process will end. The above process can be automatically executed by the automated test management module.

[0052] Corresponding to the above situation, if the use case is not executed successfully, it means that there may be potential defects in this use case, and the system will display a defect creation prompt (display a defect creation prompt message) through the corresponding user interface of the automated test management module.

[0053] When the user (the first target user) obtains a defect closing prompt or a defect creation prompt, in the user interface, view the test execution data and test report results of the corresponding use case according to the test case marked by the defect prompt. It should be noted that both the test execution data and the test report results here can be quickly and conveniently obtained through the user interface. The tester analyzes the test report and detailed test data to obtain the detailed reasons for the success or failure of this test case, and combines the analysis details with the use case results to obtain the manually reviewed and confirmed use case execution status. If the current test case is a successful use case, determine whether it is necessary to close the defect. If it is necessary to close the defect, based on the user's request, the system will automatically pull the basic defect form, the user adds a reason description, and completes the process confirmation to close the existing defect; otherwise, if it is analyzed that there is no need to close the defect, it will be directly ignored.

[0054] For the above situation, if the use case execution is unsuccessful, the tester determines whether a defect needs to be created based on the previously analyzed reasons. If a defect needs to be created, based on the user's request, the automated test management module will automatically create a basic defect form and pre-fill all necessary content based on the configured project information and the test reservation information for this test execution. Based on the pre-filled basic defect form for testing, the user (the second target user) adds a problem description and adjusts necessary defect content information in the current form item, and automatically creates a defect after completing the process confirmation; otherwise, if it is analyzed that no defect needs to be created, it is directly ignored.

[0055] It should be noted that the basic defect form generated by the above defect creation process, since it originates from the test execution task and is traceable to the result product of the current test execution task, the defect data related to this defect will also be synchronously attached in the generated defect creation form, including test reports, test data, software target files, etc., so that developers can quickly obtain the original defect data information, troubleshoot the problem cause, and quickly locate the software defect cause.

[0056] In the above defect creation process, after the defect creation process is completed, the created basic defect form will flow into the defect management module synchronously to realize the storage and management of all defect data. Since the user interfaces of the defect management module and the automated test management module are associated, the user can also directly view the current defect data information in the user interface of this system.

[0057] In one embodiment, continue to refer to Figure 2 , the automated test management module 210 is communicatively connected to the defect management module 270; the defect management module 270 is used to store defect data; the automated test management module 210 is further used for at least one of the following: obtaining a defect data acquisition instruction, the defect data acquisition instruction includes an identifier of the defect data to be acquired, obtaining the corresponding defect data to be acquired from the defect management module 270 based on the identifier of the defect data to be acquired, and storing the defect data to be acquired in a preset storage space; obtaining a defect data display instruction, the defect data display instruction includes an identifier of the defect data to be displayed, and displaying the defect data to be displayed stored in the preset storage space of the automated test management module 210 based on the identifier of the defect data to be displayed.

[0058] Among them, the preset storage space can be set in the automated test management module, or can be set in the test asset module, or other storage spaces in the vehicle embedded software automated test management system set by those skilled in the art.

[0059] As an example, the test product results in the preset product library are calculated and processed by the automated test management module to interact with the defect management module. According to the current test results, quick and convenient defect creation or defect closure is achieved, and the data is synchronized to the defect management module. The aforementioned defect management module is used to manage all test defect data, and this defect management module can be directly associated with the user interface to enable users to conveniently view test defects. In addition, the defect management module undertakes the aforementioned defect processes, including the defect creation process and the defect closure process. The defect data of all processes can be summarized in the defect management module, and data synchronization from the defect management module to the user interface of the automated test management module can be achieved. As an example, the association between the user interface of this automated test management module and the defect management module is not a simple content jump, but the synchronization and mapping of the data content of the defect management module. Thus, the vehicle embedded software automated test management system can possess all the asset data content of the defect management system. In one embodiment, there may be other data stored in the defect management module. When viewing defect data, only the data related to the defect data can be viewed.

[0060] In one embodiment, the automated test management module includes a data dashboard sub-module. The data dashboard sub-module is used to generate dashboard data based on at least one of test assets, test product results, defect data, and test requirements according to preset data rules, and display the dashboard data through the automated test management module.

[0061] The data dashboard function summarizes information such as test assets (test cases, test scripts, test data), test requirements, test defects, and test results, and forms dashboard information (dashboard data) based on the data rules (preset data rules) defined by those skilled in the art for users to obtain and view the data information within the system related to testers, so as to assist users in gaining insights into the asset status and quickly obtaining the data information they are concerned about. The dashboard data can be displayed through the relevant user interface of the automated test management module.

[0062] Please refer to Figure 4 , Figure 4 which is an exemplary schematic diagram of the vehicle embedded software automated test management system provided by the embodiment of the present invention. Taking the preset warehouse as the cloud warehouse and the preset product library as the cloud product library as an example, as Figure 4As shown in the figure, the vehicle embedded software automated test management system integrates an automated test management module, a continuous integration and continuous testing module, a test asset module, and a test resource module, and at the same time associates necessary peripheral systems, including a cloud repository, a cloud artifact repository, and a defect management module. All functions and services are provided to users through the user interface of the automated test management module, and various functional services defined by this system are realized through the interaction of multiple other system modules. The user interface of the automated test management module can call the continuous integration and continuous testing module downward. In addition, the user interface can directly synchronize and associate with the cloud repository, the cloud artifact repository, and the defect management module to realize data interaction among multiple systems. Based on the above module relationships and technical links, users of different roles can obtain various functions through the user interface, including task flow, test execution and test development, baseline process of the management system, convenient creation and closing of the defect process, configuration of platform project asset deployment, review of test assets, etc.

[0063] In one embodiment, before the automated test management module calls the continuous integration and continuous testing module to execute a test task according to the obtained test task, the automated test management module is configured to: distribute the input test task items to the corresponding tester user interfaces, where the test task items include one or more test tasks, and the automated test management module includes one or more tester user interfaces; display the received test tasks through the tester user interfaces, and confirm the received test task form through the tester user interfaces, or modify the received test task form through the tester user interfaces and confirm the modified test task form, where the test task form is generated based on the test task; make a test reservation based on the confirmed test task form, and the confirmed test task form includes at least the test task and the reserved test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the test task at the reserved test time.

[0064] It is possible that a test task item includes one or more test tasks, and these test tasks need to be completed by one or more testers. Then, the test tasks need to be assigned to the user interfaces of the corresponding testers so that they can view and execute the test tasks.

[0065] In one embodiment, the automated test management module presents and reviews the test product results, including: presenting the test product results through the tester user interface and receiving the first review result of the first review of the test product results input through the tester user interface; if the first review result is passed, submitting the test product results to the task recovery sub-module of the automated test management module; the task recovery sub-module transfers the test product results to the tester management user interface, receives the delivery review instruction input through the tester management user interface, and transmits and presents the test product results to the delivery review user interface; the delivery review user interface receives the second review result of the second review of the test product results, if the second review result is passed, delivers the test product results for the project, if the second review result is not passed, generates a task re-optimization message and transmits it to the tester management user interface; the tester management user interface receives the corrected test task items generated based on the task re-optimization message, and the corrected test task items include the test tasks to be modified and / or the test tasks to be retested, and uses the corrected test task items as the newly input test task items, and repeats the test steps again until the new second review result obtained is passed; wherein, the automated test management module further includes a task recovery sub-module, a tester management user interface and a delivery review user interface, and the repeated test steps are: distributing the newly input test task items to the corresponding tester user interface, and the newly input test task items include one or more new test tasks; presenting the received new test tasks through the tester user interface, and confirming the received new test task form through the tester user interface, or modifying the received new test task form through the tester user interface, and confirming the newly modified test task form, and the new test task form is generated based on the new test tasks; making a test appointment based on the newly confirmed test task form, and the newly confirmed test task form includes at least the new test tasks and the newly appointed test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the new test tasks at the newly appointed test time; the continuous integration and continuous testing module pulls the new target test assets in the preset repository and deploys the new target test assets to the test asset module, and the new target test assets are the test assets corresponding to the new test tasks; the continuous integration and continuous testing module calls the test asset module to deploy the new target test assets in the test asset module to the new target test resources corresponding to the new test tasks in the test resource module to execute the new test tasks; the continuous integration and continuous testing module stores the new test product results of the new test tasks in the preset artifact repository; the automated test management module obtains the new test product results in the preset artifact repository; presenting the new test product results through the tester user interface and receiving the new first review result of the first review of the new test product results input through the tester user interface;If the new first review result is passed, submit the new test product result to the task recovery sub-module of the automated test management module; the task recovery sub-module transfers the new test product result to the test management staff user interface, receives the new delivery review instruction input by the test management staff user interface, and transmits the new test product result to the delivery review user interface for display; the delivery review user interface receives the new second review result for the new test product result.

[0066] It can be understood that if the second review result is not passed, then retesting is required. The test manager will return the non-passed test content to the tester again. The tester will make an appointment based on the content to be modified or retested and deploy it to the continuous integration and continuous testing system. That is, the corrected test task item needs to be used as the new input test task item, and the following repeated test steps need to be executed again until the new second review result is passed. If the new second review result is still not passed, then generate a task re-optimization message and transmit it to the test manager user interface; the test manager user interface receives the corrected test task item generated based on the task re-optimization message, and the corrected test task item includes the test task to be modified and / or the test task to be retested, as well as the following repeated test steps. The repeated test steps are as follows: distribute the new input test task item to the corresponding tester user interface, and the new input test task item includes one or more new test tasks; display the received new test tasks through the tester user interface, and confirm the received new test task form through the tester user interface, or modify the received new test task form through the tester user interface and confirm the new modified test task form. The new test task form is generated based on the new test tasks; make a test appointment based on the newly confirmed test task form. The newly confirmed test task form includes at least the new test tasks and the new appointment test time to trigger the automated test management module to call the continuous integration and continuous testing module to execute the new test tasks at the new appointment test time; the continuous integration and continuous testing module pulls the new target test assets in the preset repository and deploys the new target test assets to the test asset module. The new target test assets are the test assets corresponding to the new test tasks; the continuous integration and continuous testing module calls the test asset module to deploy the new target test assets in the test asset module to the new target test resources corresponding to the new test tasks in the test resource module to execute the new test tasks; the continuous integration and continuous testing module stores the new test product results of the new test tasks in the preset artifact repository; the automated test management module obtains the new test product results in the preset artifact repository; display the new test product results through the tester user interface and receive the new first review result input by the tester user interface for the new test product results; if the new first review result is passed, submit the new test product results to the task recycling sub-module of the automated test management module; the task recycling sub-module transfers the new test product results to the test manager user interface, receives the new delivery review instruction input by the test manager user interface, and transmits the new test product results to the delivery review user interface and displays them; the delivery review user interface receives the new second review result for the new test product results.

[0067] Please refer to Figure 5 , Figure 5 which is a schematic flowchart of the task flow process of the vehicle embedded software automated test management system provided by the embodiment of the present invention. As shown in Figure 5 , the following describes the task flow implementation method through specific specific embodiments. In this method, all process operations of the user can be implemented through the user interface of the automated test management module. First, the test manager publishes a test task item through the task publishing function of the user interface. All testers involved in this test task( Figure 5 taking Tester 1, Tester 2, and Tester X as examples. The number of X can be set according to the needs of the preset testers and test tasks, Figure 5 which is only an example here) can obtain the corresponding test task through the user interface, and confirm the necessary information and edit and modify directly through the test reservation function based on the received test task form. The content of this test reservation includes at least the test start time. After completing the test reservation, the system reservation module will deploy to the test resources by the continuous integration and continuous testing module in the background at the reserved time, forming test results and test data (test product results). All these test product results will be submitted after being reviewed by the tester. The task recovery function of the system will transfer the test product results submitted by the tester to the test manager, and the test manager will initiate the delivery review of this task through the user interface. The delivery reviewer can obtain the test results to be reviewed through the user interface and conduct content review. If the review fails (no), then task re-optimization is required, and this process will return to the test manager who will correct this round of test tasks again and send the corrected tasks to the corresponding tester to execute the test again; if the content review passes this time (yes), then all test products of this task can be directly used for project delivery.

[0068] In one embodiment, the automated test management module is further configured to: input a baseline release process item through the test manager user interface, where the baseline release process item includes a baseline identifier and content of assets to be marked; transmit the baseline release process item to the corresponding tester user interface according to the content of assets to be marked to prompt for test asset sorting; the tester user interface receives the sorted test assets input, stores the sorted test assets in a preset warehouse, and conducts confirmation of the baseline to be marked and confirmation of the content of assets to be marked through the tester user interface, and conducts one-key confirmation marking; after the test manager user interface receives the one-key confirmation marking completion messages fed back by all tester user interfaces, complete the baseline marking; where the automated test management module includes a tester user interface and a test manager user interface.

[0069] Please refer to Figure 6, Figure 6 It is a schematic flowchart of the baseline management process of the vehicle embedded software automation test management system provided by the embodiments of the present invention. As Figure 6 shown, the following uses specific specific embodiments to illustrate the baseline process. It should be noted that all user operations in this process can be implemented through the user interface. The vehicle embedded software automation test management system can realize the refined version management of the test asset data in the system, so it also has a corresponding baseline management process. This baseline management process involves two refined processes, namely the baseline release process of the test management personnel and the baseline marking process of the test personnel. The complete baseline management process starts from the baseline release process of the test management personnel and ends at the baseline marking process of the test personnel. In the above-mentioned baseline release process, the test management personnel create a baseline release process item (release baseline) in the user interface (test management personnel user interface). In this baseline release process item, the test management personnel will define the asset content items (assets to be marked) and the target baseline number (baseline identifier) that need to implement baseline marking. Among them, the asset content items define the items and component modules that need to implement baseline marking, and the baseline number is the baseline number ID of this baseline process. The system will locate the maintainer of the component module according to the component module that needs to implement baseline marking, and send the baseline marking process to the test personnel of the corresponding component module (corresponding test personnel user interface). The following takes the execution process of a test personnel as an example for exemplary illustration. The execution processes of other test personnel are similar and will not be elaborated. It should be noted that Figure 6In the above, tester 1, tester 2, and tester X are used as examples for exemplary description. The specific number of testers can be set according to actual needs, and the value of X is not limited. In the aforementioned baseline release process, the tester will receive a baseline marking process item (that is, the aforementioned baseline release process item) in the user interface, and the baseline marking process item contains the component module and the baseline number ID that the tester needs to implement the marking. The tester organizes the test assets (that is, organizes the asset content) according to the received baseline marking process item. The test asset organization includes but is not limited to organizing all asset contents of the components that need to be marked, so that the contents of all test asset items are matched. After completing the organization of the test asset content, confirm the target baseline to be marked and confirm the asset item to be marked, that is, the component module (determine the baseline to be marked, confirm the asset to be marked), and confirm the mark with one click to complete the baseline marking process of the component module test asset. It should be emphasized that the system has a background baseline marking implementation program, which simplifies the process of users implementing baseline marking, so that users only need to organize asset content, and the system can realize convenient one-click confirmation of marking. Accordingly, after the testers complete the baseline marking process, the test manager can obtain the current baseline release process status in the user interface and view the current baseline marking process implementation status details of each component module released. Only when all relevant testers have completed the baseline marking process, the test manager's baseline release process can enter the completion state. At this point, the complete baseline management process implementation is completed.

[0070] In one embodiment, the automated testing management module also includes a test manager user interface, a system manager user interface and a tester user interface; the test manager user interface is used to input the basic project information of the project and transmit the basic project information to the system manager user interface; the system manager user interface is used to create a project space based on the basic project information and assign the management authority of the project space to the test manager account; when the test manager account of the test manager user interface is in a logged-in state, the test manager user interface is used to input at least one of the sorted project assets, sorted project resources, and sorted project software characteristics; the test manager user interface is also used to define the project modules of the project and the system function allocation of the project member accounts; when the test manager user interface is used to input the sorted project software characteristics, the test manager user interface is also used to configure the software refresh mode and configure the preset pipeline of the project; when the project member account of the tester user interface is in a logged-in state, the tester user interface is used to initiate a test appointment for the project in response to a test appointment instruction.

[0071] The following uses specific specific embodiments to exemplarily illustrate the configuration process of platform project asset deployment in this solution. It should be noted that all user operations in this process can be implemented through the user interface. Please refer to Figure 7 , Figure 7 is a flow schematic diagram of the configuration process of project asset deployment of the vehicle embedded software automated test management system provided by the embodiment of the present invention. As Figure 7As shown, the system can achieve the test deployment of differentiated projects, and can achieve the differentiated project asset allocation of specific projects, define project modules and members, define project resource allocation, project software feature configuration, etc. Therefore, when deploying each project, the test manager of the project needs to first apply to create a project space and configure the designated asset items of the project and the detailed features of the corresponding asset items within the applied-for project space. Specifically, when there is a need for specific project deployment, the test manager defines the basic project information of the project to be deployed through the user interface and inputs it into the user interface of the system manager of the system. The system manager creates a project space based on the obtained project basic information, and the created project space will assign the management authority of this project space to the test manager (assign the management authority of the project space to the test manager's account), and then the test manager obtains this project space. Further, the test manager sorts out project assets, project resources, project software features and defines project modules and members. The project assets sorted out by the above test manager include, but are not limited to, at least one of the project requirement address, the cloud repository to which this project belongs, the project component modules included, the maintenance personnel of each component module and the associated developers, the project domain in the defect management system, etc., and after completing the sorting of project assets, the corresponding project asset items are associated through the user interface of this system. The project resources sorted out by the aforementioned test manager are mainly the test resources within this test management system involved in this project, that is, the bench system and project ports. According to the test bench deployed for this project, the bench for deploying the automated test execution of this project is defined, as well as the component deployment distribution in each bench resource. Based on such information, the test manager configures the system resources of this project through the user interface of the system. The software features of this project sorted out by the aforementioned test manager are mainly for the automated software refresh when serving the test execution deployment of specific projects. Since different projects often involve multiple different controller cores, and different controller cores have different chip types, there are often differences when performing automated software refresh. In addition, according to the characteristics of different projects, the software to be verified often has different verification levels according to the development scope, such as the verification of pure bottom software, the verification of integrated application software, etc.; and there are different software versions according to the verification scope, such as whether information security is integrated, whether the customer version application is integrated, etc.; and according to customer requirements, each software target has different refresh methods, such as single-core refresh, whole-package refresh, etc. Therefore, the test manager configures specific software targets and corresponding refresh methods according to the software features of this project. And according to the existing configuration, the CX Pipeline (preset pipeline) of this project is configured through the user interface.Accordingly, after the test manager completes the association of project assets, the configuration of project system resources, the software target configuration, the refresh mode configuration, and the CX Pipeline configuration, the resource scheduling function of the system has the scheduling function for the automated test tasks of this project. Accordingly, based on the project modules and members configured by the test manager in the system, the involved testers can initiate a test reservation for this project and call the aforementioned scheduling function for the automated test tasks that can serve this project to schedule and execute specific test tasks.

[0072] The following uses specific specific embodiments to exemplarily illustrate the process of test execution and test development in the system of this solution. It should be noted that all user operations in this process can be implemented through the user interface. Please refer to Figure 8 , Figure 8 FIG. is a schematic flowchart of the test execution and test development process of the vehicle embedded software automated test management system provided by the embodiment of the present invention. As Figure 8As shown in the figure, the vehicle embedded software automated test management system manages the project requirements corresponding to the project. Users can obtain detailed project requirements through the user interface and manage test cases by developing test cases based on the project requirements through the user interface (testers manage test cases through the use case management function based on the project requirements). It should be noted that all the test cases developed by testers are the data basis for the automated test execution of the system and also the target objects of test execution. When testers make a test reservation, the test reservation function directly associates the test cases in the vehicle embedded software automated test management system. The test reservation function will send the test execution request of the tester, that is, the test execution parameters, to the system reservation module for test execution. When the test reservation time arrives, the continuous integration and continuous test module will deploy the corresponding test assets (mainly test scripts) to the test resources specified by the user for test execution. The above test execution parameters include, but are not limited to, at least one of the following parameter information: test project, test software target, software refresh target, software refresh method, software characteristic parameters, test target component, target component use case set, target deployment rack, rack port, test execution time, etc. The parameter information belongs to either a single value or a group of values, which is specifically specified according to the characteristics of the tested project. After the test resources complete the test execution, they will output test product results, such as test results and corresponding test data. The vehicle embedded software automated test management system will analyze the data of this test result and determine whether it is necessary to trigger the defect process (determine the automatic judgment of the use case execution status of the test case). If the conditions for triggering the defect process are met (the automatic judgment of the use case execution status is the target status), the defect process function will be enabled. This defect process function will synchronously create or update test defect data with the confirmation of the tester; if the conditions for triggering the defect process are not met, the defect process function will be directly skipped. According to the above process flow, testers can obtain project requirements through the user interface, create and manage test cases, view test scripts, update test defect data based on the defect process, and obtain test results and test data after the test execution ends. Through the user interface, testers can obtain complete test assets and products. In addition to the above intuitive test assets, the system has a data dashboard function. This data dashboard function summarizes information such as test requirements, test cases, test defects, test scripts, test results, and test data, and forms dashboard information based on the defined data rules for users to obtain and view the data information in the system related to testers, so as to assist users in understanding the asset status and quickly obtaining the data information they are concerned about.

[0073] In one embodiment, the vehicle embedded software automated test management system is further configured with an artificial intelligence data interface for the artificial intelligence system to obtain artificial intelligence requirement data through the artificial intelligence data interface, and process the artificial intelligence requirement data through the artificial intelligence system to obtain an artificial intelligence processing result. The artificial intelligence requirement data includes at least one of test assets, test product results, defect data, and test requirements.

[0074] As an example, the artificial intelligence data interface can be configured in the continuous integration and continuous testing module and / or the test asset module. It can be realized that in the case of subsequent needs, the relevant data accumulated in the system is further processed such as statistically analyzed, sorted, and analyzed through an approved artificial intelligence system.

[0075] Based on the integrated test assets and test resources, an interface for later deployment of AI (Artificial Intelligence) is reserved, which enables the AI system to obtain the standardized test assets within the system. Based on the huge multi-project test asset data within the system and combined with the AI function, more efficient AI technology services can be provided for the testers within the system.

[0076] The automated test management module in the vehicle embedded software automated test management system provided in the above embodiment calls continuous integration and continuous testing according to the obtained test task. The continuous integration and continuous testing module pulls the target test assets from the preset repository, deploys the target test assets to the test asset module, and calls the test asset module to deploy the target test assets in the test asset module on the target test resources corresponding to the test task in the test resource module to execute the test task. The test product result of the test task is stored in the preset artifact repository. The test product result in the preset artifact repository is obtained through the automated test management module, and the test product result is displayed and audited. The system realizes the integration of the continuous integration and continuous testing module, test assets, and test resources, and can also associate the preset repository with the preset artifact repository, thereby realizing the centralized management of test assets, test resources, test data, test products, and test processes, enabling unified management of the test management. The system can also support the deployment of test resources for multiple test projects to realize the automated test of multiple vehicle embedded software, reducing the development cost and maintenance cost, and being more convenient.

[0077] Optionally, the vehicle embedded software automated test management system provided in the above embodiment can be built on an existing system, such as a cloud repository, a cloud artifact repository, and a defect management module. The user group does not need to change the current existing application tools, and has good usability.

[0078] Optionally, the vehicle embedded software automated test management system provided by the above embodiments can achieve differentiated project deployment and be compatible with the convenient CX Pipeline configuration of individual projects, greatly improving the platform's compatibility with projects, avoiding secondary development and subsequent manual maintenance, and saving manpower input to a certain extent.

[0079] Optionally, the vehicle embedded software automated test management system provided by the above embodiments integrates test assets, test resources, and can realize data association of multiple peripheral systems, enabling users to obtain global assets through the vehicle embedded software automated test management system, which can not only achieve serial interaction of assets, but also achieve coordination and integration, and realize data association, greatly facilitating test execution and operation and maintenance.

[0080] Optionally, the vehicle embedded software automated test management system provided by the above embodiments can not only connect test assets in series, but also has a unified baseline management process, which can realize clear baseline version management within the system and make the test assets clear and well-organized.

[0081] Optionally, the vehicle embedded software automated test management system provided by the above embodiments integrates a mature continuous integration and continuous testing module and can achieve flexible and convenient project configuration, reducing the application threshold, enabling users who do not understand the continuous integration and continuous testing system to easily complete the CX Pipeline configuration of the project according to the instruction manual in the system, greatly facilitating project deployment and reducing personnel input.

[0082] Optionally, the vehicle embedded software automated test management system provided by the above embodiments realizes the functions from task release to test execution and result collection, and integrates the delivery review function, which can achieve effective delivery review quality gating, implement the test quality supervision of the project, and is beneficial to improving the test delivery quality.

[0083] Optionally, the vehicle embedded software automated test management system provided by the above embodiments integrates a convenient defect creation process and a defect closure process. Since the system realizes pre-filling of defect creation and automatic attachment of test data, it saves a large amount of content editing time for creating test defects and can effectively improve efficiency.

[0084] Optionally, the vehicle embedded software automated test management system provided by the above embodiments realizes the effective integration of test assets and test resources. The test assets in the system provide the basic data for automated testing of test resources, while the test execution of test resources continuously enriches the test assets of the project, realizing a virtuous cycle between test assets and test resources.

[0085] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the above examples are given by dividing the above-mentioned functional units and modules. In practical applications, the above functions can be allocated to different functional units and modules as needed, that is, the internal structure of the above device can be divided into different functional units or modules to complete all or part of the functions described above.

[0086] The embodiments provided above are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A vehicle embedded software automated test management system, characterized in that: The vehicle embedded software automated test management system includes an automated test management module, a continuous integration and continuous testing module, a test asset module and a test resource module, wherein: The automated test management module is used to call the continuous integration and continuous testing module to execute the test task according to the acquired test task, and the test task is a task of performing automated testing on vehicle embedded software; The continuous integration and continuous testing module is used to pull the target test assets from the preset warehouse and deploy the target test assets to the test asset module, where the target test assets are the test assets corresponding to the test tasks; The continuous integration and continuous testing module is further used to call the test asset module to deploy the target test asset in the test asset module on the target test resource corresponding to the test task in the test resource module to execute the test task; The continuous integration and continuous testing module is also used to store the test product results of the test task in a preset product library; The automated test management module is also used to obtain the test product results in the preset product library, and to display and review the test product results.

2. The vehicle embedded software automated test management system according to claim 1, characterized in that: The automated test management module is also used to determine the automatic determination case execution status of the test case according to the test product result; if the automatic determination case execution status is the target status, a prompt message is generated and displayed based on the target status, so that the first target user can determine the manual review and confirmation case execution status of the test case based on the prompt message; if the manual review and confirmation case execution status is a case failure, the automated test management module is triggered to create a basic defect form, so that the second target user can add a defect description based on the basic defect form, obtain defect data, and complete the creation of the defect form; If the manual review confirms that the execution status of the test case is successful, and the prompt message is a defect closing prompt, when the defect of the test case has been repaired and the preset conditions for closing the defect problem of the test case are met, it is confirmed that the defect needs to be closed, and the automated test management module is triggered to pull the basic defect form of the test case, so that the second target user can add a defect description based on the basic defect form to complete the creation of the defect form. After the completion process is confirmed, the defect of the test case is closed; Among them, if the target state is use case failure, the prompt message is a defect creation prompt message; if the target state is use case success, and the historical test result of the test case is test failure, the test case has an associated defect item, and the test case is in a pending verification state, the prompt message is a defect closing prompt.

3. The vehicle embedded software automated test management system as claimed in claim 2, characterized in that: The automated test management module creates a basic defect form, including: the automated test management module obtains relevant basic information of the test task to determine pre-filled information, and fills the pre-filled information into a preset form to obtain the basic defect form.

4. The vehicle embedded software automated test management system according to claim 2, characterized in that: The automated test management module is communicatively connected with the defect management module; The defect management module is used to store the defect data; The automated test management module is also used for at least one of the following: Obtain a defect data acquisition instruction, wherein the defect data acquisition instruction includes an identifier of defect data to be obtained, obtains corresponding defect data to be obtained from the defect management module based on the identifier of defect data to be obtained, and stores the defect data to be obtained into a preset storage space; A defect data display instruction is obtained, wherein the defect data display instruction includes an identifier of defect data to be displayed, and the defect data to be displayed stored in a preset storage space of the automated test management module is displayed based on the identifier of defect data to be displayed.

5. The vehicle embedded software automated test management system according to claim 4, characterized in that: The automated test management module includes a data dashboard submodule, which is used to generate dashboard data for at least one of the test assets, test product results, defect data, and test requirements according to preset data rules, and display the dashboard data through the automated test management module.

6. The vehicle embedded software automated test management system according to any one of claims 1 to 5, characterized in that: Before the automated test management module calls the continuous integration and continuous testing module to execute the test task according to the acquired test task, the automated test management module is configured as follows: Distribute the input test task items to corresponding tester user interfaces, wherein the test task items include one or more test tasks, and the automated test management module includes one or more tester user interfaces; Displaying the received test task through the tester user interface, and confirming the received test task form through the tester user interface, or modifying the received test task form through the tester user interface, and confirming the modified test task form, the test task form being generated based on the test task; A test reservation is made based on a confirmed test task form, wherein the confirmed test task form includes at least the test task and the scheduled test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the test task at the scheduled test time.

7. The vehicle embedded software automated test management system according to claim 6, characterized in that: The automated test management module displays and reviews the test product results, including: Displaying the test product result through a tester user interface, and receiving a first review result of a first review of the test product result input by the tester user interface; If the first audit result is passed, submitting the test product result to the task recovery submodule of the automated test management module; The task recovery submodule transfers the test product results to the test manager user interface, receives the delivery review instruction input by the test manager user interface, transmits the test product results to the delivery review user interface and displays them; The delivery review user interface receives a second review result of the second review of the test product result, and if the second review result is passed, the test product result is delivered to the project; if the second review result is not passed, a task re-optimization message is generated and transmitted to the test manager user interface; The test manager user interface receives a revised test task item generated based on the task re-optimization message, wherein the revised test task item includes a test task to be modified and / or a test task to be retested, and uses the revised test task item as a new input test task item, and repeatedly executes the repetitive test step until a new second audit result is obtained that is passed; Wherein, the automated test management module also includes the task recovery submodule, the test management user interface and the delivery review user interface; The repeated testing step includes: distributing the newly input test task items to the corresponding tester user interface, the newly input test task items include one or more new test tasks; displaying the received new test tasks through the tester user interface, and confirming the received new test task form through the tester user interface, or modifying the received new test task form through the tester user interface, and confirming the new modified test task form, the new test task form is generated based on the new test task; making a test appointment based on the new confirmed test task form, the new confirmed test task form at least includes the new test task and the new scheduled test time, so as to trigger the automated test management module to call the continuous integration and continuous testing module to execute the new test task at the new scheduled test time; the continuous integration and continuous testing module pulls the new target test assets in the preset warehouse, and deploys the new target test assets to the test asset module, the new target test assets are the test assets corresponding to the new test tasks; the continuous integration and continuous testing module calls the The test asset module is used to deploy the new target test asset in the test asset module on the new target test resource corresponding to the new test task in the test resource module to execute the new test task; the continuous integration continuous testing module stores the new test product result of the new test task in the preset artifact library; the automated test management module obtains the new test product result in the preset artifact library; the new test product result is displayed through the tester user interface, and a new first audit result of the first audit of the new test product result input by the tester user interface is received; if the new first audit result is passed, the new test product result is submitted to the task recovery submodule of the automated test management module; the task recovery submodule transfers the new test product result to the test manager user interface, receives the new delivery review instruction input by the test manager user interface, transmits the new test product result to the delivery review user interface and displays it; the delivery review user interface receives the new second review result of the second audit of the new test product result.

8. The vehicle embedded software automated test management system according to any one of claims 1 to 5, characterized in that: The continuous integration and continuous testing module is deployed with a plurality of preset pipelines that have completed modular integration, and the preset pipelines are used to perform at least one of continuous integration, continuous deployment, and continuous testing; and / or, The vehicle embedded software automated testing management system is also configured with an artificial intelligence data interface, so that the artificial intelligence system can obtain artificial intelligence demand data through the artificial intelligence data interface, and process the artificial intelligence demand data through the artificial intelligence system to obtain artificial intelligence processing results, wherein the artificial intelligence demand data includes at least one of the test assets, test product results, defect data, and test requirements.

9. The vehicle embedded software automated test management system according to any one of claims 1 to 5, characterized in that: The automated test management module is further configured to: Inputting baseline release process items through the test manager user interface, wherein the baseline release process items include a baseline identifier and asset content to be marked; Transmitting the baseline release process item to the corresponding tester user interface according to the content of the asset to be marked, so as to prompt the test asset to be sorted; The tester user interface receives the input of the sorted test assets, stores the sorted test assets into the preset warehouse, and confirms the baseline to be marked and the content of the assets to be marked through the tester user interface, and performs one-key confirmation marking; After the test manager user interface receives one-key confirmation marking completion messages fed back by all the tester user interfaces, the baseline marking is completed; Wherein, the automated test management module includes the tester user interface and the test manager user interface.

10. The vehicle embedded software automated test management system according to any one of claims 1 to 5, characterized in that: The automated test management module also includes a test manager user interface, a system manager user interface and a tester user interface; The test manager user interface is used to input basic project information of the project, and transmit the basic project information to the system manager user interface; The system administrator user interface is used to create a project space according to the project basic information and assign the management authority of the project space to the test administrator account; When the test manager account of the test manager user interface is in a logged-in state, the test manager user interface is used to input at least one of the combed project assets, combed project resources, and combed project software characteristics; The test manager user interface is also used to define the project modules of the project and the system function allocation of project member accounts; When the test manager user interface is used to input the sorted project software characteristics, the test manager user interface is also used to configure the software refresh mode and configure the preset pipeline of the project; When the project member account of the tester user interface is in a logged-in state, the tester user interface is used to initiate a test reservation for the project in response to a test reservation instruction.

Images