Switch CtsLibcoreOjTestCases to use AndroidJUnitRunner
Change Ia6b2334a761186d19867b3dc1a289cef9901bee0, amongst other things,
adds support for the 'runnerBuilder' instrumentation argument to the
AndroidJUnitRunner class. That allows custom RunnerBuilder
implementations to be supplied by a package under test.
That change made it possible for this change to switch the
CtsLibcoreOjTestCases CTS package from using CoreTestRunner (which
supports TestNgRunnerBuilder classes automatically) to using
AndroidJUnitRunner with the runnerBuilder option.
Made the following changes:
* Remove reference to CoreTestRunner - AJUR is the default.
* Updated AndroidManifest to specify AJUR.
* Change core-listener argument to listener.
* Add filter argument (CoreTestRunner handled core-expectation
automatically).
* Made TestNgRunnerBuilder public and specify it in the
runnerBuilder argument to AJUR.
Running the test involved:
make CtsLibcoreOjTestCases CtsLibcoreTestRunner
cts-tradefed run cts -m CtsLibcoreOjTestCases
The tests were run as follows:
1) Without any changes, worked fine. This was to get a baseline for the
tests that were run, of which there were 3975.
2) With the above changes except with an invalid runnerBuilder which
caused the tests to fail. This was done to ensure that the changes
were being made and that the runnerBuilder was being processed.
3) With this change, worked fine. Checked to make sure that the same
number of tests were run, which they were.
Bug: 28689581
Test: see above
Change-Id: Ifa89cfa343bc038e2298157a835bfb16d144fa5b
3 files changed