Quitting ScreenshotPreview Closes the iOS Simulator too

[MarkBrazier]

I think this is a bit harsh, I might want to carry on using the simulator!

[JackRostron]

This is a good example of where we should stick up a wiki and have it as a sudo-discussion/planning point. Currently terminates the simulator too so we can guarantee there is nothing else that can be interacting with the simulator/that the tests are closed (also, because that simulator session will keep outputting files to a temporary directory if we don't terminate them - something which we might need to reevaluate since at the moment if it doesn't run the code to remove the temporary directory your system might not remove previous test data). Valid reasoning to want to keep simulator open though. Needs discussion.

[SamDKBerry]

Its a tough one because its not really a simulator session its an instruments session. It wouldn't be hard to add logic so that it stops polling after the mac app passes it a command, we could just leave it in an idle loop.

On 16 June 2014 03:36, Jack Rostron notifications@github.com wrote:

This is a good example of where we should stick up a wiki and have it as a sudo-discussion/planning point. Currently terminates the simulator too so we can guarantee there is nothing else that can be interacting with the simulator/that the tests are closed (also, because that simulator session will keep outputting files to a temporary directory if we don't terminate them - something which we might need to reevaluate since at the moment if it doesn't run the code to remove the temporary directory your system might not remove previous test data). Valid reasoning to want to keep simulator open though. Needs discussion.

— Reply to this email directly or view it on GitHub https://github.com/JackRostron/UIAutomation/issues/10#issuecomment-46163530 .