Open ZSmallX opened 1 year ago
Looks like that when collectTests
was exeuted in a runnable and wait for Android JUnit Runner to addTest
to CallbackLogic
.
But in process crashed case, the remote Android JUnit Runner was unabled to call addTest
, so the test == null
and callbackLogic.allTests.isEmpty == true
. Then nothing shows up or is presented.
// callback with empty tests. https://cs.android.com/androidx/android-test/+/master:runner/android_test_orchestrator/java/androidx/test/orchestrator/AndroidTestOrchestrator.java;l=294;bpv=0;bpt=0
@ZSmallX - Your explanation looks reasonable but I'm having difficulty reproducing. Would you mind sharing a sample project with a repro?
@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.