1

So far I've successfully run iOS automation from the Instruments GUI and also using instruments on the command line. I haven't found any options that would allow me to manually open or close my app as part of the test. Instead it seems that running instruments will always launch the app at the beginning and close it at the end.

The reason I would like my app to stay open is because part of my test involves a pairing process with the desktop browser. Ideally in jenkins on osx I'd have a sequence of shell commands:

  1. run instruments test that puts app into "display passcode" state.
  2. run another command that enters the passcode in my browser component.
  3. run another instruments test that verifies my app has successfully paired.

If my app automatically closes after step 1 then the rest of the sequence won't work.

Alternatively I've checked if there's a way to execute the shell commands from within the instrumented test, but it seems that js doesnt allow such things because it would be a security risk. I'm happy with osx specific commands since I don't intend to run this on windows.

Justin Rainwater
  • 11
  • 1
  • It looks like I may be able to get the results I need by using target.host() as described [here](http://stackoverflow.com/questions/6191814/issuing-a-synchronous-http-get-request-or-invoking-shell-script-in-javascript-fr/6854819#6854819) to execute terminal commands from within my test. Still I'd like the option to have my app stay open when the instruments command is complete if anyone has any ideas... – Justin Rainwater Apr 26 '12 at 00:34

1 Answers1

1

Alas, there is no way to keep the app process running when Instruments is done with it. But, you can use target.delay() to wait until the app is in a state you're looking for. I'm not quite sure what you mean by your step 2. Are you manipulating a "browser component" outside of the simulator? Or is this this all in the same app?

Jonathan Penn
  • 1,341
  • 7
  • 8