Lately, I’ve been using composer to run instrumented tests in the Android world. ([Android]composer and swarmer)
Today, I just found an interesting PR. => https://github.com/gojuno/composer/pull/138
The PR is emulating the behaviour like AndroidTestOrchestrator. As you know, the orchestrator has some limitations and it includes Parameterized tests aren't currently supported
. It is JUnit4’s feature. So, the test support library has introduced JUnitParams.
The PR also has the same limitation. My project has been introduced the new Params
so we don’t affect the limitations. But if you’d like to introduce the new composer’s feature, you should take care it.
I also just found interesting news.
Espresso 3.0.2, Runner 1.0.2, Rules 1.0.2, Monitor 1.0.2, AndroidTestOrchestrator 1.0.2 (2018-04-24) have been released!
https://developer.android.com/topic/libraries/testing-support-library/release-notes
They have some good improvements and fixes. For example:
- Espresso 3.0.0 should NOT depend on test runner
- ActivityTestRule doesn’t update Activity instance during configuration changes
- Pass -e clearPackageData flag if you wish the orchestrator to run pm clear context.getPackageName() and pm clear targetContext.getPackageName() commands in between test invocations. Note, the context in the clear command is the App under test context.
etc.
Reading the release note, they fixed and improved many things for AndroidTestOrchestrator. That is brilliant.