Automatic test system for GPU three-dimensional graphic interface

Abstract

The invention relates to an automatic test system for a GPU three-dimensional graphic interface. The system comprises a front-end interaction module used for receiving equipment connection information and test configuration parameters input by a user and displaying a test progress and a test result in real time; the rear-end control module is in communication connection with the front-end interaction module and comprises an equipment management unit, a data storage unit and a test control unit; the real-time communication module is used for realizing real-time synchronization of test progress and state between the front end and the rear end based on a WebSocket protocol; and the data management module is connected with the rear-end control module and is used for converting the test result recorded in the SQLite database into a visual picture so as to query the test result in the front-end interaction module by utilizing a mouse interaction event. By adopting the method, the GPU three-dimensional graphic interface testing efficiency can be improved.

Description

Technical Field

[0001] This application relates to the technical field of GPU interface testing, and particularly to an automated testing system for GPU 3D graphics interfaces. Background Art

[0002] During the development of graphics card drivers, testing the driver program to measure its compatibility with various graphics programming interfaces is a very important step, which can provide important information such as defects in the driver, directions for improvement, and the GPU's capability level. In the testing of GPU's 3D graphics interfaces, the 3D graphics interfaces refer to graphics rendering APIs such as OpenGL and Vulkan, which are formulated by organizations such as Khronos. Graphics card manufacturers write drivers according to these interfaces for application programs to call.

[0003] To verify whether the implementation of the graphics card driver for the interface meets the standards, it is necessary to write test items for each interface according to the standards during the driver development process. The Khronos organization that formulates graphics interfaces such as OpenGL and Vulkan provides corresponding test suites (VKGLCTS) to verify whether the interfaces meet the specifications. This test tool provides a large number of test items to verify whether each interface of the graphics card driver meets the specifications. When using it, testers input the names of the test items to be run or a list of multiple test item names and various configuration parameters. After the test suite runs the tests, it outputs the status information of each test item. However, the automation level of this test tool is low. When using this test tool, testers generally implement some automation functions by writing shell scripts or python scripts by themselves. For example, corresponding compilation scripts are written during the tool compilation stage to achieve automatic compilation, and during the testing stage, python scripts are used to automatically split test items and start multi-threaded tests using the subprocess module.

[0004] However, in the current 3D graphics interface testing, there are often problems such as the need to compile different versions of test suites on multiple different devices, resulting in repetitive and cumbersome compilation operations for testers during testing, reducing the testing efficiency. At the same time, due to the large number of test items, testers use scripts to analyze files such as the logs of the test suite, obtain the status of each test item, and then convert it into the format they need for storage, such as saving it to a csv file. However, this method cannot intuitively reflect the test results and is not convenient for searching the results. Text files cannot intuitively show the overall test situation of a certain test group, and it takes a long time to search in text files. This makes it difficult to judge the test results. Summary of the Invention

[0005] Based on this, it is necessary to provide an automated testing system for GPU 3D graphics interfaces in view of the above technical problems.

[0006] A GPU three-dimensional graphics interface automated test system, the system comprising:

[0007] A front-end interaction module, configured to receive device connection information and test configuration parameters input by a user, and to display the test progress and results in real time;

[0008] A back-end control module, communicatively connected to the front-end interaction module, including: a device management unit, a data storage unit, and a test control unit; the device management unit establishes an SSH connection with the device under test through the Paramiko module, verifies the device reachability, and obtains configuration information; the data storage unit converts the device connection information and configuration information into a JSON file and stores it in a device-specific directory, and uses an SQLite database to record the test results; the test control unit is configured to execute test program installation, test script scheduling, and result collection;

[0009] A real-time communication module, which realizes real-time synchronization of test progress and status between the front and back ends based on the WebSocket protocol;

[0010] A data management module, connected to the back-end control module, configured to convert the test results recorded in the SQLite database into visual pictures, so as to query the test results by using mouse interaction events in the front-end interaction module.

[0011] In one embodiment, the device connection information includes: the IP address of the test device, the SSH port, the device name and description, the SSH username and password; the device management unit establishes an SSH connection with the device under test according to the IP address of the test device, the SSH port, the device name and description, the SSH username and password, and the data storage unit converts the device connection information and configuration information into a JSON file and stores it in a device-specific directory.

[0012] In one embodiment, after converting the device connection information and configuration information into a JSON file and storing it in a device-specific directory, a test interface is displayed in the front-end interaction module, and the device configuration data, online information, test results, and test program information are requested from the back-end control module and displayed on the front-end page of the front-end interaction module. When a user click instruction is received on the front-end page to enter the program installation page, the front-end interaction module requests the back-end control module to query the test program package and the installation script, and displays them on the program installation page. After the user selects the test program package, the back-end control module installs the test program package according to the installation script.

[0013] In one embodiment, the device management unit uses the Paramiko module to create an SSH connection with the device under test, starts an installation sub-thread, and passes the SSH connection object to the sub-thread. The sub-thread uses sftp to transfer the test program package to the device under test, and automatically executes the decompression and compilation commands after the transfer is completed to complete the automatic compilation of the test program. The installation progress and status information are stored through a status storage object shared with the main thread, and the front-end interaction module obtains the installation progress through the real-time communication module and displays it on the program installation page.

[0014] In one embodiment, the test configuration parameters are generated after the user selects the test program, test script, test item list, and test type information on the front-end page after the test program is installed.

[0015] In one embodiment, before the automatic test is started, the back-end control module determines whether it is a new test request or a breakpoint recovery test. If it is a new test request, a test data cache directory is created in the device-specific directory, and the test configuration information and the current device configuration information are saved to the configuration file. If it is a breakpoint recovery test, the pandas module is used to read the completed test items from the completed test item list file saved at the breakpoint and convert them into a set. After reading all the test item lists and obtaining the uncompleted test items, they are output to the to-be-tested list.

[0016] In one embodiment, after the automatic test is started, the test sub-thread reads the output of the test command in a streaming manner, uses regular expressions to match specific content in the output, and saves the test results to the test status object in real time. The status data of each test item is stored in a dataframe object of the pandas module, the number of status test items is stored in an int type, and other data is stored in a string type. Among them, the test status object is shared with the main thread to transmit data to the front-end interaction module in real time through the main thread.

[0017] In one embodiment, when the test sub-thread detects that the test command has been executed, it judges the test end status. The test end status includes: test completed, test item crashed, test aborted due to SSH connection disconnection, and test actively ended by the tester;

[0018] When the test end status is test completed, the test sub-thread converts the data of each test item from the dataframe object to SQLite database storage;

[0019] When the test end status is that a test item crashes, the test sub-thread downloads the test log from the device under test using sftp, traverses and analyzes the test log, obtains the list of run test items and the name of the crashed test item, marks the status of the run and crashed test items as crashed, removes the run and crashed test items from the total test item list to obtain a new test item list, and starts the test again using the new test item list;

[0020] When the test end status is that the test is aborted due to the SSH connection being disconnected, the test sub-thread reconnects to the test device and resumes the test from the breakpoint;

[0021] When the test end status is that the tester actively ends the test, the test sub-thread saves the test status and exits, and the test data for this time is not deleted.

[0022] In one embodiment, when the test end status is test completion, the test sub-thread converts the test item data from a dataframe object to SQLite database storage, creates an image using the PIL module, traverses each test item in the test item list, converts the status of each test item into squares of different colors and writes them into the image to generate a visualization image for querying the test results using mouse interaction events in the front-end interaction module.

[0023] In one embodiment, the visualization image is displayed on the test result viewing page of the front-end interaction module, and the visualization image is stored as an HTMLImageElement object and then drawn on the canvas element. Mouse event listeners are bound to the canvas element. When the user operates the mouse, the selected test item is updated, the image is zoomed, and the image is redrawn and displayed in real time according to the position of the selected test item and the current image zoom ratio data. When different test items are selected, the front-end interaction module sends a test item result query request to the back-end control module. The query request is the serial number of the test item in the test item list, and the serial number is calculated according to the x and y axis coordinates of the current mouse in the image and the length and width of the image.

[0024] The above GPU three-dimensional graphics interface automated test system includes: a front-end interaction module, a back-end control module, a real-time communication module, and a data management module. The front-end interaction module receives the device connection information and test configuration parameters input by the user, and displays the test progress and results in real time, enabling full control of the entire test process during the test. The back-end control module conducts test control, including connection establishment, file storage, test program installation, test script scheduling, and result collection, to achieve automated testing. Finally, the data management module is connected to the back-end control module and is used to convert the test results recorded in the SQLite database into visualization images for querying the test results using mouse interaction events in the front-end interaction module. Description of the Drawings

[0025] Figure 1 It is a structural block diagram of an automated test system for a GPU 3D graphics interface in an embodiment;

[0026] Figure 2 It is a schematic flow chart of an automated test for a GPU 3D graphics interface in an embodiment;

[0027] Figure 3 It is a schematic flow chart of a back-end running test in an embodiment;

[0028] Figure 4 It is a schematic flow chart of storing and viewing test results in an embodiment. Specific implementation manners

[0029] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0030] In one embodiment, as Figure 1 shown, an automated test system for a GPU 3D graphics interface is provided, including: a front-end interaction module 100, configured to receive device connection information and test configuration parameters input by a user, and display the test progress and results in real time; a back-end control module 200, communicatively connected to the front-end interaction module, including: a device management unit 210, a data storage unit 220, and a test control unit 230; the device management unit 210 establishes an SSH connection with the device under test through the Paramiko module, verifies the device reachability and obtains configuration information; the data storage unit 220 converts the device connection information and configuration information into a JSON file and stores it in a device-specific directory, and uses an SQLite database to record the test results; the test control unit 230 is configured to execute test program installation, test script scheduling, and result collection; a real-time communication module 300, which realizes real-time synchronization of the test progress and status between the front and back ends based on the WebSocket protocol; a data management module 400, connected to the back-end control module 200, configured to convert the test results recorded in the SQLite database into visual pictures for querying the test results by using mouse interaction events in the front-end interaction module 100.

[0031] The above GPU three-dimensional graphics interface automated test system includes: a front-end interaction module, a back-end control module, a real-time communication module, and a data management module. The front-end interaction module receives device connection information and test configuration parameters input by the user, and displays the test progress and results in real time, enabling full control of the entire test process during the test. The back-end control module conducts test control, including connection establishment, file storage, test program installation, test script scheduling, and result collection, to achieve automated testing. Finally, the data management module is connected to the back-end control module and is used to convert the test results recorded in the SQLite database into visual pictures for querying the test results using mouse interaction events in the front-end interaction module.

[0032] In one embodiment, the present application adopts a front-back end separation architecture. The front end is responsible for interacting with the user, and the back end is responsible for tasks such as managing device data and conducting automated testing. Specifically, the front-end interaction module is implemented using the Vue framework, and the back-end control module builds an interface for interacting with the front end using the FastAPI module, and uses the Paramiko module to establish an SSH connection with the device under test and conduct automated testing.

[0033] In another embodiment, the device connection information includes: the IP address of the test device, the SSH port, the device name and description, the SSH username and password; the device management unit establishes an SSH connection with the device under test according to the IP address of the test device, the SSH port, the device name and description, the SSH username and password, and the data storage unit converts the device connection information and configuration information into a JSON file and stores it in the device-specific directory.

