tree 2bdf3adbe9ba4be2db310cd403e06ca9988174e9
parent fb34c5861a1fafaab201c282805bf08f479fe475
author Remi NGUYEN VAN <reminv@google.com> 1624865285 +0000
committer Remi NGUYEN VAN <reminv@google.com> 1625461288 +0000

Fix ConnectivityManagerTest initialization on Q

The test can't have TetheringManager as an argument to methods or a
field, otherwise the test runner will crash when scanning the class for
tests because TetheringManager did not exist in Q. Although
testFactoryReset is already skipped on Q, the test runner would fail
at initialization time, before starting the run.

Use CtsTetheringUtils instead. This ensures that TetheringManager does
not have method signatures or members that reference classes that do not
exist on Q, so the test runner can scan the class successfully before
starting the run.

Bug: 188851796
Test: atest ConnectivityManagerTest on Q
Original-Change: https://android-review.googlesource.com/1740779
Merged-In: I87488d0f23628a1ef2d7af0242513fcc5401d598
Change-Id: I87488d0f23628a1ef2d7af0242513fcc5401d598