A method and apparatus for long-term stability testing of industrial software

Abstract

This invention discloses a method and apparatus for long-term stability testing of industrial software. The method includes: configuring a server resource list to obtain the server resources to be monitored; creating a UI menu inspection instance to simulate user operations on a browser, traversing all levels of menus in the industrial software under test, and enabling browser error monitoring to capture page error information; sequentially sending interface requests to the interfaces of the industrial software under test and obtaining return information, as well as saving the returned interface error information; cyclically performing UI menu inspection and interface request testing while monitoring the configured server resources and saving resource over-limit information; and remotely communicating the test results, page error information, interface error information, and resource over-limit information of the long-term stability test. This method comprehensively tests the stability of existing software during long-term operation from the perspectives of UI, interfaces, and resources, reducing human interference, achieving standardization and automation of long-term stability testing, and improving testing efficiency and accuracy.

Description

Technical Field

[0001] This invention relates to the field of industrial software information testing, and specifically to a method and apparatus for long-term stability testing of industrial software. Background Technology

[0002] Existing software may be unstable during long-term operation, requiring long-term monitoring of the stability of all software systems. However, software stability testing is a relatively difficult type of test in software testing, with limitations in time period, scenario, and operation.

[0003] Traditional long-term stability testing methods rely solely on manual testing, which is subject to numerous human interference factors and cannot achieve standardization and automation of long-term stability testing.

[0004] A Chinese invention patent proposes a software stability testing method based on pyecharts, which simply uses pyecharts to display test metrics in charts.

[0005] Therefore, it is currently impossible to conduct long-term stability and comprehensive testing of existing software. Summary of the Invention

[0006] To overcome the shortcomings of the above technologies, this invention provides a method and apparatus for long-term stability testing of industrial software. It comprehensively tests the stability of existing software during long-term operation from the perspectives of UI, interface, and resources, reduces interference from human factors, and realizes the standardization and automation of long-term stability testing, thereby improving the efficiency and accuracy of testing.

[0007] The technical solution adopted by this invention to overcome its technical problems is:

[0008] The first aspect of this invention is a method for long-term stability testing of industrial software, comprising: S1, creating a UI menu inspection instance to simulate user operation on a browser, traversing all levels of menus of the industrial software under test and enabling browser error monitoring to capture page error information; S2, sequentially sending interface requests to the interfaces of the industrial software under test and obtaining return information, and saving the returned interface error information; S3, cyclically performing UI menu inspection and interface request testing, monitoring the configured server resources, and saving resource over-limit information; S4, remotely communicating the test results of the long-term stability test, page error information, interface error information, and resource over-limit information.

[0009] Comprehensive long-term stability testing of industrial software is achieved through testing menu attributes to traverse the page menu, as well as interface testing and server resource monitoring.

[0010] Furthermore, the process involves creating a UI menu inspection instance to simulate user interaction with a browser, traversing all levels of menus in the industrial software under test, and enabling browser error monitoring to capture page error information. Specifically, this includes: S11, creating a UI menu inspection instance to create a browser object and a page object; S12, automatically logging into the industrial software under test based on the browser object and page object; S13, looping through all levels of menus in the industrial software under test for long-term stability testing, and enabling browser console error monitoring; S14, if error information is detected in the browser console, taking a screenshot of the page to obtain the error information; S15, closing the browser and the UI menu inspection instance; S16, continuously executing S11-S15 to perform long-term stability testing.

[0011] Furthermore, the automatic login to the industrial software under test based on browser objects and page objects specifically includes: performing long-term stability testing by iterating through all levels of menus in the industrial software under test based on the page menu order attribute and the page menu unique attribute.