[0034] In addition, after converting the device connection information and configuration information into a JSON file and storing it in the device-specific directory, a test interface is displayed in the front-end interaction module, and requests for device configuration data, online information, test results, and test program information are sent to the back-end control module and displayed on the front-end page of the front-end interaction module. When a user click instruction is received on the front-end page to enter the program installation page, the front-end interaction module requests the back-end control module to query the test program package and the installation script and displays them on the program installation page. After the user selects the test program package, the back-end control module installs the test program package according to the installation script.

[0035] In the above embodiments, a user-friendly graphical interaction interface is provided, and testers can conveniently complete the entire test process by clicking on the graphical interface, reducing the difficulty and time consumption of the test work.

[0036] In one embodiment, the device management unit uses the Paramiko module to create an SSH connection with the device under test, starts the installation sub-thread, and passes the SSH connection object to the sub-thread. The sub-thread uses sftp to transfer the test program package to the device under test, and automatically executes the decompression and compilation commands after the transfer is completed, completing the automatic compilation of the test program. The installation progress and status information are stored through a status storage object shared with the main thread, and the front-end interaction module obtains the installation progress through the real-time communication module and displays it on the program installation page. The test configuration parameters are generated after the test program is installed, when the user selects the test program, test script, test item list, and test type information on the front-end page.

[0037] Thus, the basic process of the automated test is completed, as Figure 2 shown.

[0038] In one embodiment, as Figure 3 shown, before the automatic test is performed, the back-end control module determines whether it is a new test request or a breakpoint recovery test. If it is a new test request, a test data cache directory is created in the device-specific directory, the test configuration information and the current device configuration information are saved to the configuration file, and the specified test item list is copied as the list of items to be tested. If it is a breakpoint recovery test, the pandas module is used to read the completed test items from the completed test item list file saved at the breakpoint and convert them into a set. After reading all the test item lists and obtaining the uncompleted test items, they are output to the list of items to be tested. After the initialization is completed, the test is started. The back-end generates test commands according to the test configuration passed in from the front-end, uses the Paramiko module to create an SSH connection, and starts the test sub-thread to execute the test commands.

[0039] In one embodiment, after the automatic test is started, the test sub-thread reads the output of the test command in a streaming manner, uses regular expressions to match specific content in the output, and saves the test results to the test status object in real time. The status data of each test item is stored in a dataframe object of the pandas module, the number of status test items is stored in an int type, and other data is stored in a string type. Among them, the test status object is shared with the main thread to transmit data to the front-end interaction module in real time through the main thread. After receiving the message that the back-end test has been started, the front-end establishes a WebSocket connection with the back-end and obtains the test status from the back-end in real time and displays it.

[0040] In one embodiment, when the test sub-thread detects that the test command has been executed, it determines the test end status, which includes: test completed, test item crashed, test aborted due to SSH connection disconnection, and test actively ended by the tester; when the test end status is test completed, the test sub-thread converts the test item data from the dataframe object to SQLite database storage; when the test end status is test item crashed, the test sub-thread uses sftp to download the test log from the device under test, traverses and analyzes the test log, obtains the list of executed test items and the name of the crashed test item, marks the status of the executed and crashed test items as crashed, removes the executed and crashed test items from the total test item list to obtain a new test item list, and uses the new test item list to restart the test; when the test end status is test aborted due to SSH connection disconnection, the test sub-thread reconnects to the test device and resumes the test from the breakpoint; when the test end status is test actively ended by the tester, the test sub-thread saves the test status and exits, and the current test data is not deleted.

[0041] Specifically, in the case of SSH connection disconnection, the test sub-thread attempts to reconnect to the device after 30 seconds and resume the test from the breakpoint. If the connection fails multiple times, the test exits and saves the test status for subsequent recovery. In the case of the tester actively ending the test, the tester can resume the current test at any time, and the previous incomplete test data will only be deleted when starting a new test.

[0042] In one embodiment, when the test end status is test completed, the test sub-thread converts the test item data from the dataframe object to SQLite database storage, creates an image using the PIL module, traverses each test item in the test item list, converts the status of each test item into squares of different colors and writes them into the image to generate a visualization image for querying the test results using mouse interaction events in the front-end interaction module.

