We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be great to be able to specify custom tools, which you could pass in the simulator guid.
In my use case, I can invisage ui tests which would use a specific simulator. My script would then call my ui testings which the simulator guid...
Having said that any number of scripts which would be able to run with parameters like the simulator folder, would be extremely useful.
The text was updated successfully, but these errors were encountered:
@dsmelov another great use for this feature..
To open specific urls in a specific simulator. xcrun simctl openurl (SIMULATOR_UUID|booted) <URL>
xcrun simctl openurl (SIMULATOR_UUID|booted) <URL>
Sorry, something went wrong.
No branches or pull requests
It would be great to be able to specify custom tools, which you could pass in the simulator guid.
In my use case, I can invisage ui tests which would use a specific simulator.
My script would then call my ui testings which the simulator guid...
Having said that any number of scripts which would be able to run with parameters like the simulator folder, would be extremely useful.
The text was updated successfully, but these errors were encountered: