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
Orchestrator has a fast path that skips test discovery if the test target is a single method:
android-test/runner/android_test_orchestrator/java/androidx/test/orchestrator/AndroidTestOrchestrator.java
Lines 259 to 262 in dd62f39
This doesn't work for parameterized tests, since even a single method target may expand to any number of parameterized test instances.
Run a parameterized test method through test orchestrator. They will all run in the same process. You can verify this by logging the PID.
Each instance of the parameterized test runs in its own process.
All of the instances of the parameterized test run in the same process.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Description
Orchestrator has a fast path that skips test discovery if the test target is a single method:
android-test/runner/android_test_orchestrator/java/androidx/test/orchestrator/AndroidTestOrchestrator.java
Lines 259 to 262 in dd62f39
This doesn't work for parameterized tests, since even a single method target may expand to any number of parameterized test instances.
Steps to Reproduce
Run a parameterized test method through test orchestrator. They will all run in the same process. You can verify this by logging the PID.
Expected Results
Each instance of the parameterized test runs in its own process.
Actual Results
All of the instances of the parameterized test run in the same process.
The text was updated successfully, but these errors were encountered: