UI Layer Automation Testing Framework (I)-Introduction and environment building

Hello everyone, this series of tutorials mainly introduces the design and practice of the automated testing framework based on the Appium UI layer. I will usually study and work of the practice of one by one of the summary down, to give beginners a little inspiration and inspiration, if there is a wrong place also please point out.
The so-called UI layer automation, as the name implies, the main test business layer interface layer, about the unit layer, interface layer of automatic follow-up, for testing, I advocated the idea is: layered testing, continuous integration. As long as the follow-up more attention to my blog, will give you a presentation.
Well, the nonsense is not much to say, start getting into the chase.

Plan ahead for this series of catalogs:
Automated Testing Framework (i): Introduction and environment construction
Automated test Framework (II): Appium Foundation
Automated test Framework (III): Base layer
Automated test Framework (IV): Object library Layer
Automated test Framework (V): Operational and use-case tiers
Automated test Framework (VI): Continuous integration and test reporting

Corresponding Source address: Https://github.com/iTestinglab : Introduction

Test Framework Name: Because the framework is based on Appium, so I gave it a domineering name:Appiumturbo

Test Frame diagram:
I will divide the framework into four layers, from the bottom up, the divisions are responsible, as shown in the figure:

Testing Framework Essentials: The framework is based on the now more popular third-party open source Framework Appium two times development through Maven project and dependency management through testng test script management through log4j build run log through ASSERTJ provide rich assertions Output a variety of test reports via reportng Finally, the source is hosted in git for continuous integration via Jenkins

The advantages of the test framework: the framework supports Android and iOS and the H5 page (which is the power of Appium) to organize the code in pages in PO mode, for all the information on this page, related operations are put into a class, This makes the specific test case into a simple invocation and validation operation. This greatly improves the reusability and readability of the code. Using data-driven thinking, data and code are effectively separated to improve the maintainability of the code. Supports parallel execution of multiple use cases, which means that multiple devices can be connected while executing different use cases, improving execution efficiency. II: Environment installation JDK, Eclipse, Andorid SDK, configure environment variables

Install the Appium server (we recommend that you install the GUI version first)
Because my computer is an imac, and Windows is not the same, the GUI interface is as follows

Click on the figure Appiumdoctor, the following screen will appear, all tick to prove that the appium depends on the environment installed
Install Maven and install the M2E plug-in installation configuration in eclipse the Jenkins Continuous integration environment, refer to my previous post Jenkins installation and build deployment

The above environment configuration, there are tutorials on the Internet, we have a lot to check the information, here is not said, will not be left to turn Google,baidu
The next chapter mainly explains the basic knowledge of appium, please look forward to.