[0012] Furthermore, the long-term stability test of the industrial software under test by iterating through all levels of menus based on the page menu order attribute and the page menu unique attribute specifically includes: S131, initializing the page menu order attribute; S132, obtaining menu elements based on the page menu order attribute, and obtaining the menu unique attribute based on the menu element; S133, clicking the menu according to the menu unique attribute and loading the corresponding page; S134, after the page is loaded, re-obtaining the menu order attribute of the current menu; S135, iteratively obtaining the menu order attribute of the next menu of the current menu, and repeating the above, thereby continuously conducting long-term stability tests on the page menus of the industrial software under test.

[0013] Furthermore, the step of obtaining the unique attribute of a menu based on a menu element specifically includes: determining whether a menu element exists; if the menu element does not exist, determining whether the menus corresponding to the current menu order attribute have been traversed; if the menu element exists, obtaining the unique attribute key corresponding to the current menu.

[0014] Furthermore, if an error message is detected in the browser console, a screenshot is taken to obtain the page error information. Specifically, this includes: taking a screenshot if the browser console outputs an error message; storing the unique menu attribute key for naming the screenshot file; and sending the error message and the screenshot file to the communication module.

[0015] Furthermore, a UI menu inspection instance is created based on the playwrite module.

[0016] Furthermore, the step of sequentially sending interface requests to the interfaces of the industrial software under test and receiving return information, as well as saving the returned interface error information, specifically includes: S21, logging into the industrial software, obtaining user authentication permissions for the industrial software, and storing the user authentication permissions in the request header; S22, sequentially sending interface requests to the industrial software, wherein the interfaces are pre-stored in the interface list; S23, receiving the return information of the test interface and storing it in the res field, judging the return information of the interface, and sending the returned error information to the communication module; S24, after executing all interface requests, logging out of the industrial software, and repeating S21-S24.

[0017] Another aspect of the present invention provides a testing apparatus for running the aforementioned long-term stability testing method for industrial software. The apparatus includes at least a long-term stability module, a monitoring module, and a communication module coupled to both the long-term stability module and the monitoring module. The long-term stability module performs long-term stability testing on the industrial software and sends long-term stability test data and anomaly information to the communication module. The long-term stability module includes an independent and parallel inspection unit and an interface request unit. The inspection unit traverses all levels of menus in the industrial software and performs error detection, sending anomaly information to the communication module. The interface request unit tests the interfaces of the industrial software and stores and sends anomaly information to the communication module. The monitoring module monitors the server resources occupied by the industrial software during the operation of the long-term stability module and sends anomaly information to the communication module. The communication module communicates the anomaly information fed back by the monitoring module and the long-term stability module, as well as the test data, with external systems.

[0018] By combining menu testing and page testing through inspection units and interface request units, comprehensive long-term stability testing of the industrial software under test can be achieved.

[0019] The beneficial effects of this invention are:

[0020] This invention proposes a method to perform long-term stability testing of industrial software by traversing page menus through menu attributes, as well as interface testing and server resource monitoring. Traditional long-term stability testing methods typically involve manual testing, such as opening and using the industrial operating system for a period of time. Compared to traditional methods, this invention achieves standardization and automation of long-term stability testing, improving efficiency and accuracy while reducing human interference. Simultaneously, the device provides intuitive data analysis and anomaly response mechanisms, offering data support for subsequent test reports. Attached Figure Description

[0021] Figure 1 This is a flowchart illustrating an industrial software long-term stability testing method according to an embodiment of the present invention.

[0022] Figure 2 This is a flowchart illustrating the process of traversing all levels of menus according to an embodiment of the present invention;

[0023] Figure 3 This is a schematic diagram of the architecture of an industrial software long-term stability testing device according to an embodiment of the present invention. Detailed Implementation

[0024] First, some abbreviations and key terms mentioned in this invention will be explained.

[0025] Playwright: An automated testing tool specifically designed to automate browser interactions in web applications.

[0026] SSH: A network protocol used for encrypted login between computers. SSH servers use the SSH protocol for remote control.

[0027] To facilitate a better understanding of the present invention by those skilled in the art, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The following are merely exemplary and do not limit the scope of protection of the present invention.

[0028] like Figure 1 As shown in the figure, a flowchart of the above-mentioned industrial software long-term stability testing method of the present invention mainly includes the following steps.

[0029] S1. Create a UI menu inspection instance to simulate user operations on the browser, traverse all levels of menus of the industrial software under test, and start browser error listening to obtain page error information by taking screenshots.

[0030] S11, create a UI menu inspection instance, thereby creating a browser object and a page object;

[0031] In one embodiment of the present invention, a UI menu inspection instance is created based on the Playwright framework, playwright = sync_playwright().start(); a browser object is created using the playwright.chromium.launch method, and finally a page object page = browser.new_page() is created.

[0032] PlayWright was used to simulate user actions on the browser, including logging in and then repeatedly clicking through all menus after logging in.

[0033] S12, Automatic Login to Industrial Software Based on Browser and Page Objects

[0034] Based on the browser object, the playwrite instance automatically opens the login page of the industrial software. The page object then automatically inputs the username and password, thus completing the login process.

[0035] S13, loop through all levels of menus in the industrial software under test to perform long-term stability testing, and enable error listening in the browser console.

[0036] After logging in, loop through all menu levels using the page object and enable error listening. The following specific process effectively traverses all menu levels, assuming lazy loading of the page menu and only one menu item is expanded at a time.

[0037] Because the page menu is not loaded completely at once—for example, when a user logs into the industrial software for the first time, only the first-level menu is loaded—when the user clicks on a menu item, its sub-menus are dynamically loaded, simultaneously expanding the parent menu and closing the expanded menus, and causing the menu order to be rearranged. Therefore, the page menu order attribute, i.e., the index attribute, changes dynamically when the menu is collapsed or expanded.

[0038] In one embodiment of the invention, traversal of all menus is achieved through the page menu order attribute `index` and the page menu unique attribute `key`. When there is no click operation, the order attribute of the next menu is the order attribute of the current menu + 1. In industrial information operating systems, the menu unique attribute `key` is unique. `key` is generally composed of the APP module's encoding, a unique field specified in the software code. After clicking a menu and causing a menu reordering, the current menu can be found through the `key` attribute. A typical flowchart is shown below. Figure 2 As shown.

[0039] S131, initialize the page menu order attribute index.

[0040] Initialize the menu order property index = 0.

[0041] S132, retrieve the menu element based on the page menu order attribute index, and retrieve the menu unique attribute based on the menu element.

[0042] In one embodiment of the present invention, the menu element is the entire menu, and all menu attributes can be obtained using the get_attribute() method, including the sequence attribute index and the unique attribute key. The menu element is obtained based on the page menu sequence attribute index using "div#menv>>div[data-index='{index}']". Elements possessing the correct attribute and value are found through the attribute and attribute value.

[0043] If the menu element does not exist, then iterate through the menus corresponding to the current menu order attribute.

[0044] When the menu element at index+1 does not exist, it means that there is no next menu in the current menu, that is, all levels of menus have been traversed.

[0045] If the menu element exists, retrieve the unique key attribute corresponding to the current menu.

[0046] In some implementations, the browser console is monitored simultaneously. If the browser console outputs an error message, a screenshot of the page is taken, and the unique menu attribute key is stored for naming the screenshot file; then the error message and the screenshot file are sent to the communication module.

[0047] It's important to note that using the key for the page screenshot allows you to clearly identify which menu item is causing the error and view the page display at the time of the error. You can't use the menu name as the screenshot name because menu names might be duplicated, risking the screenshot file being replaced. If there's no error, there's no need to take a screenshot, and therefore no need to save the key.

[0048] S133, Click the menu based on the menu's unique attribute key and load the corresponding page.

[0049] The "div#menv>>div[data-key='{key}']" function is used to make the menu clickable based on the unique key attribute of the menu.

[0050] S134, After the page has finished loading, retrieve the menu order attribute index of the current menu.

[0051] S135: Loop through the menu order attribute index of the next menu of the current menu, repeat steps S232-S235 until all menus corresponding to the current menu order attribute have been traversed.

[0052] Iterate through the index of the next menu item, so that index = index + 1.

[0053] S14. If error messages are detected in the browser console, take a screenshot of the page to obtain the page error information.

[0054] When an error occurs on the page, the browser's console will output the error message: msg.type == "error". At this point, take a screenshot of the page, and name the screenshot file using the menu key.

[0055] It should be noted that the error does not affect subsequent tests.

[0056] S15, Inspection example of closing the browser and closing the UI menu.

[0057] After clicking through all page menus in the industrial software, close the browser page and the UI menu inspection instance. Then re-execute S21 to complete the long-term stability test of the industrial software UI menu.

[0058] S16, repeat S11-S15 to continuously perform long-term stability testing.

[0059] It should be noted that the UI menu inspection example can be implemented using other languages ​​and module libraries. Languages ​​can include Python, Java, C++, Go, etc., and module libraries include, but are not limited to, playwright, selenium and its derivative libraries.

[0060] S2, sequentially sends interface requests to the interfaces of the industrial software under test and receives the returned information, and saves the returned interface error information.

[0061] Interface testing is used to test the interfaces of the industrial software under test, and specifically includes the following steps.

[0062] S21 accesses and logs into the industrial software through the interface, obtains the user authentication permissions of the industrial software, and stores the user authentication permissions in the request header.

[0063] When requesting the Login industrial software, user authentication permissions are obtained, and these permissions are added to the request headers. Subsequent requests will include these headers, thus granting subsequent requests the permission to retrieve data.

[0064] S22, sequentially send interface requests to the industrial software, wherein the interfaces are pre-stored in the interface list in the interface request unit.

[0065] The API list must include at least four fields: url, method, data, and headers.

[0066] Here, url is the request address of the interface. The interface request unit is automatically concatenated with the server and port to form a complete interface request address.

[0067] In one embodiment of the present invention, the URL request is, for example: / msService / perfrun / model01-form / save. The method is the request method of the interface, such as: get, post, put, etc.

[0068] `data` is the request body data of the API, in JSON format. To avoid data duplication during API requests, `data` supports a loop counter `index` and the `datetime` function. For example, if `data` is `{"a":index, "b":datetime.now().timestamp()}`, the first loop will pass parameter `a` = 1 and parameter `b` = the timestamp of the first loop, while the second loop will pass parameter `a` = 2 and parameter `b` = the timestamp of the second loop. The loop counter `index` can count according to user-defined rules, such as incrementing by 1, so `index` = 1 on the first request and `index` = 2 on the second request.

[0069] The headers are the request headers of the interface. This field is automatically generated by the interface request unit and contains the user authentication permissions obtained by the login method, ensuring that subsequent requests have the permission to retrieve data.

[0070] S23, the interface request unit receives the return information from the test interface and stores it in the res field, and then judges the return information. If the response code res.status_code is not a 200 series response code, the error information returned by the interface is stored in the specified file and sent to the communication module.

[0071] S24: After executing all interface requests, log out of the industrial software and repeat S31-S34.

[0072] After all requests are completed, a logout operation is performed, and then the above operation is repeated in a loop.

[0073] S3, continuously performs UI menu inspection and interface request testing, monitors the configured industrial operating system server resources, and saves resource overrun information.

[0074] S31, configure the server resource list to obtain the industrial operating system server resources to be monitored.

[0075] The industrial operating system is configured on the server, and after deployment, users can access it locally via a browser. Users create server resources to be monitored in the server resource list. The server resource list includes seven fields: name, command, regular expression, time interval, upper alarm value, lower alarm value, and enabled, as shown in Table 1. Monitoring server resources is primarily performed through the following steps.

[0076] Table 1

[0077]

[0078]

[0079] S32 creates a remote server and connects to the industrial operating system server via the connect function.

