If you are testing your application against emulator / simulator, you will still have risks that the expected features may possible not work on several real devices. To handle the real device testing you should have many devices to run your tests. In the current market, we have lots of possibilities for device and operating system versions combinations. Best approach to find most used devices, you should use some statistical data. Most of the cases Pareto analysis can help for selecting high coverage devices. However if you want to find more bug before release, you can focus on the newest device with latest OS version and the oldest devices with the oldest OS version. Any case you should have at least 5-10 android devices and 3-5 iOS devices for a good level of coverage in the beginning. Therefore managing the devices is another problem if you want to have your own local test suites. As a good alternative you can use the cloud services. In this post I want to share some information about running Calabash test on Xamarin Test-Cloud.
Xamarin Test-Cloud supports X-platform frameworks so you can use same feature files for both iOs and Android project. However you should submit the code with providing the profile and the config files in your command. If you have your own Calabash project then you are ready to submit your code to test-cloud.
Go to Xamarin Test-Cloud and open and account, then you will get 3hours X 30days free usage. Click "New Test Run" and create platform specific devices group. At the end of the creation select "Calabash" then it gives you complete command to submit test-cloud. To run test-cloud you need to install `xamarin-test-cloud` gem by the following command:
If you are not using X-platform, you submit the code with the following command:
gem install xamarin-test-cloud
test-cloud submit yourAppFile.apk f957b60sd2322wddwd1f6140c760c2204a --devices 481d761b --series "AndroidMostUsed" --locale "en_US" --app-name "ProjectName" --user email@example.com
test-cloud submit yourAppFile.apk f957b60sd2322wddwd1f6140c760c2204a --devices 481d761b --series "AndroidMostUsed" --locale "en_US" --app-name "ProjectName" --user firstname.lastname@example.org --profile android --config=config/cucumber.yml
As I have explained in my previous post Calabash-Android and Calabash-iOs is differentiated by architecture becauseof the platform dependency. These commands are directly applied but for iOs project you need to have a new target as -cal and it should be built for device. Then you should produce .ipa files from this target. To produce .ipa file you can run the following command:
/usr/bin/xcrun -sdk iphoneos PackageApplication -v ~/Library/Developer/Xcode/DerivedData/ModacruzV2-hdlgquuxyftvplepqknjiywdnclj/Build/Products/Debug-iphoneos/IOSProject-cal.app -o ~/Projects/mobile_app_automation/IOSProject.ipa
Then you can submit your iOs project with newly created .ipa file:
test-cloud submit ~/Projects/mobile_app_automation/IOSProject.ipa f957b60sd2322wddwd1f6140c760c2204a --devices 21d1d61b --series "IosMostUsed" --locale "en_US" --app-name "ProjectName" --user email@example.com --profile ios --config=config/cucumber.yml --profile ios --config=config/cucumber.yml
Then you see the progress in the console or web, on the console it gives the result and the url to reach the project on Xamarin Test-Cloud. The Xamarin very friendly user interface to see the failing test cases.
One of my favourite features of cucumber is to handle test cases with tag, but Xamarin has not implemented the tags options but they suggesting the the using categorisation. By adding the command `--include CATEGORY-NAME` for Nunit test. However I could not satisfy with this feature, hope to solve it.
Update:Answer for running with tag option came from stackoverflow, you can add the tag you want to run at the config file like `--tag @regression`
android: RESET_BETWEEN_SCENARIOS=1 PLATFORM=android -r features/support -r features/android/support -r features/android/helpers -r features/step_definitions -r features/android/pages --tag @regression
The final word, this is where the cloud testing takes advantages, you can run the same scripts with many devices in parallel.