[0043] In this embodiment, when using VKGLCTS to test the Vulkan interface, the number of test items is about 1 million. It is difficult to directly store all test item data in a text to intuitively reflect the advantages and disadvantages of the driver's implementation of this graphics interface. Therefore, in the present invention, the test platform stores the test results in an SQLite database and converts the results into visual pictures to facilitate testers to observe the test results. Specifically, the program uses the method of converting a dataframe of the pandas module to an SQLite database to store the results in a database file. There are three pieces of data in the database table: the name of the test item, the status, and the serial number in the test item list. An index is established for the two pieces of data of the serial number and the name to facilitate testers to query. After the storage is completed, the program uses the PIL module to create a picture, traverses each item in the test item list, fills different color blocks in the picture according to different results of the test items, each test item fills a square of 10×10 size, and the number of items filled in each row is rounded up to the nearest integer after taking the square root of the number of test items. Finally, the output picture is a PNG picture with an aspect ratio of 1:1.

[0044] In one embodiment, as Figure 4 shown, a schematic diagram of the test result storage and viewing process is provided. The visual picture is displayed on the test result viewing page of the front-end interaction module, and the visual picture is stored as an HTMLImageElement object and then drawn on the canvas element. Mouse event listeners are bound to the canvas element. When the user operates the mouse, the selected test item is updated, the picture is zoomed, and the picture is redrawn and displayed in real time according to the position of the selected test item and the current picture zoom ratio data. When different test items are selected, the front-end interaction module sends a test item result query request to the back-end control module. The query request is the serial number of the test item in the test item list, and the serial number is calculated according to the x and y axis coordinates of the current mouse in the picture and the length and width of the picture.

[0045] Specifically, when a tester views the test results through the front-end page of the test platform, the test result viewing page first requests the png picture output at the end of the test. The back-end will create a connection pool. When a query request is received, the corresponding test item result is queried using the database connection in the connection pool and returned. The back-end provides two query methods: the GET method query and the WebSocket query to adapt to different scenarios. The front-end updates the query results to the page in real time. Since the update speed of the selected test item is fast, the query frequency is restricted at the front-end to save resources, and the next query will only be triggered after a certain period of time has passed since the last query.

[0046] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above various methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0047] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0048] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. An automated test system for GPU 3D graphics interfaces, characterized in that, The system includes: A front-end interaction module, which is used to receive the device connection information and test configuration parameters input by the user, and display the test progress and results in real time; A back-end control module, which is communicatively connected to the front-end interaction module and includes: a device management unit, a data storage unit, and a test control unit; the device management unit establishes an SSH connection with the device under test through the Paramiko module, verifies the device reachability and obtains the configuration information; the data storage unit converts the device connection information and configuration information into a JSON file and stores it in the device-specific directory, and uses an SQLite database to record the test results; the test control unit is used to execute the installation of the test program, schedule the test script, and collect the results; A real-time communication module, which realizes the real-time synchronization of the test progress and status between the front end and the back end based on the WebSocket protocol; A data management module, which is connected to the back-end control module and is used to convert the test results recorded in the SQLite database into visual pictures, so as to query the test results by using the mouse interaction event in the front-end interaction module.

2. The automated test system according to claim 1, wherein The device connection information includes: the IP address of the test device, the SSH port, the device name and description, the SSH username and password; the device management unit establishes an SSH connection with the device under test according to the IP address of the test device, the SSH port, the device name and description, the SSH username and password, and the data storage unit converts the device connection information and configuration information into a JSON file and stores it in the device-specific directory.

