CN111913889A - Test system building method and test system - Google Patents

Abstract

The embodiment of the invention relates to the field of software automatic testing, and discloses a test system construction method and a test system. Including: creating a hierarchical directory in the newly created interactive application test project to store page elements, test data and test cases in corresponding directories; importing files required for the implementation of the test project; encapsulating APP operations and Web operations respectively public method; configure the Appium execution environment to obtain an automated test control system after launching Appium.exe during test case execution; construct a test scene class based on the automated test control system and the visual data management platform; configure the test execution based on the constructed test scene class file to implement suite testing. The invention can realize automatic testing of interactive items, reduce the coupling degree of each test scenario, realize data-driven testing, improve the stability and readability of scripts, lower the code writing ability threshold of testers, and improve code writing efficiency.

Description

A test system construction method and test system

technical field

The invention relates to the technical field of software automatic testing, in particular to a test system construction method and a test system.

Background technique

With the rapid development of the mobile Internet, the use of smart phones has become more and more extensive, and mobile phones have become an essential tool for entertainment, communication, life and learning. At the same time, the development of various mobile Internet applications has arisen, most of which have their corresponding background management systems. The testing of such system applications involves the interaction function of the platform terminal, and the execution of platform and terminal notifications. In frequent cases, the test work is cumbersome, the accuracy is poor, and the labor cost is high. At present, the existing automated testing methods for single-testing platform functions or single-testing terminal functions include:

1. Web-side automated testing. Web-side UI (UserInterface, user interface) automated testing based on QC and QTP (Quick Test Professional), this method needs to record and edit automated test scripts, complete automated testing of the software under test through scripts and output test results; Selenium-based Unlayered web-side UI automation test, testers with certain java code writing ability write test data, page objects and methods according to the test business scenario, and execute the script to output the test result. The script written by this solution is better than QC and QTP-based Web The end UI automation testing framework has improved in stability, standardization, and readability.

2. App-side automated testing. App-side UI automation testing based on adb and Monkey simulates user's key input, touch screen input, gesture input, etc. This method is mainly used to test the stability of android apps; based on Appium-based automated testing of unlayered Android apps, Appium is used as a This open source automated testing tool can quickly create Android UI automated test cases. Testers write test data, page objects and methods according to test business scenarios, and execute scripts to output test results.

The inventor found that the related art has at least the following problems: the existing solution provides a single-end UI automated testing method to a certain extent, but cannot well meet the automated testing needs of platform and terminal interaction projects. Web-side UI automation testing based on QC and QTP, limited QTP, QC and other non-open source, recorded scripts have poor readability, poor stability, slow running speed, and difficult to maintain; Selenium-based unlayered Web-side UI automation testing, Testers are required to have good script code writing ability, the threshold is high, the test data and test method scenarios are not layered, and the maintenance cost is extremely high; based on adb and Monkey App-side UI automation test, clicks and gestures are random, It is difficult to meet the testing needs of specific functions; the automated testing of unlayered Android apps based on Appium has no standardized framework and specifications in the management of page elements and data, and the acquisition of test elements is cumbersome, the technical threshold for scripting is high, and maintenance costs are high. Larger, the efficiency of single-ended automation improvement is also limited.

SUMMARY OF THE INVENTION

In view of this, the purpose of the embodiments of the present invention is to provide a test system construction method and test system, which can realize automated testing of platform terminal interaction items, and reduce the complexity of each test scenario by layering interface elements, data, and use case execution. Coupling, editing elements and data through the visual interface, realizing data-driven testing, improving the stability and readability of scripts, lowering the code writing ability threshold of testers, and improving code writing efficiency.

In order to solve the above technical problems, embodiments of the present invention provide a method for building a test system, including:

Create a hierarchical directory in the newly created interactive application test project to store page elements, test data and test cases in corresponding directories;

Import the files required for the implementation of the test project;

Encapsulate the public methods of APP operation and Web operation respectively;

Configure the Appium execution environment to obtain an automated test control system after launching Appium.exe during test case execution;

Construct test scene classes based on the automated test control system and the visual data management platform;

Configure a test execution file based on the constructed test scenario class to implement suite testing.

Embodiments of the present invention also provide a test system, including: a visual data management platform, the aforementioned automated test control system and a visual data management platform;

The automated test control system is connected in communication with the visual data management platform.

Compared with the prior art, the embodiment of the present invention realizes the automatic test of the interactive project of the platform terminal by encapsulating Selenium and Appium, and layers the interface elements, data and use case execution, and realizes the storage and storage of the elements and data through the visual interface. Modification, thereby reducing the coupling degree of each test scenario, realizing data-driven testing, improving the stability and readability of scripts, lowering the code writing ability threshold of testers, and improving code writing efficiency.

As an embodiment, the public methods for encapsulating APP operations and Web operations respectively include:

In the BaseObject directory, write classes that include the startup methods of selenium and appium, display wait, implicit wait and other basic methods;

Encapsulate public method classes according to the interactive application to be tested in the AppObject directory;

Write the startup initialization classes for Web and APP in the BrowserManager directory;

Encapsulate public method classes according to Web pages in the PageObject directory;

Store configurable parameters in the Data directory;

Write a single use case scenario class under the Test directory.

As an embodiment, a test scenario class is constructed based on the automated test control system and the visual data management platform, including:

Parse the Web element data passed in by the visual data management platform; wherein, the Web element data includes positioning type, positioning information, element name, operation method to be defined, and the Web page id, and encapsulates selenium according to different pages , which forms the core API of web page element operation methods.

As an embodiment, a test scenario class is constructed based on the automated test control system and the visual data management platform, further comprising:

Parse the APP element data passed in by the visual data management platform; wherein, the APP element data includes positioning type, positioning information, element name, operation method to be defined, and the id of the app, according to the page of the app. Appium encapsulates and forms the core API of the app page element operation method.

As an embodiment, it also includes:

Create a Maven java project through the IDE, and refer to the TestNG framework to obtain the interactive application test project.

As an embodiment, it also includes:

Visual editing of page elements, test data and test results of the interactive application to be tested is realized based on the visual data management platform.

As an embodiment, the importing the files required for the implementation of the test project includes:

Store Selenium, sikuli, and maven and Jre jar packages in the lib directory; store driver, Autoit, uploadfile and other executable files and other business files in the source directory;

Import the dependent jar and source files in the corresponding lib and source directories.

As an embodiment, the automated test control system simultaneously controls the Web test client and the App test client to execute the test execution file.

As an embodiment, the automated test control system and the visual data management platform exchange data through Ftp or Sql database.

Description of drawings

1 is a flowchart of a method for building an automated testing system for platform terminal interaction items according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a testing system according to an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can appreciate that, in the various embodiments of the present invention, many technical details are set forth for the reader to better understand the present invention. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present invention can be realized.

The first embodiment of the present invention relates to a method for building an automated testing system for platform terminal interaction items. As shown in FIG. 1 , the method for building an automated testing system for a platform terminal interaction item in this embodiment includes steps 101 to 106 .

Step 101: Create a hierarchical directory in the newly created interactive application test project for storing page elements, test data and test cases in corresponding directories respectively.

Step 102: Import the files required for the implementation of the test project.

Step 104: Encapsulate public methods of APP operation and Web operation respectively.

Step 104: Configure the Appium execution environment to obtain an automated test control system after launching Appium.exe when the test case is executed.

Step 105: Construct a test scenario class based on the automated test control system and the visual data management platform.

Step 106: Configure a test execution file based on the constructed test scenario class to implement suite testing.

Optionally, step 101 creates a Maven java project through the IDE, and references the TestNG framework to obtain the interactive application test project. Specifically, first configure the java project dependency environment, create a Maven java project through the IDE, and bundle TestNG. The hierarchical directory created in step 101 includes directories such as BaseObject, AppObject, BrowserManager, PageObject, Date, Test, and Util, and also includes a lib directory, a source directory, and files such as pom.xml and testng.xml.

Optionally, importing files required for the implementation of the test project in step 102 may include: storing jar packages of Selenium, sikuli, and maven and Jre in the lib directory; storing execution files such as driver, Autoit, uploadfile and other services in the source directory file; import the dependent jar and source files in the corresponding lib and source directories.

In this embodiment, the public methods for encapsulating the APP operation and the Web operation respectively in step 103 include:

Write classes containing selenium and appium startup methods, display waits, implicit waits and other basic methods in the BaseObject directory; encapsulate public method classes according to the interactive application to be tested in the AppObject directory; write Web and APP in the BrowserManager directory Start the initialization class; encapsulate public method classes according to Web pages in the PageObject directory; store configurable parameters in the Data directory; write a single use case scenario class in the Test directory.

Step 104 configures the Appium execution environment to start Appium.exe when the test case is executed, so that it is not necessary to manually start Appium.exe during the test, thereby realizing automated testing.

Steps 101 to 104 can complete the construction of the automated test control system. Then, through steps 105 and 106, the test scene class construction and the configuration of the automatic test control script are respectively completed, thereby realizing the automatic test of the App.

Step 105 constructs a test scene class based on the automated test control system and the visual data management platform, including: parsing the Web element data passed in by the visual data management platform; wherein, the Web element data includes the positioning type, positioning information, element name, and needs to be defined. Operation method, Web page id, encapsulate selenium according to different pages, form the core API of the operation method of the web page element, and construct the Web-side test scene class. Step 105 also includes: parsing the APP element data passed in by the visual data management platform; wherein, the APP element data includes positioning type, positioning information, element name, operation method to be defined, and id of the app, and the Appium is encapsulated according to the page of the app , forming the core API of the app page element operation method, thereby constructing the web-side test scene class.

