Report system smoke test method, RPA robot and system
By applying RPA technology in the smoke testing of the report system, the problems of low efficiency and poor accuracy of manual testing in the existing technology are solved, and a more efficient and accurate testing process is achieved, improving the user experience.
Patent Information
- Application Number
- CN202110526327.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-05-14
- Publication Date
- 2025-05-02
- Estimated Expiration
- 2041-05-14
AI Technical Summary
The smoke testing methods of existing reporting systems mainly rely on manual labor, and there are problems such as repetition of steps, high workload and easy to miss test scenarios, resulting in a decrease in testing efficiency and accuracy.
Using RPA technology, the unified authentication interface of the reporting system is logged in by RPA login test scripts, and interface passivity tests, report data function tests and user management function tests are carried out based on RPA target test scripts.
It effectively improves the efficiency and accuracy of the smoke-filled testing process of the report system, avoids the omissions of test scenarios and the repetition of test steps, and improves the user experience of test technicians.
Smart Images

Figure CN113127370B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, in particular to the field of artificial intelligence technology, and specifically to a report system smoke test method, an RPA robot and system. Background Art
[0002] With the rapid development of Internet finance, the speed of innovation and change of financial enterprises such as banks is also accelerating to meet the ever-changing needs of customers. The overall update and iteration cycle of application version development, testing, and production corresponding to innovation and change is getting shorter and shorter. Among them, most financial enterprises will adopt reporting systems to achieve data management by combining computer technology with accounting report preparation methods. In order to ensure the application reliability of the reporting system, the reporting system needs to be tested. Smoke testing, as the entry threshold for software testing, requires testing the basic functions and most important business processes of the version, which helps to discover problems in the version code as early as possible. Therefore, smoke testing of the reporting system can improve the quality of reporting system version development and testing efficiency.
[0003] However, as the speed of iteration and update of the reporting system application version increases, the pressure of smoke testing work also increases; the existing smoke testing method of the reporting system mainly relies on manual methods, which usually have problems such as repeated steps, large workload and easy omission of test scenarios. In addition, it is easy to omit and make mistakes during the process of manually obtaining, processing and checking data item by item, resulting in reduced test efficiency and accuracy. Summary of the invention
[0004] In response to the problems in the prior art, the present application provides a reporting system smoke testing method, an RPA robot and a system, which can effectively improve the efficiency of the reporting system smoke testing process, and can effectively improve the accuracy and reliability of the smoke testing of the reporting system.
[0005] In order to solve the above technical problems, this application provides the following technical solutions:
[0006] In a first aspect, the present application provides a report system smoke test method, comprising:
[0007] Perform login test on the unified authentication interface of the reporting system based on the RPA login test script;
[0008] If the unified authentication interface passes the login test, the report system is subjected to a target test based on the RPA target test script, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0009] Furthermore, the RPA login test script is used to perform a login test on the unified authentication interface of the reporting system, including:
[0010] Receive an RPA login test script, wherein the RPA login test script includes a login account, password, and application front-end address of the unified authentication interface;
[0011] Execute the RPA login test script to perform a login test on the unified authentication interface based on the login account, password and application foreground address of the unified authentication interface.
[0012] Furthermore, the RPA target test script includes: an RPA interface passability test script;
[0013] Correspondingly, the target test of the reporting system based on the RPA target test script includes:
[0014] Receiving an RPA interface passability test script, wherein the RPA interface passability test script includes an identifier of each target interface in the reporting system;
[0015] The RPA interface passability test script is executed to traverse each of the target interfaces and perform interface passability tests on each of the target interfaces based on the identifiers of each of the target interfaces.
[0016] Furthermore, the RPA target test script includes: an RPA report function test script;
[0017] Correspondingly, the target test of the reporting system based on the RPA target test script includes:
[0018] receiving an RPA report function test script, wherein the RPA report function test script includes a region, an institution, and a currency to be queried;
[0019] Execute the RPA report function test script to log in to the report query interface in the report system, and perform a report data function test on the report query interface based on the region, institution and currency to be queried, wherein the report data function test includes: report data query test and report data download test.
[0020] Furthermore, the report data function test also includes: report logic verification test; the RPA report function test script also includes: report logic verification rules;
[0021] Correspondingly, the report system smoke test method also includes:
[0022] If the report data corresponding to the region, organization and currency to be queried is downloaded through the report data download test, the RPA report function test script is executed again to perform the report logic verification test on the report data based on the report logic verification rules.
[0023] Further, the report logic verification test includes: verification and checking test of report data in a single report and / or across multiple reports;
[0024] The verification test includes at least one of: total score verification, data format verification, calculation result verification and data timeliness verification.
[0025] Further, the RPA target test script includes: an RPA user management function test script;
[0026] Correspondingly, the target test of the reporting system based on the RPA target test script includes:
[0027] Receive an RPA user management function test script, wherein the RPA user management function test script includes each user ID to be tested and a system permission requirement corresponding to each user ID;
[0028] Execute the RPA user management function test script to log in to the user management interface in the reporting system, and perform a user management function test on the user management interface based on each user ID to be tested and the system permission requirements corresponding to each user ID, wherein the user management function test includes: at least one of: adding a new user test, a user permission test, and deleting a user test.
[0029] Further, the user management interface in the logging-in reporting system is tested for user management functions based on each user ID to be tested and the system authority requirements corresponding to each user ID, including:
[0030] Using an administrator account in the user management interface of the reporting system, based on each user ID to be tested and the system authority requirements corresponding to each user ID, add corresponding users to perform the added user test;
[0031] Log out of the administrator account, and log in to each of the newly added user accounts one by one to perform the user authority test on each of the newly added user accounts;
[0032] Use the administrator account again to delete the newly added accounts of each user in the user management interface to perform the user deletion test.
[0033] Furthermore, it also includes:
[0034] Generate a smoke test report for the reporting system according to the test results corresponding to the login test and the target test respectively;
[0035] Output the smoke test report.
[0036] In a second aspect, the present application provides an RPA robot, including:
[0037] The login test module is used to perform login tests on the unified authentication interface of the reporting system based on the RPA login test script;
[0038] The target test module is used to perform a target test on the reporting system based on the RPA target test script if the unified authentication interface passes the login test, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0039] In a third aspect, the present application provides a report system smoke test system, including: a management device and multiple RPA robots;
[0040] The RPA robot is used to execute the report system smoke test method;
[0041] The management device is used to send the RPA login test script and the RPA target test script to each of the RPA robots, and receive a smoke test report for the reporting system sent by each of the RPA robots.
[0042] In a fourth aspect, the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the report system smoke test method when executing the program.
[0043] In a fifth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the report system smoke test method when executed by a processor.
[0044] It can be seen from the above technical solution that the present application provides a report system smoke test method, RPA robot and system, the method includes: based on the RPA login test script, the unified authentication interface of the report system is logged in to test; if the unified authentication interface passes the login test, the report system is targeted based on the RPA target test script, wherein the target test includes: at least one of the interface passability test, report data function test and user management function test. By applying RPA technology to the report system smoke test, the efficiency of the report system smoke test process can be effectively improved, and the accuracy and reliability of the smoke test for the report system can be effectively improved. It can effectively avoid the omission of test scenarios and the duplication of test steps, and thus effectively improve the user experience of the test technicians of the report system, and realize one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke tests of other application systems, which has great promotion value. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0046] Figure 1 It is a flowchart of the smoke test method of the reporting system in the embodiment of the present application.
[0047] Figure 2 It is a flowchart of step 100 in the smoke testing method of the reporting system in the embodiment of the present application.
[0048] Figure 3 This is a first flow chart of step 200 in the report system smoke test method in the embodiment of the present application.
[0049] Figure 4 This is a second flow chart of step 200 in the report system smoke test method in the embodiment of the present application.
[0050] Figure 5 This is a third flow chart of step 200 in the report system smoke test method in the embodiment of the present application.
[0051] Figure 6 This is a fourth flow chart of step 200 in the report system smoke test method in the embodiment of the present application.
[0052] Figure 7It is a flowchart of steps 271 to 273 in the report system smoke test method in an embodiment of the present application.
[0053] Figure 8 It is a flowchart of a smoke test method for a reporting system including step 300 and step 400 in an embodiment of the present application.
[0054] Fig. 9 It is a structural diagram of the RPA robot in the embodiment of the present application.
[0055] Fig.10 It is a flowchart of the RPA-based report system smoke testing method in the application example of this application.
[0056] Fig.11 It is a schematic diagram of the execution logic of the interface passability test module in the application example of this application.
[0057] Fig.12 It is a schematic diagram of the execution logic of the report function module in the application example of this application.
[0058] Fig.13 It is a schematic diagram of the execution logic of the user management module in the application example of this application.
[0059] Fig.14 It is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION
[0060] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0061] It should be noted that the report system smoke test method, RPA robot and system disclosed in this application can be used in the field of artificial intelligence technology, and can also be used in any field outside the field of artificial intelligence technology. The application field of the report system smoke test method, RPA robot and system disclosed in this application is not limited.
[0062] Considering that the existing smoke testing method of the reporting system mainly relies on manual methods, there are usually problems such as repeated steps, heavy workload and easy omission of test scenarios, and it is easy to omit and make mistakes in the process of manually obtaining data, processing and checking one by one, resulting in problems such as reduced test efficiency and accuracy. The embodiments of the present application respectively provide a reporting system smoke testing method, an RPA robot, a reporting system smoke testing system, and a computer-readable storage medium for electronic equipment, which can perform a login test on the unified authentication interface of the reporting system based on the RPA login test script; if the unified authentication interface passes the login test, the reporting system is subjected to a target test based on the RPA target test script, wherein the target Standard tests include: at least one of the following: interface passability test, report data function test, and user management function test. By applying RPA technology to the smoke test of the report system, the efficiency of the smoke test process of the report system can be effectively improved, and the accuracy and reliability of the smoke test for the report system can be effectively improved, thereby effectively improving the automation and intelligence of the smoke test process of the report system; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the report system, and realizing one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in the smoke test of other application systems, which has great promotion value.
[0063] In one or more embodiments of the present application, RPA robots or RPA robotic process automation (Robotic process automation) refers to devices that can replace or assist humans in completing repetitive work and tasks in digital devices such as computers and mobile phones. As long as the usage rules are designed in advance, RPA can simulate manual work, perform operations such as copying, pasting, clicking, and inputting, and assist humans in completing a large number of "relatively fixed rules and high repetitiveness" tasks, reduce manual errors, improve testing efficiency, and reduce testing costs. In specific application scenarios, RPA robots can be specifically embodied as client devices, etc.
[0064] Based on the above content, the present application also provides a reporting system smoke test device for implementing the reporting system smoke test method provided in one or more embodiments of the present application, and the reporting system smoke test device can be an RPA robot, and the RPA robot can communicate and connect with the client device held by the tester by itself or through a third-party server, etc., to receive the RPA scripts to be executed sent by the client devices corresponding to each tester, so that the RPA robot performs a login test on the unified authentication interface of the reporting system based on the RPA login test script in the RPA script; if the unified authentication interface passes the login test, the RPA robot performs a login test on the unified authentication interface based on the RPA login test script in the RPA script. The RPA target test script performs a target test on the reporting system, wherein the target test includes: at least one of an interface passability test, a report data function test, and a user management function test; then, the RPA robot generates a smoke test report for the reporting system according to the test results corresponding to the login test and the target test respectively; and sends the smoke test report to the client device of the corresponding tester, so that the client device focuses on displaying the error information that the reporting system fails the smoke test, etc., so that the technical personnel can understand the error information in time to locate and troubleshoot the problem, expose the problem in advance before the business test, and improve the version readiness efficiency of the reporting system.
[0065] It is understandable that the client device may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a personal digital assistant (PDA), a vehicle-mounted device, a smart wearable device, etc. Among them, the smart wearable device may include smart glasses, a smart watch, a smart bracelet, etc.
[0066] The client device may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission with the server. The server may include a server on the task scheduling center side, and other implementation scenarios may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, or a server cluster consisting of multiple servers, or a server structure of a distributed device.
[0067] The server and the client device may communicate with each other using any suitable network protocol, including network protocols that have not yet been developed on the date of filing this application. The network protocols may include, for example, TCP / IP, UDP / IP, HTTP, HTTPS, etc. Of course, the network protocols may also include, for example, RPC (Remote Procedure Call Protocol) and REST (Representational State Transfer) protocols used on top of the above protocols.
[0068] The details are described in detail through the following embodiments and application examples.
[0069] In order to solve the problems of low efficiency and poor accuracy in the existing reporting system testing method, the present application provides an embodiment of a reporting system smoke testing method, see Figure 1 The report system smoke test method performed by the RPA robot specifically includes the following contents:
[0070] Step 100: Perform a login test on the unified authentication interface of the reporting system based on the RPA login test script.
[0071] In step 100, the RPA robot may receive a preset RPA login test script from a client device held by a tester, and then execute the RPA login test script to perform a login test on the unified authentication interface of the reporting system.
[0072] Step 200: If the unified authentication interface passes the login test, the report system is subjected to a target test based on the RPA target test script, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0073] If the existing report system test method is used to perform interface passability test, report data function test and user management function test, the following problems will occur in interface passability test, report data function test and user management function test:
[0074] 1. In the interface passability test, it is necessary to log in to the system and traverse the target test interface to check the passability. There are problems such as repeated steps, heavy workload, and easy omission of test scenarios.
[0075] 2. In the report function test, the workload of checking and verifying the report data is relatively large. During the test, it is necessary to obtain data from multiple databases or reports according to the data processing requirements in the report, and then process it according to the calculation logic and check it with the report data exported by the system. The workload is large, and it is easy to omission and make mistakes during the manual data collection, processing and verification, resulting in reduced test efficiency and accuracy.
[0076] 3. In the user management function test, it is required to test users with different roles or permissions to ensure that the report data permissions are controllable. It is necessary to manually add different users in the system, use each type of user to log in to the system separately, and check the compliance of the actual login interface according to different user permission settings to verify the user addition and deletion functions and permission control functions. There are many repetitive tasks and low efficiency.
[0077] Therefore, in step 200, the RPA robot is used to execute the RPA target test scripts corresponding to the interface passability test, the report data function test and the user management function test, respectively, to automatically perform target testing on the report system.
[0078] It is understandable that in a preferred embodiment of step 200, if the unified authentication interface passes the login test, the report system is subjected to interface passability test, report data function test and user management function test respectively based on the RPA target test script, wherein the execution order of the report data function test and the user management function test is not specific. In addition, the target test mentioned in one or more embodiments of the present application is not limited to the interface passability test, report data function test and user management function test, and the target test may include various types of tests that can be used to perform smoke tests on the report system.
[0079] From the above description, it can be seen that the report system smoke test method provided in the embodiment of the present application can effectively improve the efficiency of the report system smoke test process by applying RPA technology to the report system smoke test, and can effectively improve the accuracy and reliability of the smoke test for the report system, thereby effectively improving the automation and intelligence of the report system smoke test process; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the report system, and realizes one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke testing of other application systems, which has great promotion value.
[0080] In order to improve the accuracy and reliability of the unified authentication interface login test, an embodiment of the report system smoke test method provided in this application is provided. Figure 2An implementation of step 100 in the report system smoke test method specifically includes the following contents:
[0081] Step 110: Receive an RPA login test script, wherein the RPA login test script includes the login account, password and application front-end address of the unified authentication interface.
[0082] Step 120: Execute the RPA login test script to perform a login test on the unified authentication interface based on the login account, password and application front-end address of the unified authentication interface.
[0083] Specifically, the RPA robot sets the unified authentication account, password, application front-end address, and each system interface that needs to be traversed in the script for pass verification. The RPA robot automatically uses the unified authentication account and password to log in to the report application front-end address for system login verification, and then judges the login to the unified authentication interface. If the test is normal, execute step 200.
[0084] From the above description, it can be seen that the reporting system smoke test method provided in the embodiment of the present application can effectively improve the accuracy and reliability of the unified authentication interface login test of the reporting system by performing a login test on the unified authentication interface of the reporting system according to the received login account, password and application foreground address of the unified authentication interface, and can further improve the automation and intelligence of the reporting system smoke test process.
[0085] In order to improve the accuracy and reliability of the interface passability test, in one embodiment of the report system smoke test method provided in the present application, the RPA target test script includes: an RPA interface passability test script; see Figure 3 Step 200 in the report system smoke test method specifically includes the following contents:
[0086] Step 210: Receive an RPA interface passability test script, wherein the RPA interface passability test script includes identifiers of each target interface in the reporting system.
[0087] Step 220: Execute the RPA interface passability test script to traverse each of the target interfaces and perform interface passability tests based on the identifiers of each of the target interfaces.
[0088] Specifically, the RPA robot traverses the target test page to check whether the main page functions normally.
[0089] From the above description, it can be seen that the reporting system smoke testing method provided in the embodiment of the present application can effectively improve the accuracy and reliability of the RPA interface pass test of each target interface in the reporting system by performing an RPA interface pass test on each target interface according to the identifier of each target interface in the received reporting system, and can further improve the automation and intelligence level of the reporting system smoke testing process.
[0090] In order to improve the accuracy and reliability of report data function testing, in one embodiment of the report system smoke test method provided in this application, the RPA target test script includes: RPA report function test script; see Figure 4 Step 200 in the report system smoke test method further specifically includes the following contents:
[0091] Step 230: Receive an RPA report function test script, wherein the RPA report function test script includes a region, institution, and currency to be queried.
[0092] Step 240: Execute the RPA report function test script to log in to the report query interface in the report system, and perform a report data function test on the report query interface based on the region, institution and currency to be queried, wherein the report data function test includes: report data query test and report data download test.
[0093] Specifically, the RPA robot sets the region, institution and currency to be queried in the script to complete report query and download. That is, the RPA robot logs in to the report query interface, and automatically fills in the report query conditions, such as report region, institution, currency, etc., and downloads the corresponding report to the specified directory after the data is ready.
[0094] From the above description, it can be seen that the reporting system smoke test method provided in the embodiment of the present application can effectively improve the accuracy and reliability of the report data query and download function test in the reporting system by performing report data query and download function test on the report query interface according to the received region, institution and currency to be queried, and can further improve the automation and intelligence level of the reporting system smoke test process.
[0095] In order to further improve the accuracy and reliability of the report data function test, in an embodiment of the report system smoke test method provided in the present application, the report data function test also includes: report logic verification test; the RPA report function test script also includes: report logic verification rules; see Figure 5 , the report system smoke test method further specifically includes the following contents after step 240:
[0096] Step 250: If the report data corresponding to the region, organization and currency to be queried is downloaded through the report data download test, the RPA report function test script is executed again to perform the report logic verification test on the report data based on the report logic verification rules.
[0097] Specifically, after the RPA robot sets the region, institution, and currency to be queried in the script to complete the report query and download, it tests and verifies the report data according to the corresponding report business test logic. For example, a bank's daily report on foreign exchange settlement and sales statistics performs a simple check on basic content such as the total settlement and total sales to check whether the logic is correct. That is, open the downloaded report, read the specified verification rules in the script, and verify the report data. The verification rules are divided into data verification tests within a single report and data verification tests across files.
[0098] From the above description, it can be seen that the report system smoke test method provided in the embodiment of the present application can effectively improve the accuracy and reliability of the report logic verification test on the report data in the report system by performing a report logic verification test on the downloaded report data according to the received report logic verification rules, and can further improve the automation and intelligence level of the report system smoke test process.
[0099] In order to further improve the comprehensiveness and wide applicability of report logic verification testing on report data in a report system, in an embodiment of a report system smoke testing method provided in the present application, the report logic verification test includes: verification and verification testing of report data across reports in a single report and / or between multiple reports; the verification and verification test includes: at least one of total score verification, data format verification, calculation result verification and data timeliness verification.
[0100] Specifically, the verification rules are divided into data verification tests within a single report and data verification tests across files. Test verification includes total score verification, data format verification, calculation result verification, and data timeliness verification.
[0101] In a specific example, performing the report logic verification test on the report data based on the report logic verification rules means performing verification and checking tests on the report data in a single report and performing total score verification, data format verification, calculation result verification and data timeliness verification on the report data across multiple reports based on the report logic verification rules.
[0102] From the above description, it can be seen that the report system smoke test method provided in the embodiment of the present application, by designing a variety of verification tests, realizes the verification test of report data across a single report and multiple reports, which can further improve the accuracy, reliability, comprehensiveness and wide applicability of report logic verification test on report data in the report system, and can further improve the automation and intelligence of the report system smoke test process.
[0103] In order to improve the accuracy and reliability of user management function testing, in one embodiment of the report system smoke test method provided in this application, the RPA target test script includes: RPA user management function test script; see Figure 6 Step 200 in the report system smoke test method further specifically includes the following contents:
[0104] Step 260: Receive an RPA user management function test script, wherein the RPA user management function test script includes each user ID to be tested and the system permission requirements corresponding to each user ID.
[0105] Step 270: Execute the RPA user management function test script to log in to the user management interface in the reporting system, and perform a user management function test on the user management interface based on each user ID to be tested and the system permission requirements corresponding to each of the user IDs, wherein the user management function test includes: at least one of: adding a new user test, a user permission test, and deleting a user test.
[0106] Specifically, the test user name and corresponding permission control requirements are set in the script. The RPA robot tests the addition of new users, user validity, user permission control, etc. on the user management page. After successful verification, the fixed user is recovered from the database for use in the next smoke test cycle.
[0107] From the above description, it can be seen that the reporting system smoke testing method provided in the embodiment of the present application can effectively improve the accuracy and reliability of the user management function test in the reporting system by performing a user management function test on the user management interface according to the received user identifiers to be tested and the system permission requirements corresponding to each user identifier, and can further improve the automation and intelligence of the reporting system smoke testing process.
[0108] In order to further improve the accuracy and reliability of user management function testing, an embodiment of the report system smoke test method provided in this application is provided. Figure 7 Step 270 in the report system smoke test method further specifically includes the following contents:
[0109] Step 271: Using an administrator account in the user management interface of the report system, based on each user ID to be tested and the system authority requirements corresponding to each user ID, add corresponding users to perform the added user test.
[0110] Step 272: Log out of the administrator account, and log in to each of the newly added user accounts one by one to perform the user authority test on each of the newly added user accounts.
[0111] Step 273: Use the administrator account to delete each of the newly added user accounts in the user management interface again to perform the user deletion test.
[0112] Specifically, after the RPA robot successfully logs in to the unified authentication with administrator privileges, it enters the user management interface, adds multiple test users and sets corresponding privileges, tests the newly added user functions, and records the test results; after logging out of the administrator user, it cycles through each account to test whether each newly added user can log in normally, and whether the function module after login meets the corresponding privilege requirements, and records the test results. For example: when adding a branch user, check whether he has the privilege to view the head office-side report, whether he has the system management privilege, etc. After all test users have logged in and verified, log in to the system again with administrator privileges, enter the user management module, delete all test accounts, and verify the function of deleting users.
[0113] From the above description, it can be seen that the reporting system smoke testing method provided in the embodiment of the present application can further improve the comprehensiveness, wide applicability and reliability of the user management function testing in the reporting system by performing tests on user addition, permissions and deletion respectively during the user management function testing process, and can further improve the automation and intelligence of the reporting system smoke testing process.
[0114] In order to enable technical personnel to understand the error information in time to locate and troubleshoot the problem, an embodiment of the smoke test method of the report system provided in this application is provided. Figure 8 The report system smoke test method further specifically includes the following contents after step 100 or 200:
[0115] Step 300: Generate a smoke test report for the reporting system according to the test results corresponding to the login test and the target test respectively.
[0116] Step 400: Output the smoke test report.
[0117] From the above description, it can be seen that the reporting system smoke testing method provided in the embodiment of the present application, by outputting smoke test reports of login test and target test, can enable technical personnel to timely understand the error information to locate and troubleshoot the problem, expose the problem in advance before business testing, and thus effectively improve the online efficiency of the reporting system version.
[0118] From the software level, in order to solve the problems of low efficiency and poor accuracy in the existing reporting system testing method, the present application provides an embodiment of an RPA robot for executing all or part of the content of the reporting system smoke test method, see Fig. 9 , the RPA robot specifically includes the following contents:
[0119] The login test module 10 is used to perform a login test on the unified authentication interface of the reporting system based on the RPA login test script.
[0120] In the login test module 10, the RPA robot can receive a preset RPA login test script from a client device held by the tester, and then execute the RPA login test script to perform a login test on the unified authentication interface of the reporting system.
[0121] The target test module 20 is used to perform a target test on the reporting system based on the RPA target test script if the unified authentication interface passes the login test, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0122] In the target test module 20, an RPA robot is used to execute the RPA target test scripts corresponding to the interface passability test, the report data function test and the user management function test, respectively, to automatically perform target testing on the report system.
[0123] It is understandable that in a preferred embodiment of the target test module 20, if the unified authentication interface passes the login test, the report system is subjected to an interface passability test, a report data function test, and a user management function test based on the RPA target test script, wherein the execution order of the report data function test and the user management function test is not specific. In addition, the target test mentioned in one or more embodiments of the present application is not limited to the interface passability test, the report data function test, and the user management function test, and the target test may include various types of tests that can be used to perform smoke tests on the report system.
[0124] The embodiment of the RPA robot provided in this application can be specifically used to execute the processing flow of the embodiment of the report system smoke test method in the above embodiment. Its functions are not repeated here, and reference can be made to the detailed description of the above method embodiment.
[0125] From the above description, it can be seen that the RPA robot provided in the embodiment of the present application can effectively improve the efficiency of the smoke test process of the reporting system by applying RPA technology to the smoke test of the reporting system, and can effectively improve the accuracy and reliability of the smoke test for the reporting system, thereby effectively improving the automation and intelligence of the smoke test process of the reporting system; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the reporting system, and realizes one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke tests of other application systems, which has great promotion value.
[0126] Based on the above-mentioned embodiment of the RPA robot, in order to solve the problems of low efficiency and poor accuracy of the existing reporting system testing method, the present application provides an embodiment of a reporting system smoke test system including an RPA robot, and the reporting system smoke test system specifically includes the following contents:
[0127] A management device and multiple RPA robots; the RPA robots are used to execute the report system smoke test method; the management device can be a client device held by the aforementioned tester, and the management device is used to send the RPA login test script and the RPA target test script to each of the RPA robots respectively, and receive the smoke test report for the report system sent by each of the RPA robots.
[0128] The embodiment of the reporting system smoke test system provided in the present application can be specifically used to execute the processing flow of the reporting system smoke test method or the RPA robot embodiment in the above-mentioned embodiment. Its functions are not repeated here, and reference can be made to the detailed description of the above-mentioned method or RPA robot embodiment.
[0129] From the above description, it can be seen that the report system smoke test system provided in the embodiment of the present application can effectively improve the efficiency of the report system smoke test process by applying RPA technology to the report system smoke test, and can effectively improve the accuracy and reliability of the smoke test for the report system, thereby effectively improving the automation and intelligence of the report system smoke test process; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the report system, and realizes one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke tests of other application systems, which has great promotion value.
[0130] In order to further illustrate this solution, this application also provides a specific application example of the smoke test method for the report system. Through the interface passability test module, it is possible to automatically log in to the report system and traverse the target test page to check the passability; through the report function module, it is possible to realize the business logic verification functions of report query, download and report data; through the user management module, it is possible to complete the user addition and deletion functions and authority control verification. Ultimately, RPA technology replaces repetitive and complicated manual operations and realizes the purpose of automating the smoke test process.
[0131] RPA (Robotic Process Automation) can be a third-party software purchased by a bank. It can simulate most manual operations and realize process automation by flexibly configuring task components, judgment logic, execution order, etc. This application provides a method for realizing automated smoke testing in the software testing process based on RPA function, using RPA to replace manual automation to complete application system authentication login test, report query and export test, report data verification, user addition and deletion test and user authority verification. Fig.10 , where "N" stands for No and "Y" stands for Yes; the specific processing flow includes:
[0132] Step 1: Interface passability test module, see Fig.11 , set the unified authentication account, password, application front-end address and each system interface that needs to be traversed in the script for pass verification. The details are as follows:
[0133] Step 1.1: RPA automatically uses the unified authentication account and password to log in to the report application front-end address for system login verification.
[0134] Step 1.2: Check the login unified authentication interface. If the test is normal, proceed to step 1.3; otherwise, jump to step 6.
[0135] Step 1.3: Traverse the target test page to check whether the main page functions are normal.
[0136] Step 2: Report function module, see Fig.12 The report function module is divided into three parts: report query, report download and report logic verification. After setting the region, institution and currency to be queried in the script to complete the report query and download, test and verify the report data according to the corresponding report business test logic, such as total score verification, data format verification, calculation result verification and data timeliness verification. For example, a bank's daily report on foreign exchange settlement and sales statistics performs a simple verification of basic contents such as the total settlement and total sales to check whether the logic is correct. The details are as follows:
[0137] Step 2.1: Log in to the report query interface. RPA automatically fills in the report query conditions, such as report region, organization, currency, etc., and downloads the corresponding report to the specified directory after the data is ready.
[0138] Step 2.2: Open the downloaded report, read the specified verification rules in the script, and verify the report data. The verification rules are divided into data verification tests within a single report and data verification tests across files.
[0139] For example, for a bank's daily foreign exchange settlement and sales statistics report, for the data verification test within a single report, RPA needs to check the business logic "A01=A02+A06", "A02=A03+A04+A05", "A16=A17+A21", "A17=A18+A19+A20", "A21=A22+A23+A24+A25+A26+A27+A30" rules specified in the sample of a bank's daily foreign exchange settlement and sales statistics report as shown in Table 1, and record the test results; for cross-file data verification and verification tests, after connecting to the database with a specified user, read the specified fields in the data table according to the rules and verify them with the fields in a bank's daily foreign exchange settlement and sales statistics report file. For example, A03, A04, and A05 in Table 1 all take the values of the foreign exchange code STATCODE and the amount AMOUNT in the data table.
[0140] Table 1
[0141]
[0142] Step 3: Judge the report logic module and record the results, including test time, test documents, data location that failed the test, error conditions, etc.
[0143] Step 4: User management module, see Fig.13 , for the permission test of account A, account B and account C, etc.; the user management module is divided into three parts: user permission addition, user permission verification and user deletion. Set the test user name and corresponding permission control requirements in the script, use RPA to test the addition of users, user validity, user permission control and other contents on the user management page, and recycle the fixed users in the database after successful verification for the next smoke test cycle. The details are as follows:
[0144] Step 4.1: After RPA successfully logs in to the unified authentication with administrator privileges in step 1.1, enter the user management interface, add multiple test users and set corresponding privileges, test the new user function, and record the test results
[0145] Step 4.2: After logging out of the administrator user, test each newly added user account by account to see if they can log in normally, and whether the function modules meet the corresponding permission requirements after logging in, and record the test results. For example: when adding a branch user, check whether they have the permission to view the head office report, whether they have the system management permission, etc.
[0146] Step 4.3: After all test users have logged in and verified, log in to the system again with administrator privileges, enter the user management module, delete all test accounts, and verify the user deletion function.
[0147] Step 5: Judge the user management module and record the test results.
[0148] Step 6: After each module is executed, a test report is generated so that technical personnel can promptly understand the error information and locate the problem, expose the problem in advance before business testing, and improve the efficiency of version readiness.
[0149] Based on the above technical solution, the RPA-based report system smoke test method provided in the application example of this application uses RPA (Robotic Process Automation) technology to perform a report system smoke test method, establishes a method for automated verification of system login pages, multi-interface passability testing, report logic comparison, and multi-user authority management, and implements one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. This method can also be reused in smoke testing of other application systems, and has great promotion value.
[0150] From the hardware level, in order to solve the problems of low efficiency and poor accuracy in the existing reporting system testing method, the present application provides an embodiment of an electronic device for implementing all or part of the contents of the reporting system smoke test method, and the electronic device specifically includes the following contents:
[0151] Fig.14 FIG. 9 is a schematic block diagram of the system structure of the electronic device 9600 according to an embodiment of the present application. Fig.14 As shown, the electronic device 9600 may include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. It is worth noting that Fig.14 is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunication functions or other functions.
[0152] In one embodiment, the smoke test function of the reporting system may be integrated into the central processing unit. The central processing unit may be configured to perform the following control:
[0153] Step 100: Perform a login test on the unified authentication interface of the reporting system based on the RPA login test script.
[0154] In step 100, the RPA robot may receive a preset RPA login test script from a client device held by a tester, and then execute the RPA login test script to perform a login test on the unified authentication interface of the reporting system.
[0155] Step 200: If the unified authentication interface passes the login test, the report system is subjected to a target test based on the RPA target test script, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0156] In step 200, an RPA robot is used to execute RPA target test scripts corresponding to the interface passability test, the report data function test, and the user management function test, respectively, to automatically perform target testing on the report system.
[0157] From the above description, it can be seen that the electronic device provided in the embodiment of the present application can effectively improve the efficiency of the smoke test process of the reporting system by applying RPA technology to the smoke test of the reporting system, and can effectively improve the accuracy and reliability of the smoke test for the reporting system, thereby effectively improving the automation and intelligence of the smoke test process of the reporting system; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the reporting system, and realize one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke tests of other application systems, and has great promotion value.
[0158] In another embodiment, the RPA robot can be configured separately from the central processor 9100. For example, the RPA robot can be configured as a chip connected to the central processor 9100, and the smoke test function of the reporting system can be implemented through the control of the central processor.
[0159] like Fig.14 As shown, the electronic device 9600 may also include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is worth noting that the electronic device 9600 does not necessarily have to include Fig.14 In addition, the electronic device 9600 may also include Fig.14 For components not shown, reference may be made to the prior art.
[0160] like Fig.14As shown, the central processing unit 9100 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor device and / or logic device. The central processing unit 9100 receives input and controls the operation of various components of the electronic device 9600.
[0161] The memory 9140 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory or other suitable devices. The above-mentioned information related to the failure may be stored, and a program for executing the relevant information may also be stored. The CPU 9100 may execute the program stored in the memory 9140 to implement information storage or processing, etc.
[0162] The input unit 9120 provides input to the central processing unit 9100. The input unit 9120 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used to display display objects such as images and texts. The display may be, for example, an LCD display, but is not limited thereto.
[0163] The memory 9140 may be a solid-state memory, such as a read-only memory (ROM), a random access memory (RAM), a SIM card, etc. It may also be a memory that saves information even when the power is off, can be selectively erased, and is provided with more data, examples of which are sometimes referred to as EPROMs, etc. The memory 9140 may also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application / function storage unit 9142, which is used to store application programs and function programs or processes for executing the operation of the electronic device 9600 through the central processor 9100.
[0164] The memory 9140 may also include a data storage unit 9143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 9144 of the memory 9140 may include various drivers for communication functions of the electronic device and / or for executing other functions of the electronic device (such as messaging applications, address book applications, etc.).
[0165] The communication module 9110 is a transmitter / receiver 9110 that sends and receives signals via an antenna 9111. The communication module (transmitter / receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as the case of a conventional mobile communication terminal.
[0166] Based on different communication technologies, multiple communication modules 9110 may be provided in the same electronic device, such as a cellular network module, a Bluetooth module and / or a wireless LAN module, etc. The communication module (transmitter / receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide an audio output via the speaker 9131 and receive an audio input from the microphone 9132, thereby realizing a common telecommunication function. The audio processor 9130 may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor 9130 is also coupled to the central processor 9100, so that recording can be performed on the local machine through the microphone 9132, and the sound stored on the local machine can be played through the speaker 9131.
[0167] The embodiment of the present application also provides a computer-readable storage medium capable of implementing all the steps in the smoke test method for the reporting system in the above embodiment. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps of the smoke test method for the reporting system in the above embodiment are implemented by the execution subject being a server or a client. For example, when the processor executes the computer program, the following steps are implemented:
[0168] Step 100: Perform a login test on the unified authentication interface of the reporting system based on the RPA login test script.
[0169] In step 100, the RPA robot may receive a preset RPA login test script from a client device held by a tester, and then execute the RPA login test script to perform a login test on the unified authentication interface of the reporting system.
[0170] Step 200: If the unified authentication interface passes the login test, the report system is subjected to a target test based on the RPA target test script, wherein the target test includes at least one of an interface passability test, a report data function test, and a user management function test.
[0171] In step 200, an RPA robot is used to execute RPA target test scripts corresponding to the interface passability test, the report data function test, and the user management function test, respectively, to automatically perform target testing on the report system.
[0172] From the above description, it can be seen that the computer-readable storage medium provided in the embodiment of the present application can effectively improve the efficiency of the smoke test process of the reporting system by applying RPA technology to the smoke test of the reporting system, and can effectively improve the accuracy and reliability of the smoke test for the reporting system, thereby effectively improving the automation and intelligence of the smoke test process of the reporting system; it can effectively avoid problems such as omission of test scenarios and duplication of test steps, thereby effectively improving the user experience of the test technicians of the reporting system, and realize one-click smoke testing after version deployment, which can more accurately cover basic business scenarios, reduce manual operations, and improve test efficiency. It can also be reused in smoke tests of other application systems, which has great promotion value.
[0173] It should be understood by those skilled in the art that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The present invention is described with reference to the flowcharts and / or block diagrams of the methods, devices (devices), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the functions in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0174] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1A step that specifies a function in one or more boxes.
[0175] The present invention uses specific embodiments to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A smoke test method for a reporting system, characterized in that: include: Perform login test on the unified authentication interface of the reporting system based on the RPA login test script; If the unified authentication interface passes the login test, the report system is subjected to a target test based on the RPA target test script, wherein the target test includes: at least one of: an interface passability test, a report data function test, and a user management function test; the RPA target test script includes: an RPA report function test script; the RPA report function test script includes the region, institution, and currency to be queried; the report data function test includes: a report data query test and a report data download test; The report data function test also includes: report logic verification test; the RPA report function test script also includes: report logic verification rules; Correspondingly, the report system smoke test method also includes: If the report data corresponding to the region, institution and currency to be queried is downloaded through the report data download test, the RPA report function test script is executed again to perform the report logic verification test on the report data based on the report logic verification rules; the report logic verification test includes total score verification, data format verification, calculation result verification and data timeliness verification; For report logic verification tests within a single report, the report logic verification rules specified in the report file sample are checked item by item and the test results are recorded; for report logic verification tests across files, after the designated user connects to the database, the designated fields in the data table are read according to the report logic verification rules and compared with the fields in the report file.
2. The smoke test method for the reporting system according to claim 1, characterized in that: The RPA login test script is used to perform a login test on the unified authentication interface of the reporting system, including: Receive an RPA login test script, wherein the RPA login test script includes a login account, password, and application front-end address of the unified authentication interface; Execute the RPA login test script to perform a login test on the unified authentication interface based on the login account, password and application foreground address of the unified authentication interface.
3. The smoke test method for a reporting system according to claim 1, characterized in that: The RPA target test script includes: an RPA interface passability test script; Correspondingly, the target test of the reporting system based on the RPA target test script includes: Receive an RPA interface passability test script, wherein the RPA interface passability test script includes an identifier of each target interface in the reporting system; The RPA interface passability test script is executed to traverse each of the target interfaces and perform interface passability tests on each of the target interfaces based on the identifiers of each of the target interfaces.
4. The smoke test method for a reporting system according to claim 1, characterized in that: The target testing of the reporting system based on the RPA target testing script includes: Receive RPA report function test scripts; Execute the RPA report function test script to log in to the report query interface in the report system, and perform report data function test on the report query interface based on the region, institution and currency to be queried.
5. The smoke test method for a reporting system according to any one of claims 1 to 4, characterized in that: The RPA target test script includes: an RPA user management function test script; Correspondingly, the target test of the reporting system based on the RPA target test script includes: Receive an RPA user management function test script, wherein the RPA user management function test script includes each user ID to be tested and a system permission requirement corresponding to each user ID; Execute the RPA user management function test script to log in to the user management interface in the reporting system, and perform a user management function test on the user management interface based on each user ID to be tested and the system permission requirements corresponding to each user ID, wherein the user management function test includes: at least one of: adding a new user test, a user permission test, and deleting a user test.
6. The report system smoke test method according to claim 5, characterized in that: The step of logging into the user management interface of the report system and performing a user management function test on the user management interface based on each user ID to be tested and the system authority requirements corresponding to each user ID, includes: Using an administrator account in the user management interface of the reporting system, based on each user ID to be tested and the system authority requirements corresponding to each user ID, add corresponding users to perform the added user test; Log out of the administrator account, and log in to each newly added user account one by one to perform the user authority test on each newly added user account; Use the administrator account again to delete the newly added accounts of each user in the user management interface to perform the user deletion test.
7. The report system smoke test method according to claim 1, characterized in that: Also includes: Generate a smoke test report for the reporting system according to the test results corresponding to the login test and the target test respectively; Output the smoke test report.
8. An RPA robot, characterized in that: include: The login test module is used to perform login tests on the unified authentication interface of the reporting system based on the RPA login test script; A target test module is used to perform a target test on the report system based on an RPA target test script if the unified authentication interface passes the login test, wherein the target test includes: at least one of an interface passability test, a report data function test, and a user management function test; the RPA target test script includes: an RPA report function test script; the RPA report function test script includes regions, institutions, and currencies to be queried; the report data function test includes: a report data query test and a report data download test; The report data function test also includes: report logic verification test; the RPA report function test script also includes: report logic verification rules; Correspondingly, the RPA robot is specifically used for: If the report data corresponding to the region, institution and currency to be queried is downloaded through the report data download test, the RPA report function test script is executed again to perform the report logic verification test on the report data based on the report logic verification rules; the report logic verification test includes total score verification, data format verification, calculation result verification and data timeliness verification; For report logic verification tests within a single report, the report logic verification rules specified in the report file sample are checked item by item and the test results are recorded; for report logic verification tests across files, after the designated user connects to the database, the designated fields in the data table are read according to the report logic verification rules and compared with the fields in the report file.
9. A report system smoke test system, characterized in that: include: Manage devices and multiple RPA robots; The RPA robot is used to perform the report system smoke test method according to any one of claims 1 to 7; The management device is used to send the RPA login test script and the RPA target test script to each of the RPA robots, and receive a smoke test report for the reporting system sent by each of the RPA robots.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the report system smoke test method according to any one of claims 1 to 7 is implemented.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the report system smoke test method according to any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
Method, device and equipment for generating process automation script, and storage medium
CN112181854A