This project contains a template for mobile test automation.
The project is developed with the Java programming language and the Appium mobile automation framework.
-
Java JDK 11
-
Appium Server 2.1.3
-
Maven
The following are the dependencies of the project:
| Dependency | Version |
|---|---|
| Cucumber Java | 7.14.0 |
| Cucumber TestNG | 7.14.0 |
| Cucumber Gherkin | 27.0.0 |
| TestNG | 7.8.0 |
| Appium Java | 8.6.0 |
| Selenium Java | 4.14.0 |
| Guava | 32.1.2-jre |
| JSON | 20230227 |
| Log4j Core | 2.20.0 |
| Log4J API | 2.20.0 |
| Slf4j API | 2.0.9 |
| Slf4j Simple | 2.0.9 |
| Allure Cucumber JVM | 2.24.0 |
| AspectJ | 1.9.20.1 |
| AssertJ | 3.24.2 |
| Tess4J | 5.8.0 |
| Joda Time | 2.12.5 |
The following are the plugins of the project:
| Plugin | Version |
|---|---|
| Maven Compiler Plugin | 3.11.0 |
| Maven Surfire Plugin | 3.1.2 |
| Maven Properties Plugin | 1.2.0 |
| Allure Maven Plugin | 2.12.0 |
The project is divided into modules to have better control of its development in the different mobile OS and common functionalities.
testing-mobile-template
│ pom.xml
└─android
| | failedScenarios.xml
| | pom.xml
| | testng.xml
| └─src
| └─test
| └─java
| | └─hooks
| | | | AndroidHooks.java
| | └─listeners
| | | | ExecutionListener.java
| | └─pages
| | | | BasePage.java
| | | | *Pages.java
| | └─steps
| | | | BaseSteps.java
| | | | ClickSteps.java
| | | | CompoundSteps.java
| | | | PageInitializer.java
| | | | SendKeysSteps.java
| | | | SwipeSteps.java
| | | | ValidationSteps.java
| | | AndroidRunnerTest.java
| | | FailedScenariosRunnerTest.java
| └─resources
| └─apps
| | | *.apk
| └─features
| | *.features
└───utilities
| │ pom.xml
| └─src
| └─main
| └─java
| | └─appium
| | | │ AppiumServer.java
| | └─drivers
| | | │ AndroidAppDriver.java
| | | │ IOSAppDriver.java
| | └─extensions
| | | │ UiAutomator2Extension.java
| | | │ ExpectedConditionsExtension.java
| | | │ XCUITestExtension.java
| | └─helpers
| | | │ OCRHelper.java
| | | │ AllureHelper.java
| | └─readers
| | | │ ConfigJsonReader.java
| | | │ PropertiesReader.java
| └─resources
| │ config.json
| │ cucumber.properties
| │ log4j2-test.xml
└─ios (Same structure as android module)
The config.json file located in the /utilities/src/main/resources path must be modified, since the configurations to initialize the appium server and connect to the test device are loaded from it.
The configs section contains the paths where the AndroidSDK, JDK, NodeJS, the Appium executable are installed and finally where the appium logs will be saved.
The way to add a new configuration is as follows:
Multiple configurations can be stored since the execution of the project can be done on different computers or servers.
"configs": {
"config1": {
"android": "/Path/to/Android/sdk",
"java": "/Path/to/jdk/Contents/Home",
"node": "/Path/to/node",
"executable": "/Path/to/appium",
"log": "target/appium.log"
},
"config2": {
"android": "/Path/to/Android/sdk",
"java": "/Path/to/jdk/Contents/Home",
"node": "/Path/to/node",
"executable": "/Path/to/appium",
"log": "target/appium.log"
}
}The capabilities section has the capabilities for the devices that will be used in the tests. These capabilities are identified with a nickname.
"capabilities": {
"ios-simulator": {
"platformVersion": "16.1",
"deviceName": "iPhone 14"
},
"ios-real": {
"platformVersion": "15.4",
"deviceName": "iPhone XS Max",
"udid": "XXXXXXXX-XXXXXXXXXXXXXXXX",
"xcodeOrgId": "XXXXXXXXXX",
"xcodeSigningId": "iPhone Developer"
},
"android-simulator": {
"appium:avd": "Android_8",
"appium:deviceName": "Android_8"
},
"android-real": {
"appium:deviceName": "XXXXXXXXX"
}
}The Tesseract dependency has to be adequate to run on MacOS, follow the instructions below:
- Install Tesseract on your MacOS
To install Tesseract, run the following command on your terminal:
sudo port install tesseract
For Brew users, run the command:
brew install tesseract
- Go to the Tesseract Maven folder
cd /Users/%username%/.m2/repository/net/sourceforge/tess4j/tess4j/%version%
%username% is the name of the user registered on the MacOS
%version% is the Tesseract's version number registered in the pom.xml file
- Create a folder named 'darwin'
mkdir darwin
- Update the .jar file corresponding to the Tesseract dependency adding the darwin folder to it
jar uf tess4j-%version%.jar darwin
%version% is the Tesseract's version number registered in the pom.xml file
- Copy the .dylib file downloaded in the first step into the darwin folder
cp /usr/local/Cellar/tesseract/%version%/lib/libtesseract.%#%.dylib darwin/libtesseract.dylib
%version% is the Tesseract's version number downloaded in the first step
%#% is the first number of the Tessearct's version number (e.g. 5)
- Update the .jar file corresponding to the Tesseract dependency adding the .dylib file into it
jar uf tess4j-%version%.jar darwin/libtesseract.dylib
%version% is the Tesseract's version number registered in the pom.xml file
- Validate that the .jar file has the darwin folder and the .dylib file on it
jar tf tess4j-%version%.jar
%version% is the Tesseract's version number registered in the pom.xml file
If everything is okay, the last command will show the content table of the .jar file and we will be able to see the darwin folder and the .dylib file
META-INF/MANIFEST.MF
...
darwin/
darwin/libtesseract.dylib
The project is executed through the following maven command called from the root folder (./testing-mobile-template/)
-pl %module% -am test
If the execution is to be done to a particular tag, the line -Dcucumber.filter.tags=@Test is added to the execution command.
-pl %module% -am test -Dcucumber.filter.tags=@Test
In the event that the test execution fails, a rerun.txt file will be created in the target folder, this file will save the failed cases so that they can be re-executed with the following command.
-pl %module% -am test -Dsuite=failedScenarios.xml
%module% is the name of the module to execute (android/ios)
The project is executed through the Maven command
The test report is generated with the following maven command, called from the required module folder ( ./testing-mobile-template/android or ./testing-mobile-template/ios).
allure:report
The report will be saved in the target/reports/report folder of the module where the command was called.