In step 106, configuring the test execution file based on the constructed test scenario class to implement the suite test includes: configuring the test execution file TestNG.xml, and using the <suite> tag to implement the suite test through the use case class name passed in in step 105.

In this embodiment, the visual editing of page elements, test data and test results of the interactive application to be tested is implemented based on the visual data management platform. Specifically, the visual data management platform can be used for the storage and modification of Web pages and APP page elements, the storage and modification of test data, and the viewing of test results. Testers can input, modify, and view on the visual interface. , The storage field format of test result data is as follows:

In this embodiment, the automated test control system simultaneously controls the Web test client and the App test client to execute the test execution file, so as to realize the automated test of the interactive project of the platform terminal. Optionally, the automated test control system and the visual data management platform can exchange data through Ftp or Sql database.

The construction method of this embodiment implements automated testing of platform terminal interaction projects by encapsulating Selenium and Appium, and layers interface elements, data, and use case execution, and realizes storage and modification of elements and data through a visual interface, thereby reducing the need for various Test the coupling of scenarios, realize data-driven testing, improve the stability and readability of scripts, lower the threshold of testers' ability to write code, and improve the efficiency of code writing.

The second embodiment of the present invention relates to a test system, comprising: a visual data management platform and the automated test control system as described in the foregoing embodiments, the automated test control system is communicatively connected to the visual data management platform. Optionally, the automated test control system and the visual data management platform are communicated and connected through an FTP server and a SQL server.

In this embodiment, the visual data management platform is used to provide a visual interface through which a user can edit and manage data such as page elements, use case scenarios, and test results.

After the automated test control system is built, the APP test scene class can be constructed based on the APP-side test data and use cases input from the visual data management platform, and through the APP operation public methods encapsulated by the automated test control system. Similarly, it can be based on visual data management The web-side test data and use cases passed in by the platform construct the web test scene class through the web operation public methods encapsulated by the automated test control system. Then configure the test execution file TestNG.xml, and use the <suite> tag to implement suite testing through the constructed use case class name. Before the test, the automated test script is obtained through the visual data management platform and uploaded to the FTP and SQL server. During the test, the automated test control system downloads automated test scripts from FTP and SQL servers, and controls the execution of automated test scripts on the Web test client and the App test client. Upload the script execution results to FTP and SQL servers, and transfer the test execution results to the visual data management platform for users to view.

The test system of this embodiment implements automated testing of platform terminal interaction projects by encapsulating Selenium and Appium, and layers interface elements, data, and use case execution, and realizes storage and modification of elements and data through a visual interface, thereby reducing the need for various Test the coupling of scenarios, realize data-driven testing, improve the stability and readability of scripts, lower the threshold of testers' ability to write code, and improve the efficiency of code writing.

The above embodiment will be specifically described below by taking a web page blacklist test case of a platform terminal interaction project as an example. The so-called interaction refers to the multi-terminal data interaction between the platform and the terminal. The project includes a background management platform and two terminals, the student terminal and the parent terminal. The background management platform and the parent terminal jointly manage the student terminal. This article introduces one of the implementation methods of the webpage blacklist: set the blacklist through the background management platform, and send the The instruction is sent to the student side, and the student side executes the instruction. Among them: the new label of the platform webpage blacklist, the input box, the xpath of the OK button (select xpath here), the operation method (corresponding to click, sendKeys, click respectively), the element name (addbut, blackwebname, confirmbut), the default of the student terminal The browser's URL input box, search button, xpath of the warning text displayed after search (select xpath here), operation method (corresponding to sendKeys, click, assertEqual respectively), element name (webname, searchbut, warning).

According to the construction method of the first embodiment, a test execution environment is built, and the main implementation methods of the directory hierarchy and the input data through the visual data management platform for the automated test execution system are as follows:

Directory layering: The method of creating layered directories in the project effectively layer interface elements, test data, and test cases. The interface elements are uniformly placed in the PageObject and AppObject directories, the test data is stored in the Data directory, and the test cases are stored Under the Test directory, input elements and data through the visual data management platform.

Input data through the visual data management platform for automated testing: encapsulate the operation method of the web page, and create a new web page blacklist class addBlackWebPage.java through the page id, element xpath, and element name (addBut) passed in by the visual data management platform Stored in the PageObject directory. The main implementation pseudocode is:

The test data is stored in the Data directory, and the newly added webpage blacklist URL https://www.taobao.com/ is stored in testData.java. The main implementation pseudocode is:

The APP page operation method is encapsulated, and the BrowserApp.java class is created and stored in the AppObject directory through the incoming appid, xpath, operation method, and element name from the visual data management platform. The main implementation pseudocode is:

