-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
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
Add an option to return an error code if the tests failed #446
Comments
Maybe this is a "bug" since iOS actually fails on test failures... |
As far as I know, XHarness exits with
Or is this about Android only? |
This is Android only. |
I see that the way it is currently handled in In XHarness we currently do this:
Question 1: Is it a lot of trouble for you to do what runtime does? |
That runner appears to be a console app? Is it not possible for xharness to look at the exit cote returned by the bundle and determine a fail?
There is also the case of a test crash:
I see It seems xharness itself succeeds even though we just asked it to fail? At least that is the disconnect for me. |
Oh, I didn't know about this. This looks like a bug. @greenEkatherine can you please have a look what we're doing with the app's exit code and the expected exit code? |
Yeah, it should be fixed. What we do now - we compare adb process' exit code with the expected one. But this adb exit code doesn't reflect what happens with instrumentation |
I have to add custom code to detect any failed tests in the results so I can fail the build.
If there was a command line arg to basically use the test failure to also mean the command failed. This can wait until everything is cleaned up, but should still return a non 0 exit code if my tests failed.
The text was updated successfully, but these errors were encountered: