User interface (UI) automatic platform construction method for travel saas platform

Abstract

The invention relates to a travel saas platform-oriented UI (user interface) automatic platform construction method, which relates to the technical field of computer testing, and designs a use case writing interface for inputting a test use case, performing visual operation through an interface editor, completing the writing work of the test use case, creating different configuration sets according to tenants and business dimensions, and writing the test use case according to the configuration sets. And parameter configuration is performed in a configuration set, a tester is allowed to create and manage different configuration sets according to needs, and according to the parameters of the configuration sets, case sets of different tenants are executed through case execution scheduling and dynamic scheduling, so that concurrent execution of the case sets of the multiple tenants, connection establishment with a mobile terminal and simultaneous connection and execution of multiple mobile devices are realized. And collecting a test result of each tenant, and generating a test report.

Description

Technical Field

[0001] The present invention relates to the field of computer testing technology, and more specifically, to a method for constructing a UI automation platform for a travel SaaS platform. Background Art

[0002] In the travel SaaS platform, the quality of the user interface is crucial to the user experience. With the continuous increase and change of functions, the testing and verification of the UI becomes more and more complicated, and the efficiency and coverage of manual testing are limited. Since the online automation platform on the market has no concept of tenants, a set of scene sets is only suitable for a single tenant, the same scene set cannot be switched, and it cannot meet the requirements of complex scenes. Therefore, building a visual, configurable, and multi-tenant automation platform improves the productivity of testers. Summary of the invention

[0003] In view of the technical problems existing in the prior art, the present invention provides a method for building a UI automation platform for a travel SaaS platform to solve the problems raised in the above background technology.

[0004] The technical solution of the present invention to solve the above technical problems is as follows: a method for building a UI automation platform for a travel SaaS platform, specifically comprising the following steps:

[0005] Step 101: Design a test case writing interface for entering test cases, and perform visual operations through the interface editor to complete the test case writing work;

[0006] Step 102: Create different configuration sets according to tenants and business dimensions, and configure parameters in the configuration sets, allowing testers to create and manage different configuration sets as needed;

[0007] Step 103: According to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets;

[0008] Step 104: Establish a connection with the mobile terminal, connect and execute multiple mobile devices at the same time, collect the test results of each tenant, and generate a detailed test report.

[0009] In a preferred embodiment, in step 101, a test case writing interface is designed to input test cases, and visual operations are performed through an interface editor to complete the writing of test cases. The specific steps are as follows:

[0010] Step A1, interface design: Design a user-friendly test case writing interface for entering test cases. The interface includes the test case name, step description, operation element, and operation action field, and further includes the following steps:

[0011] Step A101, use case name: At the top of the interface, a text box for entering the use case name is designed to prompt the user to enter the name of the test case here for easy identification and management;

[0012] Step A102, step description: for each test step, a text area is designed for inputting a description of the step, wherein the test step content described includes expected behavior and input data information;

[0013] Step A103, operation elements: for each test step, a drop-down menu is designed for inputting operation elements;

[0014] Step A104, operation action: for each test step, a radio button group is designed to select an operation action, and the operation action options include clicking, inputting text, and selecting a drop-down box;

[0015] Step A2, visual operation: Design a drag-and-drop interface editor on the interface. Testers use this tool to drag page elements from the element library to the test steps to simulate user operations, and design add, delete icons and save buttons. The add and delete icons allow users to dynamically add and delete test steps and flexibly adjust the step sequence of the test case as needed; the save button allows users to save the edited test case, and the clear button allows users to clear the currently edited content and start entering a new test case.

[0016] In a preferred embodiment, in step 102, different configuration sets are created according to tenants and business dimensions, and parameter configuration is performed in the configuration set, including domain name configuration and mock interface configuration. Testers create and manage different configuration sets as needed. The specific steps are as follows:

[0017] Step B1, create a configuration set: the tester logs in with a personal account, creates a new configuration set on the main interface, and displays a list of created configuration sets on the main interface;

[0018] Step B2: Select tenant and business dimension: In the drop-down input box of the Create Configuration Set List, the user is allowed to enter tenant and business dimension information and configure parameters, including domain name configuration and mock interface configuration. By clicking the Save button, the user is allowed to save the settings of the current configuration set and return to the main interface. The steps of domain name configuration and mock interface configuration include:

[0019] Step B201, domain name configuration: enter the domain name information in the input box, verify the entered domain name information, and save it to the configuration set object;

[0020] Step B202, mock interface configuration: input mock interface information, including URL, request method, request parameters, response data, and verify the mock interface information input by the user, and save the input mock interface information to the configuration set object;

[0021] Step B3: Manage configuration sets: Testers manage different configuration sets according to different tenants and business dimensions, design edit and delete buttons, and manage the created configuration sets, further including the following steps:

[0022] Step B301, edit configuration set: for each configuration set, an edit button is designed to allow the user to modify the parameter settings of the configuration set. After the user clicks the edit button, the user jumps to the configuration set editing page to make corresponding modifications;

[0023] Step B302, delete the configuration set: for each configuration set, a delete button is designed to allow the user to delete unnecessary configuration sets. After the user clicks the delete button, a confirmation dialog box pops up. After confirming the deletion, the configuration set is removed from the system.

[0024] In a preferred embodiment, in step 103, according to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets. The specific steps are as follows:

[0025] Step C1, parsing configuration set parameters: obtaining configuration information of each tenant from the configuration set, including domain name and mock interface, and obtaining the use case set corresponding to each tenant according to the configuration information;

[0026] Step C2, concurrent execution of use case sets: For each tenant's use case set, create an execution thread. Each execution thread configures the execution environment according to the domain name and mock interface information configured by the tenant, and concurrently executes the use case sets of each tenant.

[0027] Step C3, collecting execution results: using log recording to monitor the execution status of each execution thread, collecting the execution results, and analyzing the execution results.

[0028] In a preferred embodiment, in step 104, a connection is established with a mobile terminal, multiple mobile devices are connected and executed simultaneously, the test results of each tenant are collected, and a detailed test report is generated. The specific steps are as follows:

[0029] Step D1: collect the test results of each tenant, send the test results to the server after the mobile device executes the test task, and store the test results of each tenant in the database;

[0030] Step D2: Generate a detailed test report based on the collected test results, the report containing the use case execution status, error information, and screenshots to facilitate testers to analyze the problem, further comprising the following steps:

[0031] Step D201, designing a report template: designing a test report template, including the use case execution status, error information, and screenshots to be displayed, and setting data placeholders in the report template for filling in test result data in subsequent steps;

[0032] Step D202, reading test result data: reading the saved test result data from the database, and obtaining the execution status, error information and screenshot data of each use case;

[0033] Step D203, result data analysis: analyze the test result data, extract the use case execution status, error information and screenshot information, and store them in a structured manner;

[0034] Step D204, filling in the report template: according to the parsed test result data, fill in the execution status of the use case and the screenshot of the use case into the corresponding position in the report template, use a table to display the execution status, pass and fail information of each use case, fill in the error information obtained by parsing into the error information part of the report template, and sort them according to the order of the use cases;

[0035] Step D205: Generate a final test report file according to the filled report template.

[0036] The beneficial effects of the present invention are as follows: a use case writing interface is designed for entering test cases, and visual operations are performed through an interface editor to complete the writing of test cases, different configuration sets are created according to tenants and business dimensions, and parameters are configured in the configuration sets, allowing testers to create and manage different configuration sets as needed, and according to the parameters of the configuration sets, use case execution scheduling is used to dynamically schedule the execution of use case sets of different tenants, thereby realizing the concurrent execution of multi-tenant use case sets, establishing a connection with a mobile terminal, connecting and executing multiple mobile devices at the same time, collecting the test results of each tenant, and generating a test report, thereby realizing a set of scenario sets to test multiple tenants, and connecting multiple mobile terminals for concurrent execution, thereby greatly improving the test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 The figure is a flow chart of the method of the present invention. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only 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 those skilled in the art without creative work are within the scope of protection of this application.

[0039] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, "plurality" means two or more, unless otherwise clearly and specifically defined.

[0040] In the description of the present application, the term "for example" is used to mean "used as an example, illustration or description". Any embodiment described as "for example" in the present application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is given to enable any technician in the field to implement and use the present invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the present invention can be implemented without using these specific details. In other examples, well-known structures and processes will not be elaborated in detail to avoid unnecessary details to obscure the description of the present invention. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in the present application.

[0041] Example 1

[0042] This embodiment provides Figure 1 A method for building a UI automation platform for a travel SaaS platform is shown, which specifically includes the following steps:

[0043] Step 101: Design a test case writing interface for entering test cases, and perform visual operations through the interface editor to complete the test case writing work;

[0044] Step 102: Create different configuration sets according to tenants and business dimensions, and configure parameters in the configuration sets, allowing testers to create and manage different configuration sets as needed;

[0045] Step 103: According to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets;

[0046] Step 104: Establish a connection with the mobile terminal, connect and execute multiple mobile devices at the same time, collect the test results of each tenant, and generate a detailed test report.

[0047] Preferably, in step 101, a test case writing interface is designed for entering test cases, and visual operations are performed through an interface editor to complete the writing of test cases. The specific steps are as follows:

[0048] Step A1, interface design: Design a user-friendly test case writing interface for entering test cases. The interface includes the test case name, step description, operation element, and operation action field, and further includes the following steps:

[0049] Step A101, use case name: At the top of the interface, a text box for entering the use case name is designed to prompt the user to enter the name of the test case here for easy identification and management;

[0050] Step A102, step description: for each test step, a text area is designed for inputting a description of the step, wherein the test step content described includes expected behavior and input data information;

[0051] Step A103, operation elements: for each test step, a drop-down menu is designed for inputting operation elements;

[0052] Step A104, operation action: for each test step, a radio button group is designed to select an operation action, and the operation action options include clicking, inputting text, and selecting a drop-down box;

[0053] Step A2, visual operation: Design a drag-and-drop interface editor on the interface. Testers use this tool to drag page elements from the element library to the test steps to simulate user operations, and design add, delete icons and save buttons. The add and delete icons allow users to dynamically add and delete test steps and flexibly adjust the step sequence of the test case as needed; the save button allows users to save the edited test case, and the clear button allows users to clear the currently edited content and start entering a new test case.

[0054] Preferably, in step 102, different configuration sets are created according to tenants and business dimensions, and parameter configuration is performed in the configuration set, including domain name configuration and mock interface configuration. Testers create and manage different configuration sets as needed. The specific steps are as follows:

[0055] Step B1, create a configuration set: the tester logs in with a personal account, creates a new configuration set on the main interface, and displays a list of created configuration sets on the main interface;

[0056] Step B2: Select tenant and business dimension: In the drop-down input box of the Create Configuration Set List, the user is allowed to enter tenant and business dimension information and configure parameters, including domain name configuration and mock interface configuration. By clicking the Save button, the user is allowed to save the settings of the current configuration set and return to the main interface. The steps of domain name configuration and mock interface configuration include:

[0057] Step B201, domain name configuration: enter the domain name information in the input box, verify the entered domain name information, and save it to the configuration set object;

[0058] Step B202, mock interface configuration: input mock interface information, including URL, request method, request parameters, response data, and verify the mock interface information input by the user, and save the input mock interface information to the configuration set object;

[0059] Step B3: Manage configuration sets: Testers manage different configuration sets according to different tenants and business dimensions, design edit and delete buttons, and manage the created configuration sets, further including the following steps:

[0060] Step B301, edit configuration set: for each configuration set, an edit button is designed to allow the user to modify the parameter settings of the configuration set. After the user clicks the edit button, the user jumps to the configuration set editing page to make corresponding modifications;

[0061] Step B302, delete the configuration set: for each configuration set, a delete button is designed to allow the user to delete unnecessary configuration sets. After the user clicks the delete button, a confirmation dialog box pops up. After confirming the deletion, the configuration set is removed from the system.

[0062] Preferably, in step 103, according to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets. The specific steps are as follows:

[0063] Step C1, parsing configuration set parameters: obtaining configuration information of each tenant from the configuration set, including domain name and mock interface, and obtaining the use case set corresponding to each tenant according to the configuration information;

[0064] Step C2, concurrent execution of use case sets: For each tenant's use case set, create an independent execution thread. Each execution thread configures the execution environment according to the domain name and mock interface information configured by the tenant, and concurrently executes the use case sets of each tenant to ensure that they run independently and do not interfere with each other.

[0065] Step C3, collecting execution results: using log recording to monitor the execution status of each execution thread, collect the execution results, and analyze the execution results, including success rate and failure rate indicators.

[0066] Preferably, in step 104, a connection is established with a mobile terminal, multiple mobile devices are connected and executed simultaneously, the test results of each tenant are collected, and a detailed test report is generated. The specific steps are as follows:

[0067] Step D1: collect the test results of each tenant, send the test results to the server after the mobile device executes the test task, and store the test results of each tenant in the database to ensure the persistence and reliability of the data;

[0068] Step D2: Generate a detailed test report based on the collected test results, the report containing the use case execution status, error information, and screenshots to facilitate testers to analyze the problem, further comprising the following steps:

[0069] Step D201, designing a report template: designing a test report template, including the use case execution status, error information, and screenshots to be displayed, and setting data placeholders in the report template for filling in test result data in subsequent steps;

[0070] Step D202, reading test result data: reading the saved test result data from the database, and obtaining the execution status, error information and screenshot data of each use case;

[0071] Step D203, result data analysis: analyze the test result data, extract the use case execution status, error information and screenshot information, and store them in a structured manner;

[0072] Step D204, filling in the report template: according to the parsed test result data, fill in the execution status of the use case and the screenshot of the use case into the corresponding position in the report template, use a table to display the execution status, pass and fail information of each use case, fill in the error information obtained by parsing into the error information part of the report template, and sort them according to the order of the use cases;

[0073] Step D205: Generate a final test report file according to the filled report template.

[0074] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0075] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, 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. 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 code.

[0076] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0077] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0078] 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 in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0079] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0080] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for constructing a UI automation platform for a travel SaaS platform, characterized in that: The specific steps include: Step 101: Design a test case writing interface for entering test cases, and perform visual operations through the interface editor to complete the test case writing work; Step 102: Create different configuration sets according to tenants and business dimensions, and configure parameters in the configuration sets, allowing testers to create and manage different configuration sets as needed; Step 103: According to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets; Step 104: Establish a connection with the mobile terminal, connect and execute multiple mobile devices at the same time, collect the test results of each tenant, and generate a test report.

2. According to claim 1, a method for constructing a UI automation platform for a travel SaaS platform is characterized in that: In step 101, a test case writing interface is designed to input test cases, and visual operations are performed through the interface editor to complete the writing of test cases. The specific steps are as follows: Step A1, interface design: Design a use case writing interface for entering test cases. The interface includes the use case name, step description, operation elements, and operation action fields. Step A2, visual operation: Design a drag-and-drop interface editor on the interface. Testers use this tool to drag page elements from the element library to the test steps to simulate user operations.

3. The method for constructing a UI automation platform for a travel SaaS platform according to claim 1, characterized in that: In step 102, different configuration sets are created according to tenants and business dimensions, and parameter configuration is performed in the configuration sets. Testers create and manage different configuration sets as needed. The specific steps are as follows: Step B1, create a configuration set: the tester logs in with a personal account, creates a new configuration set on the main interface, and displays a list of created configuration sets on the main interface; Step B2: Select tenant and business dimension: In the drop-down input box of the created configuration set list, the user is allowed to enter tenant and business dimension information and configure parameters, including domain name configuration and mock interface configuration. By clicking the Save button, the user is allowed to save the settings of the current configuration set and return to the main interface; Step B3: Manage configuration sets: Testers manage different configuration sets according to different tenants and business dimensions, design edit and delete buttons, and manage created configuration sets.

4. The method for constructing a UI automation platform for a travel SaaS platform according to claim 3, characterized in that: In step B2, the steps of domain name configuration and mock interface configuration include: Step B201, domain name configuration: enter the domain name information in the input box, verify the entered domain name information, and save it to the configuration set object; Step B202, mock interface configuration: input mock interface information, verify the mock interface information input by the user, and save the input mock interface information into the configuration set object.

5. The method for constructing a UI automation platform for a travel SaaS platform according to claim 3, characterized in that: The step B3 manages the configuration set, and the tester manages different configuration sets according to different tenants and business dimensions, designs edit and delete buttons, and manages the created configuration sets, further including the following steps: Step B301, edit configuration set: for each configuration set, an edit button is designed to allow the user to modify the parameter settings of the configuration set. After the user clicks the edit button, the user jumps to the configuration set editing page to make changes; Step B302, delete the configuration set: for each configuration set, a delete button is designed to allow the user to delete unnecessary configuration sets. After the user clicks the delete button, a confirmation dialog box pops up. After confirming the deletion, the configuration set is removed from the system.

6. The method for constructing a UI automation platform for a travel SaaS platform according to claim 1, characterized in that: In step 103, according to the parameters of the configuration set, the use case sets of different tenants are dynamically scheduled to be executed through the use case execution scheduling, so as to realize the concurrent execution of the multi-tenant use case sets. The specific steps are as follows: Step C1, parsing configuration set parameters: obtaining configuration information of each tenant from the configuration set, including domain name and mock interface, and obtaining the use case set corresponding to each tenant according to the configuration information; Step C2, concurrent execution of use case sets: For each tenant's use case set, create an execution thread. Each execution thread configures the execution environment according to the domain name and mock interface information configured by the tenant, and concurrently executes the use case sets of each tenant. Step C3, collecting execution results: using log recording to monitor the execution status of each execution thread, collecting the execution results, and analyzing the execution results.

7. The method for constructing a UI automation platform for a travel SaaS platform according to claim 1, characterized in that: In step 104, a connection is established with a mobile terminal, multiple mobile devices are connected and executed simultaneously, the test results of each tenant are collected, and a detailed test report is generated. The specific steps are as follows: Step D1: collect the test results of each tenant, send the test results to the server after the mobile device executes the test task, and store the test results of each tenant in the database; Step D2: Generate a detailed test report based on the collected test results. The report contains the use case execution status, error information, and screenshots to facilitate testers to analyze problems.

Images