The construction of test scene classes on the web side and the app side, the test cases are stored in the Test directory, and the web side addClass.java is created according to the operation type passed in by the visual data management platform (to realize the addition of the web page blacklist), and the App side isBlackWeb.java (implementing the verification of the execution of the webpage blacklist instruction). Configure TestNG.xml and use the <suit> tag to implement suite testing. The main code of its implementation:

The construction method and the constructed test system of this embodiment can realize automated testing of platform terminal interaction projects, the layered design idea can reduce the degree of code coupling, and the combination of the visual data management platform and the automated control system can effectively reduce code writing and maintenance. cost.

A third embodiment of the present invention relates to an electronic device. The electronic device of this embodiment may be an independent server. The electronic device includes: a memory and a processor;

Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to implement the method for building an automated test control system according to the first embodiment.

As a non-volatile computer-readable storage medium, the memory can be used to store non-volatile software programs, non-volatile computer-executable programs and modules. The processor executes various functional applications and data processing of the device by running the non-volatile software programs, instructions and modules stored in the memory, that is, the construction method of the above-mentioned automatic test control system is realized.

The memory may include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required by at least one function. Additionally, the memory may include high speed random access memory, and may also include nonvolatile memory, such as at least one magnetic disk storage device, flash memory device, or other nonvolatile solid state storage device. In some embodiments, the memory may optionally include memory located remotely from the processor, such remote memory being connectable to an external device via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

One or more modules are stored in the memory, and when executed by one or more processors, execute the method for building an automated test control system in any of the foregoing method embodiments.

The above device can execute the method provided by the embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method. For technical details not described in detail in this embodiment, refer to the method provided by the embodiment of the present invention.

The fourth embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program, and the computer-readable program is used for a computer to execute some or all of the above method embodiments.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

Those skilled in the art can understand that the above-mentioned embodiments are specific examples for realizing the present invention, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present invention. scope.

Claims (10)

1. A test system building method is characterized by comprising the following steps:

establishing a hierarchical directory in the newly-built interactive application test project, wherein the hierarchical directory is used for storing the page elements, the test data and the test cases in the corresponding directories respectively;

importing files required by the implementation of the test project;

respectively packaging public methods of APP operation and Web operation;

configuring an Apdium execution environment to obtain an automatic test control system after starting Apdium.exe when a test case is executed;

constructing a test scene class based on the automatic test control system and the visual data management platform;

configuring a test execution file based on the constructed test scenario class to realize the suite test.

2. The test system building method of claim 1, wherein encapsulating the common methods of APP operations and Web operations separately comprises:

writing classes containing startup methods, display waiting, implicit waiting and other basic methods of selenium and appium under a BaseObject directory;

packaging a public method class according to the interactive application to be tested under an AppObject directory;

compiling a starting initialization class of Web and APP under a Browsermanager directory;

packaging the public method class according to the Web page under the PageObject directory;

storing configurable parameters in a Data directory;

and writing a single use case scene class under the Test directory.

3. The test system building method according to claim 2, wherein constructing a test scenario class based on the automated test control system and the visual data management platform comprises:

analyzing Web element data transmitted by the visual data management platform; the Web element data comprises a positioning type, positioning information, an element name, an operation method needing to be defined and the Web page id, and the selenium is encapsulated according to different pages to form a core API of the operation method of the Web page elements.

4. The test system building method according to claim 3, wherein a test scenario class is constructed based on the automated test control system and the visual data management platform, and further comprising:

analyzing APP element data transmitted by the visual data management platform; the APP element data comprises a positioning type, positioning information, an element name, an operation method needing to be defined and an id of the APP, and the APP is packaged according to the page of the APP to form a core API of the APP page element operation method.

5. The test system set-up method of claim 1, further comprising:

and newly building a java project of Maven through the IDE, and introducing a TestNG framework to obtain the interactive application test project.

6. The test system set-up method of claim 1, further comprising:

and realizing the visual editing of the page elements, the test data and the test results of the interactive application to be tested based on the visual data management platform.

7. The test system building method according to claim 1, wherein the importing the files required for the test engineering implementation comprises:

storing the jar packages of Selenium, sikuli, maven and Jre in a lib directory; storing execution files such as driver, Autoit, uploadfile and the like and other service files in a source directory;

and importing dependent jar and source files under the corresponding lib and source directories.

8. The test system construction method according to claim 1, wherein the automated test control system controls a Web test client and an App test client to execute the test execution file at the same time.

9. The test system setup method according to claim 1, wherein the automated test control system and the visual data management platform exchange data via an Ftp or Sql database.

10. A test system, comprising: a visual data management platform and an automated test control system according to any one of claims 1 to 9;

and the automatic test control system is in communication connection with the visual data management platform.

Images