3. The automated test system according to claim 2, characterized in that, After converting the device connection information and configuration information into a JSON file and storing it in the device-specific directory, a test interface is displayed in the front-end interaction module, and the device configuration data, online information, test results, and test program information are requested from the back-end control module and displayed on the front-end page of the front-end interaction module. When the front-end page receives the user click instruction and enters the program installation page, the front-end interaction module requests to query the test program package and the installation script from the back-end control module and displays them on the program installation page. After the user selects the test program package, the back-end control module installs the test program package according to the installation script.

4. The automated test system according to claim 3, wherein, The steps for the back-end control module to install the test program package according to the installation script include: The device management unit uses the Paramiko module to create an SSH connection with the device under test, starts the installation sub-thread and passes the SSH connection object to the sub-thread. The sub-thread uses sftp to transfer the test program package to the device under test. After the transfer is completed, the decompression and compilation commands are automatically executed to complete the automatic compilation of the test program. The installation progress and status information are stored through the status storage object shared with the main thread, and the installation progress is obtained through the real-time communication module in the front-end interaction module and displayed on the program installation page.

5. The automated test system according to claim 4, wherein The test configuration parameters are generated after the installation of the test program is completed, when the user selects the test program, test script, test item list, and test type information on the front-end page.

6. The automated test system according to any one of claims 1 to 5, characterized in that, Before the automatic test is performed, the backend control module determines whether it is a new test request or a breakpoint recovery test. If it is a new test request, a test data cache directory is created under the device-specific directory, and the test configuration information and the current device configuration information are saved to the configuration file. If it is a breakpoint recovery test, the pandas module is used to read the completed test items from the completed test item list file saved at the breakpoint and convert them into a set. After reading all the test item lists and obtaining the uncompleted test items, they are output to the to-be-tested list.

7. The automated test system according to claim 6, characterized in that, After the automatic test is started, the test sub-thread reads the output of the test command in a streaming manner, uses regular expressions to match specific content in the output, and saves the test results to the test status object in real time. The status data of each test item is stored in a dataframe object of the pandas module, the number of status test items is stored in an int type, and other data is stored in a string type. Among them, the test status object is shared with the main thread to transmit data to the front-end interaction module in real time through the main thread.

8. The automated test system according to claim 6, wherein, When the test sub-thread detects that the test command execution is completed, it judges the test end status. The test end status includes: test completed, test item crashed, test aborted due to SSH connection disconnection, and test actively ended by the tester. When the test end status is test completed, the test sub-thread converts the test item data from the dataframe object to SQLite database storage. When the test end status is test item crashed, the test sub-thread uses sftp to download the test log from the device under test, traverses and analyzes the test log, obtains the list of test items that have been run and the name of the crashed test item, marks the status of the run and crashed test items as crashed, removes the run and crashed test items from the total test item list to obtain a new test item list, and uses the new test item list to restart the test. When the test end status is test aborted due to SSH connection disconnection, the test sub-thread reconnects to the test device and resumes the test from the breakpoint. When the test end status is test actively ended by the tester, the test sub-thread saves the test status and exits, and the test data for this time is not deleted.

9. The automated test system according to claim 8, wherein When the test end status is test completed, the test sub-thread converts the test item data from the dataframe object to SQLite database storage, uses the PIL module to create an image, traverses each test item in the test item list, converts the status of each test item into squares of different colors and writes them into the image to generate a visualization image for querying the test results using mouse interaction events in the front-end interaction module.

10. The automated test system according to claim 9, characterized in that, The visualization picture is displayed on the test result viewing page of the front-end interaction module, and the visualization picture is stored as an HTMLImageElement object and then drawn on the canvas element. Each mouse event listener is bound to the canvas element. When the user operates the mouse, the selected test item is updated synchronously, the picture is zoomed, and the picture is redrawn and displayed in real time according to the position of the selected test item and the current picture zoom ratio data. When different test items are selected, the front-end interaction module sends a test item result query request to the back-end control module. The query request is the serial number of the test item in the test item list, and the serial number is calculated according to the x and y axis coordinates of the current mouse in the picture and the length and width of the picture.

Images