-
Notifications
You must be signed in to change notification settings - Fork 314
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
Instrumented test results outputs nothing when test collection failed(process crashed) with AndroidX test orchestrator #1834
Comments
Looks like that when But in process crashed case, the remote Android JUnit Runner was unabled to call // callback with empty tests. |
@ZSmallX - Your explanation looks reasonable but I'm having difficulty reproducing. Would you mind sharing a sample project with a repro? |
@ananci Yeah, here is the repro https://github.com/ZSmallX/android_test_issue_1834 And by this repro, I can get the expected test results when running from IDE, and can not when running from command line. |
any update on this? |
Description
My code changes caused exception at Application.onCreate(), and instrumented tests run via AndroidX test orchestrator.
execution command line like:
And there is one details file at
adb shell run-as androidx.test.orchestrator cat /data/user_de/0/androidx.test.orchestrator/files/testCollection.txt
.Steps to Reproduce
Expected Results
See process crashed details in instrumented tests results outputs to indicate test failure.
Actual Results
No process crashed details in instrumented tests results outputs and indicate test success.
AndroidX Test and Android OS Versions
Android API Level 29
AndroidX Test Orchestrator 1.4.2
Link to a public git repo demonstrating the problem:
None currently.
The text was updated successfully, but these errors were encountered: