CN107451060A - A kind of across mobile terminal automated test frame system - Google Patents

Abstract

The purpose of the present invention is to aim at the deficiencies in the prior art, and provide a cross-mobile terminal automated testing framework system, which can perform automated testing on Android and IOS terminals with only one set of codes. When the company's hardware resources and manpower are insufficient, the current framework does not need to distinguish development platforms, so the development cycle and maintenance costs will be greatly reduced.

Description

A Cross-Mobile Automated Testing Framework System

technical field

The invention relates to the field of computers, in particular to a cross-mobile terminal automated testing framework system.

Background technique

The automation of the existing framework Android and IOS must be realized separately, the cost of manpower and hardware investment is high, and the maintenance is difficult.

Contents of the invention

The purpose of the present invention is to aim at the deficiencies in the prior art and provide a cross-mobile automated testing framework system, which can perform automated testing on both Android and IOS terminals with only one set of codes. When the company's hardware resources and manpower are insufficient, the current framework does not need to distinguish development platforms, so the development cycle and maintenance costs will be greatly reduced.

To achieve the above object, the present invention discloses the following technical solutions:

A cross-mobile automated testing framework system, including:

Device configuration module: including test Android/IOS test package path configuration, device related configuration, APP main package name and main class name configuration, initialization driver configuration;

Driver module: It is necessary to call the public methods of the driver layer. The driver layer needs to be used: element positioning operations, gestures, and screenshots are all encapsulated in the driver, which is convenient for business modules to call;

Business module: adopt the pageObject+keywords mode to separate business from data, freely customize the scene and scene execution sequence, and realize the combination of Android and IOS codes; the business module includes:

The page element positioning file is a specified file that stores the page control elements in the form of static parameters. If the elements of the page control are changed, there is no need to modify the associated N places, and Android and IOS can be named separately or stored separately;

The parameter file is used to store static parameters and SQL statements in the case;

Element operation file, which operates on page control elements, including: click, input, view, slide, screenshot, log; here is the operating system judgment to distinguish whether to test Android APP or IOS APP. If it is executed on Windows, execute Android , Mac operates IOS; if the project only has Android APP, just set the IOS part to empty, and vice versa;

The case file is composed of multiple element operation files into a case, and the parameters passed in by the case come from the parameter file, so that one element operation can be called by multiple cases;

Scenario files are composed of multiple case files, including one or more of BVT scripts, payment scenario scripts, and process scripts, which can be customized at will;

Testng.xml file, manage and execute test cases;

The build.xml file is used to build the code, run the testng file to execute the test, and generate the test report;

Test report file, the test report is automatically generated after the script is executed, including the number of executed cases, the number of passed cases, the number of failed cases and error records;

Screenshot archive module, including regular screenshots and abnormal screenshots. Regular screenshots are controlled by switches. Only when the switch is turned on will screenshots be taken during execution. If the switch is not turned on, screenshots will not be taken. Abnormal screenshots will only be taken when the program throws an exception;

Log archiving module: output test logs during the test and store them in the specified location.

Furthermore, a framework supports both Android and IOS automation. The project has both Android App and IOS APP and writes the corresponding positions at the judgment place of the business operation layer platform. If the project only has Android APP, set the IOS part at the judgment place of the business operation layer platform It is empty and optional, and vice versa.

A cross-mobile terminal automated testing framework system disclosed by the present invention has the following beneficial effects:

1. This framework separates the similarities and differences between IOS and Android automated testing, and is divided into three layers: device configuration layer, driver layer, and business layer; so that a set of frameworks is compatible with IOS and Android automated testing at the same time;

2. The IOS and Android driver layers store the public methods that need to be called in the driver layer, which is convenient for the business layer to call. Save the time of writing common methods during development;

3. Save human resources and operating costs: When the company's hardware resources and manpower are insufficient, the current framework does not need to distinguish between development platforms, so the development cycle and maintenance costs will be greatly reduced.

4. This framework supports independent operation. If the project only has Android APP, set the IOS part to empty and enable at the element operation layer platform judgment, and vice versa.

Description of drawings

Fig. 1 is the flow chart of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described below. Obviously, the described embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The core of the present invention is to provide a cross-mobile automated testing framework system, which can realize Android and IOS automated testing with only one set of codes, and makes secondary packaging for public methods such as element positioning, operation, and screen operation, shortening the development cycle , which reduces the cost of code maintenance and does not distinguish the operating system of the development environment.

In order to realize a framework compatible with both Android and IOS automation testing, it is necessary to clarify the similarities and differences between Android and IOS automation:

1. Similarities

1) The same framework is based on Appium+Selenium+Testng+Ant

2) JAVA language used in both

2. Similarities and differences

1) Drivers are different

2) Different platforms

3) The method of starting the App is also different

4) Android uses Uiautomatorviewer to locate elements, and IOS uses Appium Inspector.

precondition:

1. Build Appium+Selenium+Java+Testng+Ant environment on Windows/MAC operating system respectively;

2. Configure Appium on Windows/MAC operating system respectively.

See Fig. 1, a kind of framework system of cross-mobile terminal automated testing disclosed by the present invention, comprises:

Device configuration module: including test Android/IOS test package path configuration, device related configuration, APP main package name and main class name configuration, initialization driver configuration;

Driver module: It is necessary to call the public methods of the driver layer. The driver layer needs to be used: element positioning operations, gestures, and screenshots are all encapsulated in the driver layer, which is convenient for business modules to call;