[0080] In one embodiment of the present invention, the long-term stability test method introduces the paramiko library, creates an SSH server, and then uses the connect function to connect to the industrial operating system server. The industrial operating system runs the industrial software under test. The information required to connect to the remote server is the information of the industrial operating system server, including the server IP, port, username and password.

[0081] S33 retrieves server resource information at preset time intervals and saves it until the long-term stability test ends.

[0082] In one embodiment of the present invention, after connecting to the server, the `exec_command` function is used to execute Linux commands. The output of the command execution is processed using regular expressions to obtain information about the server resource. Furthermore, the system iterates through the queries at time intervals and stores the retrieved values ​​in a table until the long-term stability test is completed.

[0083] S34 compares the saved result with a preset threshold. If the preset threshold is exceeded, a server resource alarm is triggered, and the resource name, real-time value, and alarm value are sent to the communication module.

[0084] If the preset threshold is exceeded, the server resource will trigger an alarm. The name of the server resource that triggered the alarm, the real-time value, and the alarm value will be sent to the communication module.

[0085] S4 remotely communicates the test results of long-term stability testing, page error information, interface error information, and resource overrun information.

[0086] Long-term stable test data includes, but is not limited to: the number of times UI inspections were executed, the list of API requests and the number of times they were executed, server resource data tables, and a summary of exception information.

[0087] like Figure 3As shown, another embodiment of the long-term stability testing device of the present invention includes at least a long-term stability module, a monitoring module, and a communication module coupled to the long-term stability module and the monitoring module respectively. The long-term stability module is used to perform long-term stability testing on industrial software and send long-term stability test data and abnormal information to the communication module. The long-term stability module includes an independent and parallel inspection unit and an interface request unit. The inspection unit is used to traverse all levels of menus of the industrial software and perform error detection, and send abnormal information to the communication module. The interface request unit is used to test the interface of the industrial software and store and send abnormal information to the communication module. The monitoring module is used to monitor the server resources occupied by the industrial software during the operation of the long-term stability module and send abnormal information to the communication module. The communication module is used to communicate the abnormal information fed back by the monitoring module and the long-term stability module, and to communicate the test data with the outside.

[0088] The long-term stability module, as the core execution module for long-term stability testing, is used to perform long-term stability testing on the software and send long-term stability test data and exception information to the communication module. The long-term stability module includes an inspection unit and an interface request unit, each running two independent parallel threads.

[0089] The interface request unit in the long-term stability module is used to test the interfaces of industrial software and to store and send exception information to the communication module. The interface request unit sends requests directly through the interfaces, requiring a login request to obtain user authentication permissions before sequentially requesting the interfaces to be tested.

[0090] The monitoring module monitors server resources during the operation of the long-term stability module and sends abnormal information to the communication module. The communication module then communicates the abnormal information from the monitoring module and the long-term stability module with external systems. This enables monitoring of server resources used by industrial software during the operation of the long-term stability module.

[0091] In one embodiment of the present invention, the communication module can be configured to communicate with the user in real time via WeChat, DingTalk, email, SMS, etc. When the stability module and the monitoring module send abnormal information to the communication module, the communication module will send information to the user in real time, informing them of the abnormal situation during the stability test. When the stability test ends, the communication module will also send the stability test data to the user. The stability test data includes, but is not limited to: the number of UI inspection executions, the list of interface requests and the number of executions, the server resource data table, and a summary of abnormal information.

[0092] It should be noted that the interface request unit is mainly used to cover interfaces that the UI inspection unit does not request, such as document details, document saving, process submission, etc.

[0093] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0094] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

Claims

