BrowserStack : The Best Mobile Farm there is and there will be
- Video playback of execution
- Network Logs of execution
- Daily summary of number of tests run and the success percentage
Cons
- The product should be made affordable for freelancers as this will allow even more publicity for an otherwise already awesome tool
- 24*7 Customer Support
- Immense Community Support
- Range of test devices for both Android as well as iOS
- Less Expenditure on buying new device for testing
- Less Time Being spent on Environment setup
- Quicker debugging as Playback option is available
- Smoother Releases as we can quickly give a go ahead from the Automation End
We have integrated our repo with Browserstack and pipeline and run cases directly. When the cases fail we can see the video playback and also Test Observability tab provides better introspection and Pattern analysis
- App Automate
- Test Observability
Not only has this resolved our need for automating multiple Android devices without buying multiple models, it has also helped in iOS by providing devices across all OS
Test Observability is the best partner Ione could possibly hope for checking trends and patterns of failing cases
- LambdaTest and Sauce Labs
We have 1 person from Devops team, who is responsible to ensure the pipeline is successfully integrated with Browserstack
We have our CEO who extensively uses the Test Observability feature to check the trends of the cases
If we are unable to do so, we check with the Browserstack Single Point of Contact Shubham, and he in turn directs to check with his team if needed
- Automating iOS Devices
- Checking the video Playback of the iteration to observe the fail point instead of re-running it
- Observing the trends of execution and picking up the flaky cases for optimisation
- We are only in the initial phases of using Browserstack, so we have not yet come up an Out of the box innovation here
- We are in talks to include the App Live feature in our package
- We also are checking and observing Test Management
- Scalability
- Integration with Other Systems
- Ease of Use
We definitely wanted to be able to scale the device coverage so that was a big deciding factor as two which device farm can provide how many devices
We also wanted to be able to integrate this with our Repo and Pipeline so Integratability was also one thing we wanted
and of course , it should not need a crash course just to be able to use it, so all three factors played a role here
- Implemented in-house
- Na
- No Training
- App Live
- App Automate
- Test observability
- Not found
- Cicle CI
- Bitbucket
- NA
- API (e.g. SOAP or REST)
- Na
- Na