Business module: It can form a complete technical solution, adopt pageObject+keywords mode, separate business from data, freely customize scenes and scene execution sequence, and realize Android and IOS code merging; business modules include:

The page element positioning file is a specified file that stores the located page control elements in the form of static parameters. If the element address changes, only the parameters in the element positioning file need to be modified, and the corresponding case is not required. Android and IOS are named differently. Or store them separately;

The parameter file is used to store static parameters and SQL statements in the case;

Element operation file, which operates on page control elements, including: click, input, view, slide, screenshot, log; here is the operating system judgment, which is mainly used to distinguish whether to test Android APP or IOS APP, and execute it if it is executed on Windows Android, if it is a Mac, then operate IOS; if the project only has Android APP, just set the IOS part to empty;

The case file is composed of multiple element operation files into a case, and the parameters passed in by the case come from the parameter file, so that one element operation can be called by multiple cases;

Scenario files are composed of multiple case files, including one or more of BVT scripts, payment scenario scripts, and process scripts;

Testng.xml file, manage and execute test cases;

The build.xml file is used to build the code, run the testng file to execute the test, and generate the test report;

Test report file, the test report is automatically generated after the script is executed, including the number of executed cases, the number of passed cases, the number of failed cases and error records;

Screenshot archive module, including regular screenshots and abnormal screenshots. Regular screenshots are controlled by switches. Only when the switch is turned on will screenshots be taken during execution. If the switch is not turned on, screenshots will not be taken. Abnormal screenshots will only be taken when the program throws an exception;

Log archiving module: output test logs during the test and store them in the specified location.

In one embodiment of the present invention, in the screenshot archiving module, when the program execution fails to find elements, an exception will be automatically thrown, and the exception screenshot method will be called at the place where the exception is thrown, and when the program throws an exception, the screenshot will be automatically stored in a specified location .

The present invention separates Android and IOS device configurations, because IOS and Android call devices similarities and differences; the driver layer is separated, and the driver layer is a public method that needs to call the driver, element positioning operation, screenshot, and screen operation; the element operation layer judges the execution on the Windows side of the platform androidAPP, execute IOS APP on Mac side; CASE, scene, testmg.xml, ant.xml configure Android and IOS merged execution; add regular screenshots and abnormal screenshots in the script and store them in different directories, regular screenshots are controlled by switches, and switches are turned on for execution Automatic screenshot when scripting, if not open, no screenshot, abnormal screenshot will only be taken when an exception is thrown.

Compared with the content introduced in the background technology, the present invention has a clear structure, high script reusability, flexibility, and easy maintenance. The framework adopts the pageObject+keywords mode, which is realized according to the structural layered mode; the encapsulation code of the public method is highly reusable, Reduce code redundancy; don't need to care about specific implementation, which reduces code maintenance costs; facilitates test task assignment and process control. And it is suitable for personnel of different technical levels.

The above description is only a preferred embodiment of the present invention, and is not intended to limit it; Modifications to the technical solutions described in the examples, or equivalent replacement of some or all of the technical features; and these modifications and replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (2)

1. A cross-mobile terminal automated testing framework system, characterized in that it comprises: Device configuration module: including test Android/IOS test package path configuration, device related configuration, APP main package name and main class name configuration, initialization driver configuration; Driver module: It is necessary to call the public methods of the driver layer. The driver layer needs to be used: element positioning operations, gestures, and screenshots are all encapsulated in the driver, which is convenient for business modules to call; Business module: adopt the pageObject+keywords mode to separate business from data, freely customize the scene and scene execution sequence, and realize the combination of Android and IOS codes; the business module includes: The page element positioning file is a specified file that stores the page control elements in the form of static parameters. If the elements of the page control are changed, there is no need to modify the associated N places, and Android and IOS can be named separately or stored separately; The parameter file is used to store static parameters and SQL statements in the case; Element operation file, which operates on page control elements, including: click, input, view, slide, screenshot, log; here is the operating system judgment to distinguish whether to test Android APP or IOS APP. If it is executed on Windows, execute Android , Mac operates IOS; if the project only has Android APP, just set the IOS part to empty, and vice versa; The case file is composed of multiple element operation files into a case, and the parameters passed in by the case come from the parameter file, so that one element operation can be called by multiple cases; Scenario files are composed of multiple case files, including one or more of BVT scripts, payment scenario scripts, and process scripts, which can be customized at will; Testng.xml file, manage and execute test cases; The build.xml file is used to build the code, run the testng file to execute the test, and generate the test report; Test report file, the test report is automatically generated after the script is executed, including the number of executed cases, the number of passed cases, the number of failed cases and error records; Screenshot archive module, including regular screenshots and abnormal screenshots. Regular screenshots are controlled by switches. Only when the switch is turned on will screenshots be taken during execution. If the switch is not turned on, screenshots will not be taken. Abnormal screenshots will only be taken when the program throws an exception; Log archiving module: output test logs during the test and store them in the specified location. 2. A kind of cross-mobile terminal automation testing framework system according to claim 1, it is characterized in that, a framework supports Android and IOS automation simultaneously, and project has Android App and IOS APP to write respectively at the judgment place of business operation layer platform For the corresponding position, if the project only has Android APP, it is possible to set the IOS part to empty at the judgment of the business operation layer platform, and vice versa.