-
Notifications
You must be signed in to change notification settings - Fork 335
Open
Description
Description
When using parametrized tests, it seems that the orchestator doesn't restart the process when running a single test (i.e from Android Studio). When running the entire test class it works as intended.
Steps to Reproduce
git clone git@github.com:rciovati/orchestrator-bug.git- Filter the logcat for
asdf - From Android Studio, run one of the two tests in
ExampleInstrumentedTest
Expected Results
D/asdf: Application#onCreate
D/asdf: test one... value: false
D/asdf: Application#onCreate
D/asdf: test one... value: true
Actual Results
D/asdf: Application#onCreate
D/asdf: test one... value: false
D/asdf: test one... value: true
Notes
If you run the entire class you'll see:
D/asdf: Application#onCreate
D/asdf: Application#onCreate
D/asdf: test one... value: false
D/asdf: Application#onCreate
D/asdf: test two... value: false
D/asdf: Application#onCreate
D/asdf: test one... value: true
D/asdf: Application#onCreate
D/asdf: test two... value: true
which is the intended behaviour.
AndroidX Test and Android OS Versions
See the dependencies here: https://github.com/rciovati/orchestrator-bug/blob/main/app/build.gradle#L43-L53
Link to a public git repo demonstrating the problem:
fgoncalves and jasonwyatt
Metadata
Metadata
Assignees
Labels
No labels