Method and system for automatic regression test of RPA component

Abstract

The invention belongs to the technical field of RPA testing, and particularly relates to a method and system for automatic regression testing of an RPA component. The method comprises the following steps: S1, performing parameterized transmission on common configuration according to different execution environments, different client versions and different executors during RPA component regression; s2, building a general component test framework, filling the general component test framework with the to-be-tested component according to the function scene, and setting a judgment standard for judging whether component function judgment is passed or not and judging whether component return value type judgment is correct or not; s3, collecting test data, and uniformly summarizing the test data into a global variable; s4, storing the collected test data into a database, and performing data analysis; and S5, judging whether to send a message notification or not according to the initial configuration after the test data is stored in the database. The method has the characteristic that the automatic regression test of the component can be completed through the self-packaged test framework of the RPA tool without depending on a third-party tool.

Description

Technical Field

[0001] The present invention belongs to the field of RPA testing technology, and in particular relates to a method and system for automated regression testing of RPA components. Background Art

[0002] RPA (Robotic Process Automation) is a technology that simulates and executes repetitive business tasks or processes through software robots. In the past few years, RPA has become an important tool for many companies to achieve digital transformation, especially in the fields of finance, accounting, customer service, supply chain management, etc. With the widespread application of RPA technology, how to ensure the quality and stability of RPA systems has become a focus of attention for enterprises. In particular, when the RPA system undergoes version iteration, environment changes, or new scenario adaptation, how to effectively perform regression testing of components to ensure the compatibility and correctness of the automated process has become a key issue in the testing field.

[0003] With the rapid development of RPA technology, traditional manual testing methods can no longer meet the needs of large-scale and efficient component regression testing. RPA testing faces the following challenges: Frequent component changes: Since RPA tools need to constantly adapt to new systems, new page structures, and new scenarios, the number of components continues to increase and component functions are constantly updated. Therefore, a large number of regression tests are required to ensure the quality of component releases.

[0004] Complex workflows: RPA-automated processes are usually complex, involving the integration of multiple systems and applications. The correctness of each link and sub-process must be ensured during testing.

[0005] Non-interactive execution environment: Many RPA systems do not rely on human interaction for execution, so traditional user interface (UI) automation testing tools are difficult to directly apply to RPA testing.

[0006] However, the existing RPA component regression testing methods have the following disadvantages: 1. The number of components and functions are frequently updated, resulting in poor test adaptability and high maintenance costs; Existing RPA component testing often relies on third-party testing frameworks, which require pre-building test cases and automated scripts for component testing, making it inflexible for testing frequently changing RPA components. Every time an RPA component is updated, test cases and scripts need to be modified or rewritten, adding extra workload and labor costs.

[0007] 2. Component regression test results are not stored and cannot be traced; The result data of manual tests are usually not stored in the database, or are only stored in the local file system, which makes data management and sharing difficult. In addition, the lack of centralized storage of test results often makes it impossible to conduct comprehensive analysis and monitoring across platforms and projects. The test team cannot read data online in real time, nor can they obtain test data from different environments and devices, which poses a challenge to the monitoring, evaluation and optimization of large-scale automated test projects.

[0008] 3. The problem of inconsistent execution standards for human regression testing; When regression testing is performed manually, it is often limited by factors such as each executor's testing experience and familiarity with components, which often leads to inconsistent execution results and inability to determine whether the execution has passed. This brings hidden dangers to regression testing and subsequently affects the user experience.

[0009] 4. Lack of effective exception handling and repair mechanism; Exception handling in RPA testing usually relies on manual intervention, and existing testing tools lack effective automatic repair mechanisms when encountering exceptions. Although some tools provide error capture and logging functions, once a test fails, it is usually necessary to manually fix the error and re-execute the test.

[0010] 5. Component test dependency files cannot be reused; RPA tools often contain a large number of components that read and write files. After the execution of the files that the component functional regression depends on, the content or format is often changed and cannot be reused. Each regression requires repeated preparation of test files, which increases the testing cost.

[0011] Therefore, it is very important to design a method and system for automated regression testing of RPA components to achieve the purpose of completing automated regression testing of components through the test framework encapsulated by the RPA tool itself without relying on third-party tools. Summary of the invention

[0012] The present invention aims to overcome the problems in the prior art of the existing RPA component regression testing method, such as poor test adaptability, high maintenance cost, untraceable test results, inconsistent human regression test execution standards, lack of effective exception handling and repair mechanism, and inability to reuse component test dependency files. The present invention provides a method and system for RPA component automated regression testing that can achieve component automated regression testing without relying on third-party tools through a test framework encapsulated by the RPA tool itself.

[0013] In order to achieve the above-mentioned object of the invention, the present invention adopts the following technical solutions: The method for automated regression testing of RPA components includes the following steps: S1, when the RPA component is regressed, the common configuration is parameterized and passed according to the different execution environments, client versions, and executors; S2, build a component general test framework, fill the components to be tested into the component general test framework according to the functional scenarios, and set the judgment criteria for whether the component function is passed and whether the component return value type is correct; S3, collects all test data and aggregates all test data into global variables; S4, storing all collected test data into the database and performing data analysis; S5: After all test data are stored in the database, it is determined whether to send a message notification according to the initialization configuration of step S1.

[0014] Preferably, step S1 comprises the following steps: S11, add a custom dialog component, select an input box control, configure the executor and default value for this time; add a radio button control, configure the execution environment and default value for this time; add a radio button control, configure whether to send a message notification after the operation ends; add a static text control, configure the description of this execution; S12, convert the custom dialogue parameters into global variables; considering the large number of components to be tested, put the components with the same functional characteristics into the same task block for execution; S13, adding an empty list variable list_data in the global variables to store the result data during the component execution process.

[0015] Preferably, step S2 comprises the following steps: S21, encapsulates the component general test framework as follows: Add a folding component and name it as the test scenario of the component to be tested; Add an exception acquisition component to ensure that execution can continue if an error is encountered during execution; Add the components to be tested and the judgment conditions in the try statement block, which are: judging whether the component execution result meets expectations, judging whether the component return value type is correct; the component return value type is used to affect the compatibility before and after the component upgrade; S22, adding a print error log component in the abnormal branch; S23, the execution component return value type judgment process is as follows: Get the data type component, pass in the component return value parameter, and directly return the type of the passed parameter after running; S24, based on the functional scenario of the component to be tested, the dependent files are restored. The restoration process includes adding files and modifying files. The specific process is as follows: Add file: Create a new word component. After the execution is completed, you need to add the close document and delete file components to delete the newly created word file; Modify file: Write text component. You need to add copy file component before execution to back up the file to be operated. Operate the backup file during execution. After execution, delete the backup file through delete file component.

[0016] Preferably, in step S3, the test data includes positive result data, abnormal result data and execution error data.

[0017] Preferably, step S4 comprises the following steps: S41, add a database connection component and configure information according to the deployed database type; after filling in the configuration and testing the connection, add an SQL statement execution component and fill in the table creation statement; S42, looping through the empty list variable list_data in the global variable, and inserting the data into the database in batches; S43, after the data is stored in the database, it is necessary to query the execution status of the current test group, and it is necessary to add a SQL query component to analyze the results; the statements of the SQL query component all use dynamic parameters to ensure that different test groups are common.

[0018] Preferably, in step S5, the type of the message notification supports Feishu, DingTalk, and enterprise WeChat notification robots; the formats of the message notification include text, MarkDown (MarkDown is a lightweight markup language) and developer mode.

[0019] Preferably, when the type of message notification supports Lark, step S5 includes the following steps: S51, add the Feishu robot component, enter the custom robot Webhook address that has been added in the Feishu group, send a test message after entering, and receiving the test message indicates a successful connection; then set the content format, select rich text mode, and enter the corresponding code.

[0020] The present invention also provides a system for automated regression testing of RPA components, including: Initialization configuration module, used to parameterize and transfer common configurations according to different execution environments, client versions, and executors during RPA component regression; The component use case execution module is used to build a component general test framework, fill the components to be tested into the component general test framework according to the functional scenarios, and set the judgment criteria for whether the component function is passed and whether the component return value type is correct; The result collection module is used to collect all test data and aggregate all test data into global variables; Data analysis module, used to store all collected test data into the database and perform data analysis; The message push module is used to determine whether to send a message notification based on the initial configuration after all test data is stored in the database.

[0021] Compared with the prior art, the present invention has the following advantages: (1) The testing scheme of the present invention is unique in the industry. By encapsulating the core steps of each link of the regression test into a visual framework, the connection between the various links of the RPA regression test is opened up, so that test engineers who have just entered the RPA field can quickly get started and reduce a lot of learning costs for component functions; (2) The present invention classifies components by function and automatically performs regression testing, ensuring that all functional scenarios are covered, solving the problem of test omissions caused by frequent updates of the number of components and functions, and improving the comprehensiveness and accuracy of the test; (3) Compared with third-party tools and code frameworks, the testing scheme of the present invention does not need to maintain a complete set of code environments separately, but only needs to provide component dependencies. It can be run directly, and can respond more quickly to the problem of frequent updates and changes in the number of components and functions, reducing the workload and labor costs of script maintenance; (4) The technical solution of the present invention optimizes the test process and collects and stores test data in a unified manner through a database storage solution, solving the problem of data opacity and avoiding the problems of data dispersion and inconsistent formats in traditional methods, which facilitates subsequent tracing and data analysis; (5) The technical solution of the present invention eliminates the problem of inconsistent manual judgment standards through the component assertion module encapsulated in the framework, thereby ensuring the consistency and reliability of regression testing; (6) The innovation, comprehensiveness, efficiency and ease of use of the technical solution of the present invention can greatly improve the performance of RPA component regression testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A flowchart of the method for automated regression testing of RPA components in the present invention; Figure 2 This is an overall architecture diagram of the method for automated regression testing of RPA components in the present invention; Figure 3 A flow chart of the process of encapsulating the component universal test framework in the present invention; Figure 4 A flow chart of the data analysis process in the present invention; Figure 5 A flowchart of the method for automated regression testing of RPA components provided in an embodiment of the present invention in practical application. DETAILED DESCRIPTION

[0023] In order to more clearly illustrate the embodiments of the present invention, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those of ordinary skill in the art, other accompanying drawings and other implementation methods can be obtained based on these accompanying drawings without creative work.

[0024] The present invention provides a method for automated regression testing of RPA components, such as Figure 1 As shown, first, the RPA components to be tested are divided into different regression test groups according to their functional characteristics. In this embodiment, word and file processing classes are taken as examples. Build an initialization configuration module, including the executor who triggers this regression, the operating environment, whether to send message notifications, execution notes, and global variable settings. Then build a component general test framework to support regression testing of different types of components, including determining whether the component function is implemented, determining whether the component return value type is correct, writing positive and exception assertions, executing exception handling, and executing post-processing modules, covering all component function scenarios under word classification and file processing classification. During the test execution process, all test data is temporarily stored in variables, and then the temporarily stored data is stored in the database. The test framework will automatically analyze the execution results of the regression test, count the total number of cases, the number of successful cases, the number of failed cases, and the success rate under the current test group, and use the analysis results to determine whether to send message notifications based on the initialization configuration.

[0025] Specifically, the method for automated regression testing of RPA components of the present invention includes initialization configuration, component use case execution, result collection, data analysis, and message push. The overall architecture is as follows: Figure 2 As shown, the details are as follows: 1. Initialization configuration When the RPA component is regressed, the common configuration needs to be parameterized and passed according to the different execution environments, client versions, and executors. The specific steps are as follows: 1-1, add a custom dialog component, select the input box control, configure the executor and default value; add a radio button control, configure the execution environment and default value; add a radio button control, configure whether to send a message notification after the run ends; add a static text control, configure the description of this execution.

[0026] 1-2. Convert custom dialog parameters to global variables. Due to the large number of components to be tested, components with the same functional features will be placed in the same task block for execution in actual operations. For example, the word and file processing task groups mentioned above will be divided into two process blocks, namely the word component and the data processing component. This requires converting the parameters defined in the initialization configuration to global variables to implement cross-process block calls. Reassign the local variables input_executeby, input_env, input_send_message, and input_remark by setting the variable component, and pass them to the global variables var_executeby, var_env, var_send_message, and var_remark.

[0027] 1-3. Add an empty list variable list_data in the global variables to store the result data during the component execution process.

[0028] 2. Component Use Case Execution The component use case execution part requires building a component general test framework, filling the components under the test group into the test framework according to the functional scenarios, and setting the judgment criteria for whether it passes or not. The specific steps are as follows: 2-1, component general test framework packaging. The process is as follows Figure 3 As shown, add a folding component and name it as the test scenario of the component to be tested. Then add an exception acquisition component to ensure that the execution can continue if an error is encountered during execution. Add the component to be tested and the judgment conditions in the try statement block, which are: judging whether the component execution result meets expectations, judging whether the component return value type is correct. The component return value type affects the compatibility of the component before and after the upgrade. If the return value type changes after the component is updated, such as from a list to a dictionary, the process that used the component before the upgrade will become unusable, so the return value judgment part is encapsulated in the framework.

[0029] 2-2, add a print error log component in the exception branch. Considering the flexibility of the regression process package, it is necessary to support not only automatic regression execution, but also manual triggering execution, so that the execution error of the component can be intuitively seen during the manual execution process. The error log content is as follows: Component function judgment failed: f'Component name: test scenario, function abnormality'; The component return value type judgment fails: f'component name: test scenario, return value exception'; Component execution process exception: f'Component name: Process execution exception, exception reason: '+str(ex); 2-3, component return value type judgment. Add a component to obtain the data type, pass in the component return value parameter, and directly return the type of the passed-in parameter after running. This can also be achieved through type (component return value).

[0030] 2-4, component execution post-processing. According to the functional scenario of the component to be tested, the dependent files need to be restored. The restoration process includes adding files and modifying files: Add files: For example, if you create a new word component, after execution, you need to add the close document and delete file components to delete the newly created word file to ensure the integrity of the data for the next execution.

[0031] Modify files: If you want to write text components, you need to add a copy file component before execution to back up the file to be operated. When executing, operate the backup file. After the execution is completed, delete it using the delete file component.

[0032] 3. Results Collection The framework comes with positive result collection, abnormal result collection, and execution error collection, and the data is uniformly summarized in the global variable list_data. After adding the insertion code component, write it according to the actual scenario.

[0033] Positive result collection: list_data.append(["component name","component test scenario","yes","normal function"]); Abnormal result collection: list_data.append(["component name","component test scenario","no","function abnormality"]); Execution error collection: list_data.append(["component name","component test scenario","no","process execution exception, exception reason:"+str(ex)]).

[0034] 4. Data Analysis After the Word and file processing regression process package is executed, the execution results are automatically summarized into the global variable list_data. At this time, the collected data needs to be stored in the database. 4-1, create a data table. The process is as follows Figure 4 As shown, add a database connection component and configure information according to the deployed database type. MySQL, SQL server, postgresql, Oracle, etc. are supported. This article takes MySQL as an example. After filling in the configuration and testing the connection, add the SQL statement execution component and fill in the table creation statement.

[0035] The table creation statement is as follows: CREATE TABLE t_regression_result_data ( id INT AUTO_INCREMENT PRIMARY KEY, -- auto-increment ID, used as primary key package_name VARCHAR(255) NOT NULL, -- process package name component_name VARCHAR(255) NOT NULL, -- component name component_test_scene VARCHAR(255) NOT NULL, -- component test scene is_passed BOOLEAN NOT NULL, -- whether the execution passed (0: failed, 1: passed) execution_desc TEXT, -- Execution description run_duration INT NOT NULL, -- running time (unit: seconds) addtime TIMESTAMP DEFAULT CURRENT_TIMESTAMP, -- creation time, default current time updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP -- Update time, automatically updated to the current time ); 4-2, loop through the global variable list_data and insert data into the database in batches, such as Figure 4 As shown, SQL is used here to insert data components in batches; 4-3. After the data is entered into the database, you need to query the execution status of the current test group. You need to add a SQL query component to analyze the results. All SQL statements here use dynamic parameters to ensure that they are universal for different test groups.

[0036] Number of successful execution cases: sql_success_count SELECT COUNT(*) FROM t_regression_result_data t1 JOIN ( SELECT package_name, MAX(addtime) AS latest_addtime FROM t_regression_result_data GROUP BY package_name ) t2 ON t1.package_name = t2.package_name AND t1.addtime = t2.latest_addtime WHERE t1.issuccess = 1 AND t1.package_name LIKE %s; sql_fail_count: The number of failed query execution cases sql_total_count: the total number of query execution cases sql_success_rate: query execution success rate.

[0037] 5. Message push After the data is stored, it is determined whether to send a message notification based on the initial configuration. The message notification type supports Feishu, DingTalk, and enterprise WeChat notification robots. The formats include text, MarkDown (MarkDown is a lightweight markup language), and developer mode. The following takes the Feishu robot configuration as an example to explain the specific process of message push: 5-1, add the Lark robot component, enter the custom robot Webhook address that has been added in the Lark group, send a test message after entering, and receiving the test message indicates a successful connection. Then set the content format, select rich text mode, and enter the corresponding code.

[0038] After the regression process package is executed, the message notification result is as follows: Regression process package running results Process package name: Word+file processing Data overview: Total number of use cases - 80, number of successes - 80, number of failures - 0 Pass rate: 100.0000% Start time: 2023-08-08 10:33:00 Operating environment: release Run results: Click to view report Executor: 567 Note: 660-Upgrade.

[0039] In addition, the present invention also provides a system for automated regression testing of RPA components, including: Initialization configuration module, used to parameterize and transfer common configurations according to different execution environments, client versions, and executors during RPA component regression; The component use case execution module is used to build a component general test framework, fill the components to be tested into the component general test framework according to the functional scenarios, and set the judgment criteria for whether the component function is passed and whether the component return value type is correct; The result collection module is used to collect all test data and aggregate all test data into global variables; Data analysis module, used to store all collected test data into the database and perform data analysis; The message push module is used to determine whether to send a message notification based on the initial configuration after all test data is stored in the database.

[0040] Based on the technical solution of the present invention, the following case scenario is used to illustrate the implementation process of the present invention in practical application. The specific application implementation plan is as follows: Example 1: Test task word class component regression test.

[0041] Initialization: Prepare the word component test dependency files, fill in the executor, select release for the execution environment, select send message notification and fill in the remarks as needed. Figure 5 As shown, the details are as follows: 1. Build a general component testing framework; 2. Add the newly created word component under the word category to the test framework; 3. Add positive result assertion, abnormal result assertion, and execution exception assertion; 4. The execution results are collected into the list list_data, and the collection results are: [["Open document","doc format","yes","normal function"],["Open document","doc format","yes","normal return value"]]; 5. Perform post-processing and delete the newly created word file; 6. Traverse the list_data data and write it to the configured database; 7. Perform data analysis; Number of query execution failure cases: SELECT COUNT(*) FROM t_regression_result_data t1 JOIN ( SELECT package_name, MAX(addtime) AS latest_addtime FROM t_regression_result_data GROUP BY package_name ) t2 ON t1.package_name = t2.package_name AND t1.addtime = t2.latest_addtime WHERE t1.issuccess = 0 AND t1.package_name LIKE %s; Query the total number of execution cases: SELECT COUNT(*) FROM t_regression_result_data t1 JOIN ( SELECT package_name, MAX(addtime) AS latest_addtime FROM t_regression_result_data GROUP BY package_name ) t2 ON t1.package_name = t2.package_name AND t1.addtime = t2.latest_addtime WHERE t1.package_name LIKE %s; Query execution success rate: sql_success_rate = sql_success_count / sql_total_count; 8. Check the message notification word test group execution status; 9. Filter out component scenarios that fail and submit bugs to corresponding developers; 10. Track and verify submitted bugs; 11. Output the test report based on the execution status.

[0042] Example 2: Test task file processing component regression test Initialization: Prepare the test dependency files for the file processing component, fill in the executor for this time, select release for the execution environment, select send message notification and fill in the remarks as needed. Figure 5 The process shown is as follows: 1. Copy the built common component test framework; 2. Fill the components to be tested under the file processing category into the test framework according to different test scenarios, and set up post-processing to ensure that the files are restored to their initial state after execution; 3. Add positive result assertion, abnormal result assertion, and execution exception assertion; 4. The execution results are collected into the list list_data; 5. Manually click Run to execute the regression process package; 6. Check the assertions printed in the output and find components that fail, and submit the bug to the corresponding developer; 7. Track and verify submitted bugs; 8. Output the test report based on the execution status.

[0043] The innovative features of the present invention are as follows: 1. Unique visual regression testing framework: Provides a visual regression testing framework to help test engineers who are new to the RPA field get started quickly and reduce learning costs.

[0044] 2. Comprehensive coverage of regression testing scenarios: Through functional classification and automated execution, we ensure that all test scenarios are covered, solving the problem of test omissions caused by frequent updates.

[0045] 3. Easy-to-use visual configuration: There is no need for a complex code environment, and it can be run directly by just providing component dependencies, which reduces script maintenance and labor costs.

[0046] 4. Unified data collection and storage: By uniformly storing test data in a database, data dispersion and format inconsistency issues are avoided, and data transparency and traceability are improved.

[0047] 5. Standardized regression test judgment: The judgment criteria are unified through the assertion module to ensure the consistency and reliability of regression test results.

[0048] The above description is only a detailed description of the preferred embodiments and principles of the present invention. For ordinary technicians in this field, according to the ideas provided by the present invention, there will be changes in the specific implementation methods, and these changes should also be regarded as the protection scope of the present invention.

Claims

1. A method for automated regression testing of RPA components, characterized in that: The steps include: S1, when the RPA component is regressed, the common configuration is parameterized and passed according to the different execution environments, client versions, and executors; S2, build a component general test framework, fill the components to be tested into the component general test framework according to the functional scenarios, and set the judgment criteria for whether the component function is passed and whether the component return value type is correct; S3, collects all test data and aggregates all test data into global variables; S4, storing all collected test data into the database and performing data analysis; S5: After all test data are stored in the database, it is determined whether to send a message notification according to the initialization configuration of step S1.

2. The method for automated regression testing of RPA components according to claim 1, characterized in that: Step S1 includes the following steps: S11, add a custom dialog component, select an input box control, configure the executor and default value for this time; add a radio button control, configure the execution environment and default value for this time; add a radio button control, configure whether to send a message notification after the operation ends; add a static text control, configure the description of this execution; S12, convert the custom dialogue parameters into global variables; considering the large number of components to be tested, put the components with the same functional characteristics into the same task block for execution; S13, adding an empty list variable list_data in the global variables to store the result data during the component execution process.

3. The method for automated regression testing of RPA components according to claim 2, characterized in that: Step S2 includes the following steps: S21, encapsulates the component general test framework as follows: Add a folding component and name it as the test scenario of the component to be tested; Add an exception acquisition component to ensure that execution can continue if an error is encountered during execution; Add the components to be tested and the judgment conditions in the try statement block, which are: judging whether the component execution result meets expectations, judging whether the component return value type is correct; the component return value type is used to affect the compatibility before and after the component upgrade; S22, adding a print error log component in the abnormal branch; S23, the execution component return value type judgment process is as follows: Get the data type component, pass in the component return value parameter, and directly return the type of the passed parameter after running; S24, based on the functional scenario of the component to be tested, the dependent files are restored. The restoration process includes adding files and modifying files. The specific process is as follows: Add file: Create a new word component. After the execution is completed, you need to add the close document and delete file components to delete the newly created word file; Modify file: Write text component. You need to add copy file component before execution to back up the file to be operated. Operate the backup file during execution. After execution, delete the backup file through delete file component.

4. The method for automated regression testing of RPA components according to claim 1, characterized in that: In step S3, the test data includes positive result data, abnormal result data and execution error data.

5. The method for automated regression testing of RPA components according to claim 3, characterized in that: Step S4 includes the following steps: S41, add a database connection component and configure information according to the deployed database type; after filling in the configuration and testing the connection, add an SQL statement execution component and fill in the table creation statement; S42, looping through the empty list variable list_data in the global variable, and inserting the data into the database in batches; S43, after the data is stored in the database, it is necessary to query the execution status of the current test group, and it is necessary to add a SQL query component to analyze the results; the statements of the SQL query component all use dynamic parameters to ensure that different test groups are common.

6. The method for automated regression testing of RPA components according to claim 1, characterized in that: In step S5, the type of the message notification supports Feishu, DingTalk, and enterprise WeChat notification robots; the format of the message notification includes text, MarkDown, and developer mode.

7. The method for automated regression testing of RPA components according to claim 6, characterized in that: When the type of message notification supports Lark, step S5 includes the following steps: S51, add the Feishu robot component, enter the custom robot Webhook address that has been added in the Feishu group, send a test message after entering, and receiving the test message indicates a successful connection; then set the content format, select rich text mode, and enter the corresponding code.

8. A system for automated regression testing of RPA components, used to implement the method for automated regression testing of RPA components according to any one of claims 1 to 7, characterized in that: The system for automated regression testing of RPA components includes: Initialization configuration module, used to parameterize and transfer common configurations according to different execution environments, client versions, and executors during RPA component regression; The component use case execution module is used to build a component general test framework, fill the components to be tested into the component general test framework according to the functional scenarios, and set the judgment criteria for whether the component function is passed and whether the component return value type is correct; The result collection module is used to collect all test data and aggregate all test data into global variables; Data analysis module, used to store all collected test data into the database and perform data analysis; The message push module is used to determine whether to send a message notification based on the initial configuration after all test data is stored in the database.

Images