Interface verification system and method and medium

Abstract

The invention provides an interface verification system, an interface verification method and a medium, and the interface verification system comprises a use case management module which uses a content imported by a use case to correspond to a keyword specification preset in the interface verification system, and generates an executable program corresponding to the content imported by the use case; the task management module is used for creating tasks and executing the tasks based on the executable program; the equipment management module is used for monitoring the signal state of the equipment terminal executing the task; and the data management module is used for generating a selectable use case list through the content imported by the use case. According to the method, all expected values and operation normalization are covered by a defined keyword system, task-based execution of a use case is visualized, a picture of a vehicle machine screen is projected to a system page through a screen projection program, and the innovation after execution is to provide a visualized analysis result and a result report which can be exported. The problems that most cockpit automation tests are difficult to rapidly carry out and cockpit automation needs to repeatedly adapt codes are solved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle system testing, and in particular to an interface verification system, a tool chain, a method and a medium. Background Art

[0002] With the development of automobile electronics and intelligence, the functionality and complexity of vehicle systems are increasing. In order to ensure the stability and reliability of vehicle control systems, the verification of the core functional points of vehicle computers has become particularly important. The traditional vehicle control function verification process mainly relies on manual operation, which is not only time-consuming and labor-intensive, but also prone to errors.

[0003] In order to quickly detect the implementation of the core functional points of the vehicle computer and ensure the correctness of the interaction of the human-machine user interface HMI-UI (Human Machine Interface-User Interface) and the accuracy of signal switching, a semi-automated interface verification tool chain can be used to solve the problem of low efficiency of manual confirmation of signals, while improving verification efficiency and ensuring consistency with product demand design.

[0004] There are many existing automated testing systems in the industry, but most of them have the disadvantage of having to adapt repeatedly. For version iterations, repeated code writing is necessary. The requirements for temporary tasks of automated program developers increase according to the number of iterated versions. Based on this problem, another problem will occur, that is, after each iteration and change, testers need to wait for the addition of automated programs before they can use them. However, manual operations alone cannot complete the relevant work in a short period of time. If you want to use manual coverage to solve the problem in a short period of time, you need to expand the number of personnel several times. When a program that is constantly iterating to meet the needs of users is in the process of rapid development, its corresponding detection program should be iterated synchronously and should not lag behind. Therefore, a corresponding automated testing system is needed to quickly adapt to rapid iterations, keep up with the development rhythm, and block the scope of serious problems that may exist in the program, so as to improve the efficiency of program function detection and reduce labor costs.

[0005] Therefore, we realize automatic double confirmation of vehicle computer signals and HMI UI screens, and set each operation step reasonably and flexibly to ensure that we do not reinvent the wheel (in program development, reinventing the wheel means reinventing existing and widely recognized solutions. There are already many ready-made solutions in the programming world, so "do not reinvent the wheel" has become an important principle). When the use case is written, it is equivalent to writing the program. As long as the use case is written correctly, the corresponding result report can be obtained. Through one-stop analysis, strong business customization can reduce the workload of repeated adaptation of most automation systems.

[0006] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present invention and does not constitute any limitation to the present invention. Summary of the invention

[0007] In view of the above-mentioned shortcomings of the prior art, the present invention provides an interface verification system, tool chain, method and medium, which covers all expected values ​​and the normativeness of operations through a defined keyword system, visualizes the execution of use cases based on tasks, and projects the screen of the vehicle computer onto the system page through a screen projection program. The innovation after execution is to provide visual analysis results and exportable result reports. This solves the problem that most cockpit automation tests are difficult to carry out quickly and that cockpit automation requires repeated adaptation of codes.

[0008] The present invention provides an interface verification system, comprising: a use case management module, which is used to perform keyword specification before the use case in the interface verification system is imported, the content of the use case import corresponds to the keyword specification preset in the interface verification system, and an executable program corresponding to the content of the use case import is generated according to the keyword specification of the use case; a task management module, which creates and executes tasks in the interface verification system based on the executable program; a device management module, which is used to monitor the signal status of a device terminal that executes the task; and a data management module, which generates a selectable use case list through the content of the use case import.

[0009] In one embodiment of the present invention, it also includes: a use case import workflow, which executes a use case import step through a data management module and automatically generates a selectable use case list; a use case execution workflow, which includes a selectable use case list step, a task generation step, a task execution step, and a completion and result report generation step; a signal monitoring workflow, which executes a status monitoring step through a device management module to confirm in real time the signal status of the device terminal related to the task execution.

[0010] In one embodiment of the present invention, in the use case execution workflow, the interface verification system synchronously displays the user interface and records the process video corresponding to the execution task steps in the user interface as the content of the result report.

[0011] In one embodiment of the present invention, it also includes a front-end page and a back-end program; the execution steps of the interface verification system include: a data import step: it uploads the use case data for processing by the back-end program in the interface verification system through the user interface of the front-end page, and stores the processed use case data in the database; a data export step: it initiates a query request through the user interface, and passes the query request to the back-end program to extract the use case data in the database and display it in the user interface.

[0012] In one embodiment of the present invention, the data import step also includes: building a user interface of the front-end page based on the front-end framework and its component library; uploading use case data through the user interface, and the front-end framework passes the use case data to the back-end framework; after the back-end framework receives the use case data, analyzing and processing the use case data through the back-end program and its software; storing the processed use case data in the corresponding database.

[0013] In one embodiment of the present invention, the data export step also includes: after a query request is initiated in the user interface, the query request is passed to the backend framework of the backend through the front-end framework of the front end; the back-end framework returns the use case data obtained from the database to the front-end framework, and displays the use case data on the user interface through the chart library of the front-end framework; an export request for the result file corresponding to the use case data is made through the user interface, and the front-end framework passes the export request to the back-end framework; the back-end framework generates a result file based on the use case data, returns it to the front-end framework, and downloads the result file from the user interface through the front-end framework.

[0014] In one embodiment of the present invention, an interface verification method is also provided, including: configuring functional scenario use cases of a device terminal based on keyword specifications; converting the functional scenario use cases into executable programs of the device terminal according to the keyword specifications; and determining the use case import workflow, use case execution workflow or signal monitoring workflow of the interface verification system based on the operation of the executable program.

[0015] In one embodiment of the present invention, it also includes: setting keyword specifications through the use case management module of the interface verification system; establishing a database of functional scenario use cases according to the keyword specifications; and developing a use case generation program that adapts to the general behavior of device terminals based on the database of functional scenario use cases.

[0016] In one embodiment of the present invention, an interface verification system that runs an interface verification method includes: providing a data import function for a functional scenario use case; creating and executing tasks corresponding to the data of the functional scenario use case; updating the status of the functional scenario use case based on recording the execution status of the task; analyzing the execution results of the task and displaying the analysis results through a user interface; providing an export function for the task execution results; wherein the export file of the task execution results also includes a video and log file of the functional scenario use case whose task execution results are failed.

[0017] In one embodiment of the present invention, a computer-readable storage medium is also provided, on which a computer program is stored. The computer program constructs any of the above-mentioned interface verification systems. When the computer program is executed by a processor of a computer, the computer executes any of the above-mentioned interface verification methods.

[0018] Beneficial effects of the present invention: The present invention provides an interface verification system, tool chain, method and medium, which realizes dual confirmation of vehicle computer signals and user interface (HMI UI screen) through automation, and makes corresponding reasonable and flexible settings for each operation step to ensure that the development process does not repeat the wheel. When the use case for interface verification is configured, it is equivalent to the program configuration is completed. As long as the use case is configured correctly, the result report can be obtained. Through one-stop analysis, strong business customization can reduce the workload of repeated adaptation of most automation systems.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present invention, and together with the specification, are used to explain the principles of the present invention. Obviously, the drawings described below are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0021] Figure 1 is a schematic diagram of an interface verification system of the present invention;

[0022] Figure 2 A schematic diagram of the workflow of the interface verification system of the present invention;

[0023] Figure 3 A schematic diagram of the user interface of the interface verification system of the present invention in the use case execution state;

[0024] Figure 4 A schematic diagram of a report on the results of a use case execution in an embodiment;

[0025] Figure 5 A schematic diagram of a process of an interface verification system based on a business perspective in an embodiment;

[0026] Figure 6 A schematic diagram of a user interface of an interface verification system on a task details page in an embodiment;

[0027] Figure 7 An example diagram of entity-relationship in a user interface of an interface verification system in one embodiment;

[0028] Figure 8 A schematic diagram of a device management page in a user interface of an interface verification system in an embodiment;

[0029] Fig. 9 A schematic diagram of a use case list page in a user interface of an interface verification system in an embodiment;

[0030] Fig.10 A schematic diagram of an executing page in a user interface of an interface verification system in an embodiment;

[0031] Fig.11 A schematic diagram of a task details page in a user interface of an interface verification system in another embodiment. DETAILED DESCRIPTION

[0032] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied by other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the features in the following embodiments and embodiments can be combined with each other without conflict. It should also be understood that the terms used in the embodiments of the present invention are to describe specific specific embodiments, rather than to limit the scope of protection of the present invention.

[0033] See also Figures 1 to 11 . It should be noted that the structures, proportions, sizes, etc. illustrated in the drawings in this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the limiting conditions for the implementation of the present invention, so they have no substantial technical significance. Any structural modification, change in proportional relationship, or adjustment of size, without affecting the effects and purposes that can be achieved by the present invention, should still fall within the scope of the technical content disclosed by the present invention. At the same time, the terms such as position and quantitative relationship cited in this specification are only for the convenience of description, and are not used to limit the scope of the implementation of the present invention. Changes or adjustments in their relative relationships should also be regarded as the scope of the implementation of the present invention without substantially changing the technical content.

[0034] See also Figures 1 to 4 The present invention provides an interface verification system, comprising:

[0035] A use case management module is used to perform keyword specification before the use case is imported into the interface verification system, to correspond the content of the use case import to the keyword specification preset in the interface verification system, and to generate an executable program corresponding to the content of the use case import according to the keyword specification of the use case;

[0036] A task management module, which creates tasks and executes tasks in the interface verification system based on the executable program;

[0037] A device management module, which is used to monitor the signal status of the device terminal performing the task;

[0038] The data management module generates a list of selectable use cases through the content imported by the use cases.

[0039] Furthermore, the interface verification system also includes:

[0040] The use case import workflow executes the use case import steps through the data management module and automatically generates a list of selectable use cases;

[0041] A use case execution workflow, which includes a selectable use case list step, a task generation step, a task execution step, and a completion and result report generation step;

[0042] The signal monitoring workflow executes the status monitoring step through the device management module to confirm the signal status of the device terminals related to the task execution in real time.

[0043] Among them, in the use case execution workflow, the interface verification system synchronously displays the user interface and records the process video of the corresponding execution task steps in the user interface as the content of the result report.

[0044] Specifically, in the embodiment of the present invention, the interface verification is performed through the input and output process of the use case, and the use case written by the interface requirement interpreter is standardized. The custom specification is the keyword set (that is, the keyword specification) of the use case import table. The corresponding use case is written through the defined keyword specification. After the interface is imported, the corresponding executable program is automatically generated to perform interface verification, and the status parameters of the device terminal such as the vehicle computer are monitored during the execution of the use case, and the execution result file is output after execution. In other words, the use case management module is used to manage the use cases that have been imported into the interface verification system; the task management module is used to create and execute tasks corresponding to the use case content; the device management module is used to confirm the current status of the device terminal; and the data management module is used to import external (Excel) data.

[0045] Please refer to the attached Figure 2 In the use case import workflow, the Excel format use cases written by the tester are imported through the data management module, and the use case list data for selection is automatically generated. In the use case execution workflow, by selecting the use case in the use case list and clicking execute, the system will generate the task and execute it. During the execution process, the real-time car computer central control screen will be displayed to confirm the real-time action for the user, and the execution process video will be automatically saved after the execution is completed, which is used as the basis for result confirmation. At the same time, after execution, a detailed result report is output, which explains the start time and end time of the execution task. If the result of the execution task is a failure, the log file corresponding to the failure result can also be directly exported on the page, which is convenient for subsequent targeted problem solving. In the signal monitoring workflow, through the status monitoring function of the device management module, the key signals of the device terminal such as the car computer during the execution of the task are monitored in real time.

[0046] Please refer to the attached Figure 3 More specifically, in a device terminal such as a car system, in the use case execution workflow, the corresponding user interface of the interface verification system is displayed. The progress information of the task being executed is displayed, including the total progress bar of multiple task sets located on the user interface and the module progress bar for executing the current task. The content of the use case is displayed on the left side of its user interface, such as content information that meets the requirements of the keyword specification. In the remaining main part of its user interface, there is a mapping of the central control interface of the car system, so that the execution process of the use case on the corresponding device terminal can be intuitively displayed, which is convenient for observing the changes in the corresponding front-end page of the interface verification.

[0047] Likewise, please see the attached Figure 4 , the result report file in the signal monitoring workflow can be data in Excel format, including use case ID, function, description, steps, expected value, start time, end time and result content. For example, for the use case to execute the air conditioning operation function, the use case ID information corresponding to the air conditioning on and off is 00023 and 00024 respectively; the function information corresponding to the air conditioning on and off is turning on AC and off AC respectively; the description information of turning on and off the air conditioning is "click the AC button to turn on the AC function" and "click the AC button to turn off the AC function" respectively; the step information of turning on and off the air conditioning is "open APP [air conditioning], set [AC] [off], click component [AC]" and "open APP [air conditioning], set [AC] [off], click component [AC]"; the expected value information of turning on and off the air conditioning is "confirm [AC] [on], receive signal [HmiAC = 01]" and "confirm [AC] [off], receive signal [HmiAC = 00]" respectively; the start time and end time information of turning on and off the air conditioning; the result information of turning on and off the air conditioning is "success" or "failure", and the specific meaning of the content of the result report file is not repeated here.

[0048] In this way, the dual confirmation of the vehicle computer signal and the user interface (HMI UI screen) is realized through automation, and each operation step is set reasonably and flexibly to ensure that the development process does not repeat the wheel. Once the use case for interface verification is written, it is equivalent to writing the program. As long as the use case is written correctly, you can just wait to get the result report. Through one-stop analysis, the business is strongly customized and the workload of repeated adaptation of most automation systems is reduced.

[0049] In the embodiment of the present invention, in order to realize the core function of automatically confirming vehicle control, the keyword automatic conversion system is defined through differences, and the content of the use case is converted into an executable program according to the keyword specification, so as to monitor the expected signal in the task execution of the device terminal in real time. With the correct use case written by the user in the interface verification operation as input, the program will automatically realize the cockpit function of the entire vehicle system and obtain the execution result, and output the result report to the user.

[0050] See also Figures 5 to 10 In one embodiment, the interface verification system further includes a front-end page and a back-end program, and the execution steps of the interface verification system include:

[0051] Data import step: Build the user interface of the front-end page through the front-end framework, upload the use case data for the back-end program to process in the interface verification system, and store the processed use case data in the database;

[0052] Data export step: Initiate a query request through the user interface, and pass the query request to the back-end program through the front-end framework to extract the use case data from the database and display it in the user interface.

[0053] Among them, the data import step also includes: building a user interface of the front-end page based on the front-end framework and its component library; uploading use case data through the user interface, and at the same time the front-end framework passes the use case data to the back-end framework of the back-end program; after the back-end framework receives the use case data, the use case data is analyzed and processed through the back-end program and its software; and the processed use case data is stored in the corresponding database.

[0054] Among them, the data export step also includes: after a query request is initiated in the user interface, the query request is passed to the back-end framework through the front-end framework; the back-end framework returns the use case data obtained from the database to the front-end framework, and displays the use case data on the user interface through the chart library of the front-end framework; an export request for the result file corresponding to the use case data is made through the user interface, and the front-end framework passes the export request to the back-end framework; the back-end framework generates a result file based on the use case data, returns it to the front-end framework, and downloads the result file from the user interface through the front-end framework.

[0055] Specifically, in an embodiment of the present invention, a front-end page designed and interactively implemented through a front-end framework such as a Vue framework is used to satisfy the user's needs for importing use case data, viewing the execution process, analyzing and confirming the results after execution verification, and exporting valid result files. The user's use case data is analyzed through a back-end program such as Python as a background program, and compliant data is imported into the database for storage. When the user wants to find use case or task result data, the database data is retrieved from the background and displayed to the user through the front-end framework, that is, the front-end page of the Vue framework. During this period, the tool chain used in the interface verification system also used back-end frameworks such as FastAPI (a modern, high-performance web framework suitable for building APIs, which uses Python 3.6 or higher). Similarly, it also includes the use of technical frameworks such as Electron (an open source library for building cross-platform desktop applications using JavaScript, HTML and CSS), Node.js (a JavaScript runtime environment based on the Chrome V8 engine, which enables JavaScript to run on the server side and is widely used to build back-end services and tools), Vue (Vue.js is usually referred to as Vue, which is a progressive JavaScript framework for building user interfaces and single-page applications SPA), Element-UI (a component library based on Vue, which provides a complete set of front-end interface solutions, including various common components and interaction modes), ECharts (an open source visualization chart library implemented in JavaScript, which can run on web pages and is used to make various charts and data visualization effects), SQLAlchemy (a Python SQL toolkit and object-relational mapping (ORM) system, which provides an efficient and concise interface for database operations). Its specific applications are not described here.

[0056] It should be noted that the current industry analysis of the automation framework of Android-related products has found that the RF framework (Robot Framework is a general automation testing framework that can be used for the development of keyword-driven programs) and the most popular automation framework Appium (an open source automation testing tool for UI testing between different mobile operating systems and applications) cannot solve the problem solved by the embodiment of the present invention, that is, the automation program cannot quickly meet the needs of updating the vehicle screen and signal set by continuously iterating the code. Therefore, based on the ideas and solutions for customization of vehicle-mounted products, and the program of the monitoring mechanism of the existing terminal vehicle-mounted UI screen and signal, based on the comparison dimension of the vehicle-mounted software system, the following improvements have been made:

[0057] 1. Keyword-driven program (keyword-driven program is a software testing method that controls the application interface by simulating user input and is widely used in automated testing): its goal is to automatically generate program code and execute it according to the defined keywords after the use case program is written;

[0058] 2. Vehicle control customization: The goal is to customize the core functions of vehicle control and make universal algorithms and processing for similar functions;

[0059] 3. Platform-based R&D (Platform-based R&D usually refers to the development of a reusable and scalable platform to support the development of multiple products and services): Its goal is to collaborate with developers and demand interpreters to determine relevant signals and page components during the development phase;

[0060] 4. Early warning notification: The goal is to collaborate with testers to achieve tasks and make the tools more timely;

[0061] 5. Verification scenario: Screen important scenarios for the core functions of the vehicle model, with the goal of covering all core functions;

[0062] 6. Component ID is configurable: The goal is to communicate and reach agreement with the development team in advance and put forward requirements for the component ID of the development module;

[0063] 7. Log acquisition: Collaborate with the log module developers to make the exported logs more effective;

[0064] 8. Scalability: The goal is to achieve a solution that can confirm the signals and APP actions involved in related functions by writing use cases.

[0065] In this way, all expectations and operational norms are covered through a defined keyword system. The innovation in operation is to visualize the execution of use cases based on tasks, and to project the image of the car screen onto the system page through the projection program. The innovation after execution is to provide visual analysis results and exportable result reports.

[0066] See also Figure 5 The present invention further provides an interface verification method, including: configuring a functional scenario use case of a device terminal based on a keyword specification; converting the functional scenario use case into an executable program of the device terminal according to the keyword specification; and determining at least one of a use case import workflow, a use case execution workflow, and a signal monitoring workflow of an execution interface verification system based on the executable program.

[0067] Specifically, in the embodiment of the present invention, the direct correspondence between the use case and the program is established through the system-defined keyword specifications for the vehicle computer, and the relationship between the program and the system page component is established through the system-defined component configuration table provided by the development team. The relationship between the signal in the use case and the current system is established through the signal file matched with the vehicle model. The specific implementation process is as follows Figure 5 As shown, ① is the functional scenario use case written for the specified vehicle model; ② is the automatic conversion of the use case that meets the keyword specification into a program; ③ is the process of sorting out the automated program into a complete workflow; ④ is the work of ② assisted by the signal file automatically matched with the vehicle model combined with the scenario use case; ⑤ is the work of ② assisted by the component file matched with the vehicle model combined with the scenario use case.

[0068] Furthermore, it also includes: setting keyword specifications through the use case management module of the interface verification system; establishing a database of functional scenario use cases according to the keyword specifications; and developing a use case generation program adapted to the general behavior of device terminals based on the database of functional scenario use cases.

[0069] Furthermore, an interface verification system that runs the interface verification method includes: providing a data import function for functional scenario use cases (such as Excel or CSV files); creating and executing tasks corresponding to the data of the functional scenario use cases; updating the status of the functional scenario use cases based on recording the execution status of the tasks; analyzing the execution results of the tasks, and displaying the analysis results through a user interface; providing an export function for the task execution results (such as PDF or Excel reports); wherein the export file of the task execution results also includes videos and log files of the functional scenario use cases whose task execution results are failed.

[0070] Specifically, in the embodiment of the present invention, the export file of the task execution result is shown in the attached Figure 6 As shown, in the user interface of the interface verification system, the basic information of the task details page includes the task name, task status, execution result, creation time, start time, end time, and encoding information of the execution device. The extended information of the task name is also displayed below the basic information of the user interface, which includes the information of the use case, the information of the generated report, and the statistical information of the number of exported full logs. On the right side of the basic information and on the upper side of the extended information of the task name, there are graphical statistics of the number of success / failure execution results of the use case data, as well as option buttons for "Execute again", "Result file", and "View use case". At the same time, in the entire task details page, if the execution result of the use case fails, the tile at the corresponding position is displayed in red, and if it is successful, the tile is displayed in green.

[0071] Please refer to the attached Figure 7As shown, it shows the relevant structure of the ER diagram (Entity Relationship Diagram) in the embodiment of the present invention, also known as the entity-relationship diagram. It includes the specific contents of the keyword specification examples such as the use case table, the device table, the task table, the signal correspondence table, and the component definition table, which will not be repeated here.

[0072] Please refer to the attached Figure 8 As shown, it shows the device management page of the interface verification system in the embodiment of the present invention. It displays the parameter information (model and serial number) of the corresponding device name and the "status monitoring" and "screen mirroring" buttons below the corresponding device name, and can call up the mapping of the central control interface of the vehicle system in the main page view of the user interface, so that the execution process on the corresponding device terminal during the use case execution can be intuitively displayed, which is convenient for observing the change process of the corresponding front-end page of the interface verification.

[0073] Please refer to the attached Fig. 9 As shown, it shows a page for selecting scenarios and use cases in the interface verification system in an embodiment of the present invention. The information of the use case list is displayed, and the fillable items for model, keyword filtering and function module filtering are displayed on the upper side of the page, and option buttons for "Execute Test", "Create Use Case Set" and "Batch Delete" are displayed on the right. The remaining main part of the page displays a list of use case information, which includes the type of use case, ReqId, module, function, description, operation steps and expected value information content, and a check box button is set on the left side of the use case information table in each row, and an editable option button is set on the right side. In this way, the use case information can be intuitively operated through the user interface.

[0074] Please refer to the attached Fig.10 As shown, it shows the page for executing the verification process in the interface verification system in the embodiment of the present invention, which is similar to the attached Figure 3 The contents of the pages shown are the same and will not be repeated here.

[0075] Please refer to the attached Fig.11 As shown, it shows the page of the result output process in the interface verification system in the embodiment of the present invention. The task details page is displayed, and basic information is displayed on the upper side. This part is similar to the attached Figure 6The corresponding contents are the same as in , so they will not be repeated here. Similarly, on the right side of the basic information, there are graphical statistics of the number of success / failure results of the use case data execution, as well as option buttons for "Execute again" and "Export report". The remaining main part of the page displays a list of use case information, which includes the use case's ReqId, module, function, description, steps, expected value, start time, end time, result, result details, and exception information content. In this way, the use case information can be intuitively operated through the user interface, and the exception information content of the interface verification failure can be conveniently obtained, so as to quickly correct the problems reflected by the interface verification system.

[0076] The present invention also provides a computer-readable storage medium on which a computer program is stored. The computer program constructs any of the above-mentioned interface verification systems. When the computer program is executed by a processor of a computer, the computer executes any of the above-mentioned interface verification methods.

