Profile cover photo
Profile photo
Anand Bagmar
280 followers -
Software Quality Evangelist
Software Quality Evangelist

280 followers
About
Anand's posts

Post has attachment
Anand Bagmar commented on a post on Blogger.
See this post - https://goo.gl/linfxs - for code and implementation details.

Post has attachment
Sharing implementation of cucumber-jvm - Appium test framework

Post has attachment
Sharing implementation of cucumber-jvm - Appium test framework
I recently shared the Features of my Android Test Automation Framework and also the challenges, and, how we overcame those, to make the parallel test execution work well with Android 7.0 devices as well. In this blog post, I will be sharing the details (inc...

Post has attachment

Post has attachment
Finding my way out of bottomless pit with Appium & Android 7.0 for parallel test runs
As mentioned in my earlier post - I designed and implemented a cucumber-jvm - Appium -based test framework to run automated tests against Android Mobile Devices. We were using: cucumber-jvm - v1.2.5 cucumber-reporting - v3.3.0 appium - v1.6.3 appium-java-cl...

Post has attachment
How to upgrade the appium-uiautomator2-driver version for appium 1.6.3?

Post has attachment
How to upgrade the appium-uiautomator2-driver version for appium 1.6.3?
I am using appium v1.6.3 - which comes with appium-uiautomator-driver@0.2.3 with appium-uiautomator-server@0.0.8. I need to upgrade to the newer appium-uiautomator-driver@0.2.9 (which has a fix for an issue I am seeing - https://github.com/appium/appium/iss...

Post has attachment
Anand Bagmar commented on a post on Blogger.
+Saurabh Pandey - you mentioned

--> I would love to read more about the parallelization. Could you please share more details around it.
Yes, I will be sharing the Jenkins configuration + the gradle file soon with the community to show the solution implemented for testing Viu.

Post has attachment
Anand Bagmar commented on a post on Blogger.
+Nikhil Bhandari 
You mentioned:

--> I love the Jenkins part where configuration is source controlled.
This is essential to be done. Else we need to keep track of this manually every time - and this is an error prone activity. Also, as the number of Jenkins jobs increase over time, there is so much duplication in the configuration.

--> Can you share some more details around it? Is it done automatically when the job configuration is updated?
Will share this configuration in a gist soon

--> Also for the step where you need to provide URL for Android APK can be very well automated. For example, build is completed and debug/release artifacts can be stored in repository (nexus/artifactory). If tests are run independently (not as part of CI) then APK can be downloaded from repo.
You are right. bAt present, we have different CI servers where the build is created, Vs where the tests run. Hence, the URL is required to be updated manually - from where to get the APK. However, there is work already in progress to use the same CI server - so as soon as a new APK is available, it will automatically trigger the e2e tests, by providing the location of the APK file. There will be no manual intervention required then.

Post has attachment
Features & Capability of my #Android #Test #Automation #Framework - for a (private) Real-device Test Lab
Wait while more posts are being loaded