1. A method for long-term stability testing of industrial software, characterized in that, The application relates to a long-term stability test method for industrial software, which comprises the following steps: S1, creating a UI menu inspection instance to simulate user operation on a browser, traversing all hierarchical menus of the industrial software to be tested, starting browser error monitoring to obtain page error information through screenshot; S2, sending interface requests to the interface of the industrial software to be tested in sequence to obtain return information, and saving the interface error information; S3, cyclically performing UI menu inspection and interface request testing, monitoring configured server resources, and saving resource overrun information; S4, performing remote communication on the test results, page error information, interface error information and resource overrun information of long-term stability testing; The application further relates to a long-term stability test method for industrial software, which comprises the following steps: S11, creating a UI menu inspection instance to create a browser object and a page object; S12, automatically logging into the industrial software to be tested based on the browser object and the page object; S13, cyclically traversing all hierarchical menus of the industrial software to be tested to perform long-term stability testing, and starting error monitoring of the browser console; S14, if error information is monitored in the browser console, performing page screenshot to obtain page error information; S15, closing the browser and the UI menu inspection instance; S16, cyclically performing S11-S15 to continuously perform long-term stability testing.

2. The method of claim 1, wherein the industrial software is a software for a vehicle. The application further relates to a long-term stability test method for industrial software, which comprises the following steps:

3. The method of claim 2, wherein the industrial software is a software for a vehicle. S131, initializing a page menu sequence attribute; S132, obtaining a menu element based on the page menu sequence attribute, and obtaining a menu unique attribute based on the menu element; S133, clicking the menu according to the menu unique attribute and loading a corresponding page; S134, reobtaining the menu sequence attribute of the current menu after the page is loaded; S135, cyclically obtaining the menu sequence attribute of the next menu of the current menu, and repeating the above steps to continuously perform long-term stability testing on the page menu of the industrial software to be tested. The application further relates to a long-term stability test method for industrial software, which comprises the following steps:

4. The method for long-term stability testing of industrial software according to claim 3, characterized in that, determining whether the menu element exists, if the menu element does not exist, determining that the current menu sequence attribute corresponding menu is traversed; if the menu element exists, obtaining the menu unique attribute key corresponding to the current menu; if error information is monitored in the browser console, performing page screenshot to obtain page error information, which comprises the following steps:

5. The method of claim 3, wherein the industrial software is a software for a vehicle. if the browser console outputs error information, performing page screenshot; storing the menu unique attribute key for naming the page screenshot file; and sending the error information and the page screenshot file to a communication module. The application further relates to a long-term stability test method for industrial software, which comprises the following steps:

6. The method of claim 1-5, wherein the method is a long-term stability test method for industrial software, characterized in that, creating a UI menu inspection instance based on a playwrite module.

7. The method for long-term stability testing of industrial software according to claim 1, characterized in that, The interface request is sent to the interface of the industrial software to be tested in sequence, and the returned information and the saved returned interface error information are obtained, and the method specifically comprises the following steps: S21, logging in the industrial software, obtaining the user authentication permission of the industrial software, and storing the user authentication permission in the request header; S22, sending an interface request to the industrial software in sequence, wherein the interface is stored in an interface list in advance; S23, receiving the returned information of the test interface and storing it in the field res, judging the returned information of the interface, and sending the returned error information to the communication module; S24, logging out of the industrial software after executing all interface requests, and repeating S21-S24.

8. A test device for running the method of long-term stability testing of industrial software according to any one of claims 1 to 7, characterized in that At least comprising a long stability module, a monitoring module, and a communication module coupled with the long stability module and the monitoring module, The long stability module is used for long-term stability testing of the industrial software, and sends the long stability test data and abnormal information to the communication module, The long stability module comprises an independent and parallel inspection unit and an interface request unit; The inspection unit is used for traversing all hierarchical menus of the industrial software and performing error detection, and sends the abnormal information to the communication module; The interface request unit is used for testing the interface of the industrial software, and stores and sends the abnormal information to the communication module; The monitoring module is used for monitoring the server resources occupied by the industrial software during the running process of the long stability module, and sends the abnormal information to the communication module; The communication module is used for communicating the abnormal information fed back by the monitoring module and the long stability module, and testing data with the outside.

Images