[0077] In summary, the interface verification system, tool chain, method and medium provided by the present invention are to achieve the core function of automatically confirming vehicle control. Through the differential definition of the keyword automatic conversion system, the content of the use case is converted into an executable program according to the keyword specification, and the expected signals in the execution of the task by the device terminal are monitored in real time. By using the correct use case written by the user in the interface verification job as input, the program will automatically implement the cockpit function of the entire vehicle system and obtain the execution result, and output the result report to the user. Through automation, double confirmation of the vehicle signal and the user interface (HMI UI screen) is achieved, and each operation step is set reasonably and flexibly to ensure that the development process does not repeat the wheel. When the use case for interface verification is configured, it is equivalent to the completion of the program configuration. As long as the use case configuration is correct, the result report can be obtained. Through one-stop analysis, strong business customization can reduce the workload of repeated adaptation of most automation systems.

[0078] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. An interface verification system, It is characterized in that include: A use case management module, which is used to perform keyword specification before the use case is imported into the interface verification system, so that the content of the use case import corresponds to the keyword specification preset in the interface verification system, and generate an executable program corresponding to the content of the use case import according to the keyword specification of the use case; A task management module, which creates and executes tasks in the interface verification system based on the executable program; A device management module, which is used to monitor the signal status of the device terminal performing the task; A data management module generates a selectable use case list through the content imported by the use case.

2. The interface verification system according to claim 1, It is characterized in that Also includes: A use case import workflow, which executes the use case import step through the data management module and automatically generates a list of selectable use cases; A use case execution workflow, which includes a step of selecting the selectable use case list, a step of generating a task, a step of executing the task, and a step of completing and generating a result report; The signal monitoring workflow executes the status monitoring step through the device management module to confirm the signal status of the device terminal related to the task execution in real time.

3. The interface verification system according to claim 2, It is characterized in that In the use case execution workflow, the interface verification system synchronously displays the user interface and records the process video corresponding to the execution task steps in the user interface as the content of the result report.

4. The interface verification system according to any one of claims 1 to 3, It is characterized in that It also includes a front-end page and a back-end program; the execution steps of the interface verification system include: Data import step: uploading the use case data for processing by the back-end program in the interface verification system through the user interface of the front-end page, and storing the processed use case data in the database; Data export step: initiating a query request through the user interface, and passing the query request to the back-end program to extract the use case data from the database and display it in the user interface.

5. The interface verification system according to claim 4, It is characterized in that The data importing step further includes: Constructing the user interface of the front-end page based on the front-end framework and its component library; Uploading the use case data through the user interface, and the front-end framework transferring the use case data to the back-end framework of the back-end program; After the backend framework receives the use case data, the backend program and its software are used to analyze and process the use case data; The processed use case data is stored in a corresponding database.

6. The interface verification system according to claim 5, It is characterized in that The data export step further comprises: After the user interface initiates a query request, the query request is transmitted to the backend framework through the frontend framework; The backend framework returns the use case data obtained from the database to the frontend framework, and displays the use case data on the user interface through the chart library of the frontend framework; Propose an export request for a result file corresponding to the use case data through the user interface, and the front-end framework transmits the export request to the back-end framework; The backend framework generates the result file based on the use case data and returns it to the frontend framework, and the result file is downloaded from the user interface through the frontend framework.

7. An interface verification method, It is characterized in that include: Configure functional scenario use cases of device terminals based on keyword specifications; Converting the functional scenario use case into an executable program for the device terminal according to the keyword specification; Based on the executable program, a use case import workflow, a use case execution workflow or a signal monitoring workflow of the execution interface verification system is determined.

8. The interface verification method according to claim 7, It is characterized in that Also includes: Setting the keyword specification through a use case management module of the interface verification system; Establishing a database of the functional scenario use cases according to the keyword specification; Based on the database of the functional scenario use cases, a use case generation program adapted to the general behavior of the device terminal is developed.

9. The interface verification method according to claim 8, It is characterized in that The interface verification system for running the interface verification method comprises: Provide data import function for the functional scenario use case; Create and execute tasks corresponding to the data of the functional scenario use case; Based on recording the execution status of the task, updating the status of the functional scenario use case; Analyze the execution results of the task and display the analysis results through a user interface; Providing an export function for the task execution results; Among them, the export file of the task execution result also includes the video and log file of the functional scenario use case where the task execution result is failure.

10. A computer-readable storage medium, It is characterized in that A computer program is stored thereon, and the computer program constructs the interface verification system according to any one of claims 1-6. When the computer program is executed by a processor of a computer, the computer executes the interface verification method according to any one of claims 7-9.

Images