machine; • Two tablets - started to think about moving away from my local machine; • Three tablets and four 3rd party application - moving away from my local machine.
to run your tests; • Easy integration with calabash automation; • Our app was developed using Xamarin framework. • Cons • Our tablets were not available into their supported devices. • Couldn’t test with third party components
Fast and stable. • Cons • We wanted to test mobile network behaviour (3g); • Increased risk - not testing what users will use; • Wouldn’t be testing the whole bundle (app + hardware).
there; • We had the space to create it; • 3rd Party Components • Cons: • Running on one tablet at a time; • Getting result reports slow; • No benefit for releases.
is not just the app is the whole bundle (app + hardware); • Easy to interact with devices if needed; • Fast results from all platforms; • Being able to monitor and to analyse the behaviour of the tablets; • Faster releases. • Cons: • Maintaining all the hardware.
for each device; • Hardware identification using the Android hardware IDs • Mapping file between Android IDs and users; • Environment variable for users (sent from TeamCity).
task: • couldn’t use environment vars anymore; • cucumber task was running on a different thread than the one used to create it; Solution: • parse the cucumber parameters and use the report path one to grab the device ID
We will be moving some of the tests to use a mock back end… • Emulators for some tests? • Splitting tests for one model between multiple devices? • BYOD?
thekraken
garrettdimon
hatefulcrawdad
notwaldorf
matthewcrist
3n
andyhume
mclloyd
yeseniaperezcruz
.png){kind=avatar}
helenjbeal
reverentgeek
katarinadahlin
