Method and device for testing long-term stability of industrial software

Abstract

The invention discloses a method and a device for testing long-term stability of industrial software. The method comprises the following steps: configuring a server resource list to obtain server resources to be monitored; creating a UI menu inspection instance so as to simulate the operation of a user on a browser, traversing all hierarchical menus of the industrial software to be tested, and starting browser error reporting and monitoring so as to obtain page error information through screenshot; sending interface requests to the interfaces of the industrial software to be tested in sequence, obtaining return information, and storing returned interface error information; circularly performing UI menu inspection and interface request testing, monitoring the configured server resources, and storing resource overrun information; and performing remote communication on the test result of the long-term stability test, the page error information, the interface error information and the resource overrun information. The stability of existing software in long-term operation is comprehensively tested from UI, interfaces and resources, interference of human factors is reduced, standardization and automation of long-term stability testing are achieved, and testing efficiency and accuracy are improved.

Description

Technical Field

[0001] The present invention relates to the field of industrial software information testing, and in particular to a method and device for testing the long-term stability of industrial software. Background Art

[0002] Existing software may be unstable during long-term operation, and it is necessary to monitor the stability of all software systems over a long period of time. However, software stability testing is a relatively difficult test type in software testing, and it has cycle limitations, scenario limitations, and operational limitations.

[0003] The traditional long-term stability test method is only conducted manually, which has many human interference factors and cannot achieve standardization and automation of long-term stability testing.

[0004] A software stability testing method based on pyecharts is proposed in a Chinese invention patent. It only uses pyecharts to realize the chart display of test indicators.

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

[0006] In order to overcome the deficiencies of the above technologies, the present invention provides a method and device for long-term stability testing of industrial software, which comprehensively tests the stability of existing software in long-term operation from the perspective of UI, interface and resources, reduces interference from human factors, realizes standardization and automation of long-term stability testing, and improves test efficiency and accuracy.

[0007] The technical solution adopted by the present invention to overcome the technical problems is:

[0008] The first aspect of the present invention is to propose a method for testing the long-term stability of industrial software, including S1, creating a UI menu inspection instance to simulate the user's operation on the browser, traversing all the hierarchical menus of the industrial software to be tested and turning on the browser error monitoring to take a screenshot to obtain the page error information; S2, sending interface requests to the interfaces of the industrial software to be tested in turn and obtaining return information, and saving the returned interface error information; S3, cyclically performing UI menu inspection and interface request testing and monitoring the configured server resources, and saving resource overlimit information; S4, remotely communicating the test results of the long-term stability test, page error information, interface error information and resource overlimit information.

[0009] Through the menu attribute traversal page menu test, as well as the interface test and server resource monitoring of the industrial software to be tested, a comprehensive long-term stability test of the industrial software can be carried out

[0010] Furthermore, the invention provides a method for creating a UI menu inspection instance to simulate the user's operation on the browser, traverse all levels of menus of the industrial software to be tested, and enable browser error monitoring to obtain a screenshot of the page error information, which specifically includes: S11, creating a UI menu inspection instance to create a browser object and a page object; S12, automatically logging in to the industrial software to be tested based on the browser object and the page object; S13, looping through all levels of menus of the industrial software to be tested for long-term stable testing, and enabling error monitoring of the browser console; S14, if the browser console is monitored to output an error message, taking a screenshot of the page to obtain the page error information; S15, closing the browser and the UI menu inspection instance; S16, looping through S11-S15 to continue the long-term stable testing.

[0011] Furthermore, the automatic login to the industrial software to be tested based on the browser object and the page object specifically includes: looping through all levels of menus of the industrial software to be tested based on the page menu sequence attribute and the page menu unique attribute to perform long-term stability testing.

[0012] Furthermore, the method of looping through all levels of menus of the industrial software to be tested based on the page menu sequence attribute and the page menu unique attribute to perform long-term stability testing specifically includes: S131, initializing the page menu sequence attribute; S132, obtaining menu elements based on the page menu sequence attribute, and obtaining menu unique attributes based on the menu elements; S133, clicking the menu and loading the corresponding page according to the menu unique attribute; S134, re-obtaining the menu sequence attribute of the current menu after the page loading is completed; S135, looping to obtain the menu sequence attribute of the next menu of the current menu, and repeating the above, thereby continuously conducting long-term stability testing of the page menu of the industrial software to be tested.

[0013] Furthermore, the obtaining of the menu unique attribute based on the menu element specifically includes: determining whether the menu element exists; if the menu element does not exist, determining whether the traversal has completed the menu corresponding to the current menu sequence attribute; if the menu element exists, obtaining the menu unique attribute key corresponding to the current menu.

[0014] Furthermore, if the browser console outputs error information, a screenshot of the page is taken to obtain the page error information, specifically including: if the browser console outputs error information, a screenshot of the page is taken; the menu unique attribute key is stored for naming the file of the page screenshot; and the error information and the page screenshot file are sent to the communication module.

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

[0016] Furthermore, the interface requests are sent to the interfaces of the industrial software to be tested in turn and the return information is obtained, and the returned interface error information is saved, specifically including: S21, logging in to the industrial software, obtaining the user authentication authority of the industrial software, and storing the user authentication authority in the request header; S22, sending interface requests to the industrial software in turn, wherein the interfaces are pre-stored in the interface list. S23, receiving the return information of the test interface and storing it in the field res, and judging the return 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.

[0017] Another aspect of the present invention proposes a testing device for a long-term stability testing method for industrial software, which is used to run the above-mentioned testing device for the long-term stability testing method for industrial software. The testing device comprises at least a long-term stability module, a monitoring module, and a communication module respectively coupled to the long-term stability module and the monitoring module. The long-term stability module is used to perform long-term stability testing on the industrial software, and send the long-term stability test data and abnormal information to the communication module. The long-term stability module comprises an independent and parallel inspection unit and an interface request unit; the inspection unit is used to traverse all hierarchical menus of the industrial software and perform error detection, and send the abnormal information to the communication module; the interface request unit is used to test the interface of the industrial software, and store and send the 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 the 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 the test data with the outside.

[0018] Through the inspection unit and the interface request unit, menu testing and page testing are taken into account to achieve a comprehensive long-term stability test of the industrial software to be tested.

[0019] The beneficial effects of the present invention are:

[0020] The present invention proposes to conduct long-term stability testing of industrial software by traversing page menus through menu attribute tests, as well as interface testing and server resource monitoring of the industrial software to be tested. Traditional long-term stability testing methods are generally manual testing, which involves opening the industrial operating system for use and then continuing for a period of time. Compared with traditional long-term stability testing methods, the present invention realizes standardization and automation of long-term stability testing, improves test efficiency and accuracy, and reduces interference from human factors. At the same time, the device provides intuitive data analysis and abnormal response mechanisms to provide data support for later test reports. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A schematic diagram of a flow chart of a method for long-term stability testing of industrial software according to an embodiment of the present invention;

[0022] Figure 2 A schematic diagram of a process of traversing all levels of menus according to an embodiment of the present invention;

[0023] Figure 3 The present invention 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 DESCRIPTION

[0024] First, some abbreviations and key terms mentioned in the present invention are explained.

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

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

[0027] In order to facilitate those skilled in the art to better understand the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. The following is only exemplary and does not limit the protection scope of the present invention.

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

[0029] S1, create a UI menu inspection instance to simulate the user's operation on the browser, traverse all levels of menus of the industrial software to be tested and enable browser error monitoring to take a screenshot to obtain page error information.

[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(); the playwright.chromium.launch method is used to create a browser object, and finally a page object page=browser.new_page() is created.

[0032] Use playwright to simulate user operations on the browser, including logging in and clicking all menus in a loop after logging in.

[0033] S12, automatic login to industrial software based on browser objects and page objects

[0034] Based on the browser object, the PlayWrite instance automatically opens the login page of the industrial software. The user name and password are automatically entered through the page object to perform the login.

[0035] S13, loops through all levels of menus of the industrial software to be tested for long-term stability testing, and turns on error monitoring of the browser console.

[0036] After logging in, click all the hierarchical menus through the page object and enable error monitoring. When the page menu is lazy loaded each time and only one menu is expanded each time, the following specific process is used to effectively traverse all the hierarchical menus.

[0037] Since the page menu is not fully loaded at one time, for example, when a user logs in to the industrial software for the first time, only the first-level menu is loaded. When the user clicks on a menu, the submenu of the menu is dynamically loaded, and at the same time, the parent menu is expanded and the expanded menu is closed, and the menu order is rearranged. Therefore, when the menu is collapsed or expanded, the page menu order attribute, that is, the index attribute, will change dynamically.

[0038] In one embodiment of the present invention, the traversal of all menus is achieved through the page menu sequence attribute index and the page menu unique attribute key. When there is no click operation, the sequence attribute of the next menu is the sequence attribute of the current menu + 1. In the industrial information operating system, the menu unique attribute key is unique. The key is generally composed of the code of the APP module, a unique field specified in the software code. After clicking the menu and causing the menu to be rearranged, the current menu can be found through the key attribute. The general flow chart is as follows Figure 2 shown.

[0039] S131, initializing the page menu sequence attribute index.

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

[0041] S132, obtaining a menu element based on the page menu sequence attribute index, and obtaining a menu unique attribute based on the menu element.

[0042] In one embodiment of the present invention, the menu element is the entire menu, and the menu attributes can be obtained through the get_attribute() method, including the sequential attribute index and the unique attribute key. According to the page menu sequential attribute index, the menu element is obtained by using "div#menv>>div[data-index='{index}']". The element with this attribute and the correct value is found through the attribute and attribute value.

[0043] If the menu element does not exist, determine whether the menu corresponding to the current menu sequence attribute has been traversed.

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

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

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

[0047] It should be noted that by taking a screenshot of the page with a key, you can clearly know which menu reported the error and view the page display when the error occurred. You cannot use the menu name because the menu name may be repeated, and there is a risk that the screenshot file will be replaced. If there is no error, there is no need to take a screenshot and save the key.

[0048] S133, click the menu according to the menu's unique attribute key and load the corresponding page.

[0049] Use "div#menv>>div[data-key='{key}']" to click the menu according to the menu's unique attribute key.

[0050] S134, after the page is loaded, re-obtain the menu order attribute index of the current menu.

[0051] S135, loop to obtain the menu order attribute index of the next menu of the current menu, and repeat steps S232-S235 until the menus corresponding to the current menu order attribute are traversed.

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

[0053] S14, if the browser console outputs error information, a screenshot of the page is taken to obtain page error information.

[0054] When an error occurs on a page, the browser console will output an error message, i.e., msg.type=="error". At this time, a screenshot of the page is taken, and the screenshot file is named using the menu key.

[0055] It should be noted that error reporting does not affect subsequent testing.

[0056] S15, close the browser and close the UI menu inspection instance.

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

[0058] S16, repeating S11-S15, thereby continuing the long-term stability test.

[0059] It should be noted that the UI menu inspection instance can be implemented using other languages ​​and module libraries. The languages ​​can be python, java, c++, go, etc. The module libraries include but are not limited to playwright, selenium and its derivative libraries.

[0060] S2, sending interface requests to the interfaces of the industrial software to be tested in turn and obtaining return information, and saving the returned interface error information.

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

[0062] S21, access and log in to the industrial software through the interface, obtain the user authentication authority of the industrial software, and store the user authentication authority in the request header.

[0063] When requesting to log in to industrial software, the user authentication permission will be obtained, and then this permission will be added to the request header. Subsequent requests will carry headers, so that subsequent requests will have the permission to obtain data.

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

[0065] The interface list includes at least 4 fields: url, method, data, and headers.

[0066] Among them, url is the request address of the interface, and the interface request unit automatically splices 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. method is the request method of the interface, such as: get, post, put, etc.

[0068] data is the request body data of the interface, in json format. In order to avoid data duplication during interface request, data supports loop counter index and time function datetime. For example, when data is {"a":index, "b":datetime.now().timestamp()}, the parameter a=1 and parameter b=timestamp of the first loop will be passed in during the first loop, and the parameter a=2 and parameter b=timestamp of the second loop will be passed in during the second loop. The loop counter index can count according to user-defined rules, such as incrementing by 1, index=1 for the first request and index=2 for the second request.

[0069] Headers is the request header of the interface. This field is automatically generated by the interface request unit and contains the user authentication authority obtained by the login method to ensure that the subsequent requests have the authority to obtain data.

[0070] S23, the interface request unit receives the return information of the test interface and stores it in the field res, and determines the return information of the interface. If the response code res.status_code of the interface is not a 200 series response code, the error information returned by the interface is stored in a designated 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 executed, the logout operation is performed, and then the above operations are repeated.

[0073] S3, cyclically perform UI menu inspection and interface request test and monitor the configured industrial operating system server resources, and save resource overlimit information.

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

[0075] The industrial operating system is configured on the server. After it is released, users can access it locally through a browser. Users create server resources to be monitored in the server resource list. The server resource list includes 7 fields, namely name, command, regular expression, time interval, upper alarm value, lower alarm value, and enable. The fields are shown in Table 1. The following steps are mainly used to monitor server resources.

[0076] Table 1

[0077]

[0078]

[0079] S32, create a remote server and connect to the industrial operating system server through the connect function.

[0080] In one embodiment of the present invention, the long-term stable testing 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 to be tested. The information required to connect to the remote server is the information of the industrial operating system server, including the server IP, port, user name and password.

[0081] S33, obtaining server resource information based on a preset time interval and saving it until the long-term stability test is completed.

[0082] In one embodiment of the present invention, after connecting to the server, the exec_command function is used to execute the Linux command, and the output result of the command execution is processed using a regular expression to obtain the information of the server resource. The query is cyclically performed at a time interval, and the queried value is stored in a table until the long-term stability test is completed.

[0083] S34, compare the saved result with the preset threshold value. If the preset threshold value 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] When the preset threshold is exceeded, that is, the server resource triggers an alarm, the server resource name, real-time value, and alarm value that triggers the alarm are sent to the communication module.

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

[0086] Long-term test data includes but is not limited to: UI inspection execution times, interface list and execution times of interface requests, server resource data table, exception information summary, etc.

[0087] like Figure 3As shown, the long-term stability testing device described in another embodiment of the present invention at least includes a long-term stability module, a monitoring module, and a communication module respectively coupled to the long-term stability module and the monitoring module. The long-term stability module is used to perform long-term stability testing on the industrial software, and send the 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 hierarchical menus of the industrial software and perform error detection, and send the abnormal information to the communication module; the interface request unit is used to test the interface of the industrial software, and store and send the 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 the 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 the test data with the outside.

[0088] The long-term stability module is the core execution module of the long-term stability test, which is used to perform long-term stability tests on the software and send long-term stability test data and abnormal information to the communication module. The long-term stability module includes a patrol unit and an interface request unit, which are used to run two independent parallel threads.

[0089] The interface request unit in the Changwen module is used to test the interface of the industrial software and store and send the abnormal information to the communication module. The interface request unit sends the request directly through the interface. It needs to make a login request first, obtain the user authentication authority, and then request the interface to be tested in turn.

[0090] The monitoring module is used to monitor the server resources during the operation of the long-term stable module and send abnormal information to the communication module. The communication module is used to communicate the abnormal information of the monitoring module and the long-term stable module with the outside world. It realizes the monitoring of the server resources occupied by the industrial software during the operation of the long-term stable module.

[0091] In one embodiment of the present invention, the communication module can be configured to communicate with users in real time through enterprise WeChat, DingTalk, email, SMS, etc. When the long-term 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 to inform the abnormal situation in the long-term stability test. When the long-term stability test is completed, the communication module will also send the long-term stability test data to the user. The long-term stability test data includes but is not limited to: the number of UI inspection executions, the interface list and execution times of the interface request, the server resource data table, and the abnormal information summary.

[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: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0094] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The system and system embodiment described above are only illustrative, and some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

Claims

1. A method for testing the long-term stability of industrial software, characterized in that: include: S1, create a UI menu inspection instance to simulate the user's operation on the browser, traverse all levels of menus of the industrial software to be tested and enable browser error monitoring to take a screenshot to obtain page error information; S2, sending interface requests to the interfaces of the industrial software to be tested in turn and obtaining return information, and saving the returned interface error information; S3, cyclically performing UI menu inspection and interface request testing and monitoring the configured server resources, and saving resource overlimit information; S4, remotely communicates the test results of the long-term stability test, page error information, interface error information and resource limit excess information.

2. The method for testing the long-term stability of industrial software according to claim 1, characterized in that: The creation of a UI menu inspection instance to simulate the user's operation on the browser, traversing all levels of menus of the industrial software to be tested and enabling browser error monitoring to obtain a screenshot of the page error information specifically includes: S11, create a UI menu inspection instance, thereby creating a browser object and a page object; S12, automatically log in to the industrial software to be tested based on the browser object and the page object; S13, loop through all levels of menus of the industrial software to be tested for long-term stability testing, and enable error monitoring of the browser console; S14, if the browser console outputs error information, a screenshot of the page is taken to obtain the page error information; S15, close the browser and close the UI menu inspection instance; S16, execute S11-S15 cyclically to continuously perform long-term stability test.

3. The method for testing the long-term stability of industrial software according to claim 2, characterized in that: The automatic login to the industrial software to be tested based on the browser object and the page object specifically includes: looping through all levels of menus of the industrial software to be tested to perform long-term stability testing based on the page menu sequence attribute and the page menu unique attribute.

4. The method for long-term stability testing of industrial software according to claim 3, characterized in that: The method of looping through all levels of menus of the industrial software to be tested based on the page menu sequence attribute and the page menu unique attribute to perform long-term stability testing specifically includes: S131, initializing page menu sequence attributes; S132, obtaining menu elements based on the page menu sequence attribute, and obtaining menu unique attributes based on the menu elements; S133, click the menu according to the unique attribute of the menu and load the corresponding page; S134, after the page is loaded, re-obtain the menu order attribute of the current menu; S135, cyclically obtaining the menu sequence attribute of the next menu of the current menu, and repeating the above, thereby continuously performing the long-term stability test of the page menu of the industrial software to be tested.

5. The method for testing the long-term stability of industrial software according to claim 4, characterized in that: The method of obtaining a unique attribute of a menu based on a menu element specifically includes: Determine whether the menu element exists. If the menu element does not exist, determine whether the menu corresponding to the current menu order attribute has been traversed; If the menu element exists, get the unique menu attribute key corresponding to the current menu.

6. The method for long-term stability testing of industrial software according to claim 4, characterized in that: If the browser console outputs error information, take a screenshot of the page to obtain the page error information, including: If the browser console outputs an error message, take a screenshot of the page; The unique attribute key of the storage menu is used to name the file of the page screenshot; And send the error message and page screenshot file to the communication module.

7. A method for testing the long-term stability of industrial software according to any one of claims 1 to 6, characterized in that: Create a UI menu inspection instance based on the playwrite module.

8. The method for long-term stability testing of industrial software according to claim 1, characterized in that: The step of sequentially sending interface requests to the interfaces of the industrial software to be tested and obtaining returned information, and saving the returned interface error information, specifically includes: S21, log in to the industrial software, obtain the user authentication authority of the industrial software, and store the user authentication authority in the request header; S22, sending interface requests to the industrial software in sequence, wherein the interfaces are pre-stored in the interface list. S23, receiving the return information of the test interface and storing it in the field res, and judging the return information of the interface, and sending the returned error information to the communication module; S24, after executing all interface requests, log out of the industrial software and repeat S21-S24.

9. A testing device for running the industrial software long-term stability testing method according to any one of claims 1 to 8, characterized in that: At least includes 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 tests on industrial software and send long-term stability test data and abnormal information to the communication module. The long-stable 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 the 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 stable 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, as well as the test data to the outside.

Images