Re: Strategies for multiple device testing - iOS
Re: Strategies for multiple device testing - iOS
- Subject: Re: Strategies for multiple device testing - iOS
- From: Alex Zavatone <email@hidden>
- Date: Fri, 22 Apr 2016 13:01:41 -0400
FYI, if anyone else is interested in this madness…
I've got success with 3 iOS simulators running at once from the same user through Xcode. The 4th became possessed, but worked after changing the version of iOS it was running.
I'm using Mac OSX 10.11.1 and Xcode 7.3.
There is an actual tool out there for managing this for real.
https://github.com/facebook/FBSimulatorControl
Cheers.
On Apr 22, 2016, at 11:48 AM, Alex Zavatone wrote:
> I'm not sure if this is the right place to open this discussion, so please direct me to a better forum if any of you have an idea where one might be.
>
> This touches on Xcode operation and use a little, but really not much.
>
> Situation:
> We are running into a reoccurring and difficult problem to reproduce with out main iOS app where it drops offline after a period of time and we've been debugging this as it appears over the past 8 months without a resolution.
>
> We now are entering a formal testing phase using all the iOS devices we have to replicate this issue in a manner that allows us to reproduce it, identify it and kill it.
>
> Since our app is meant to run in the background, and it's in the background when it the connection dies, we need to have it running on devices and logging its online state in this condition.
>
> However…
>
> iOS devices are expensive, we only have so many to test with and we have been ignoring trying to reproduce this error using the simulator.
>
> A potential advantage to using the simulator to test this is that we might be able to set up several users on one Mac, launch 4 copies of Xcode and run the app in 4 simulators.
>
> One could switch between logged in users on one Mac or even spool up versions of VMWare (if that's legal) and get multiple simulators running to test on.
>
> Does anyone know if this is even remotely possible? If it's possible, is it wise?
>
> We're looking to get to the root of why our application's network access dies while it's in the background, does it even sound viable to include the simulator in long term tests to try and narrow this down?
>
>
> If it does, the simulator can be automated through javascript and 4 years ago, I actually scripted it through AppleScript, so other apps running in the foreground could be automated while our app sits in the background.
>
>
> Are any of you out there aware of any resources on this front that are worth reading?
>
> Thanks in advance.
>
> Alex Zavatone
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden