You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2018. It is now read-only.
It seems that bwoken has the requirement that you need to pass in a unique device identifier when running a script in the simulator. IMO, bwoken should have the built in ability to run the device on a specific simulator by name (Or even on an array of simulator names).
There are some bugs being mentioned out there when bwoken is returning after 'Build Succeeded' with no results. Digging in, it looks like no 'w' flag is being passed to instruments. This flag is required so instruments returns with no output.
Is there any way that Bwoken can currently run tests without specifying the unique identifier for the simulator? Or is this a feature enhancements?
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey All,
It seems that bwoken has the requirement that you need to pass in a unique device identifier when running a script in the simulator. IMO, bwoken should have the built in ability to run the device on a specific simulator by name (Or even on an array of simulator names).
There are some bugs being mentioned out there when bwoken is returning after 'Build Succeeded' with no results. Digging in, it looks like no 'w' flag is being passed to instruments. This flag is required so instruments returns with no output.
Is there any way that Bwoken can currently run tests without specifying the unique identifier for the simulator? Or is this a feature enhancements?
Thanks!
The text was updated successfully, but these errors were encountered: