Add the below dependencies in your pom.xml (Master)
<dependency>
<groupId>com.github.saikrishna321</groupId>
<artifactId>AppiumTestDistribution</artifactId>
<version>09c4398</version>
</dependency>
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
Clone the project (https://github.com/saikrishna321/PageObjectPatternAppium) If your application is cross-platform and you end up building a PageObjectPattern Framework. Then you can also run those tests across Android and iOS devices connected to the same Mac OSX Host.
(e.g. If you have 3 Android and 3 iOS devices connected to the same machine, you will be able to execute these test parallel on both platforms)
-
Install flick
$ gem install flick
-
Install ffmpeg. OSX
$ brew update$ brew install ffmpeg
-
Install mp4box. OSX
$ brew install mp4box
-
Install ffmpeg. windows
-
Install mp4box. [windows] (https://gpac.wp.mines-telecom.fr/downloads/)
##Videos will be logged for failure tests
VIDEO_LOGS="true" mvn clean -Dtest=Runner test
Thanks to
- @thote and @jaydeepc for the motivation.
- @SrinivasanTarget for contributing on iOS parallel.
- @temyers for letting us use the cucumber-jvm-parallel-plugin(https://github.com/temyers/cucumber-jvm-parallel-plugin) as part of framework which helps generating a Cucumber JUnit or TestNG runner for each feature file.
Your should see report file generated as ExtentReport.html under the target folder.
Run Parallel tests across iOS devices and Simulators.
Q. Can I automate application which I already have installed/ downloaded from App store?
A. With XCUITest framework, that is available from ios version 9.3, it's possible to execute Native (WebViews content would not be reachable) application using it's bundle id.
In order to get information about bundle id of pre-installed application:
- connect device with application installed;
- run ideviceinstaller -l or ideviceinstaller -l -u {udid of the device} in case if more then one device connected to the host;
- in the list - find name of the application followed by its bundle id.
After that, instead of app capability bundleId should be used with application's bundle id as a value.
Since Appium still needs WDA to be built and deployed on the real device - valid certificate and provisioning profile will be needed. More information could be found here
In case if test need to interact with WebViews and/or ios version has no support of XCUITest - Appium would need instruments application which is in debug mode, it will not work with any application which is not in debug mode. Read more about it here
Q. Is this framework supports to run multiple IOS simulators?
A. Yes, Currently Appium does support multiple simulators with latest 1.6.6.beta with Xcode9-beta.
Q. Unable to instruments application or instruments crashed on start up?
A. Below are few possible causes
- (app/ipa) is not on debug mode.
- (app) targeted to simulator will not work with real device and vice versa
- Check device's developer option in settings.
Q. Unable to install application during automation?
A. A quick solution would try to install the application using "ideviceinstaller -i ipa_name", if that does not work, check app is built with the valid provisioning profile.
Q. Can I run tests on iOS app for which I have source code(e.g:"Wordpress") on real devices?
A. Yes, with a Valid provisioning profile this app can be installed on your device. (Note: The application must be signed with a valid developer certificate and your device should be added to the provisioning profile)
| ThoughtWorks | CeX |
|---|---|
 |
 |
| Jio India | M800 | Reward Gateway |
|---|---|---|
 |
 |
 |
