Test API behavior change in standalone test case
In previous CL, the behavior was modified in the module,
but the test was not skipped for T device with unmodified module,
which usually happens in some specific test suites, e.g. wifi MTS.
Move the assertion to another test and annotate with
@ConnectivityModuleTest to indicate that the test needs
to be executed with updated module to prevent from breaking
the test.
Test: atest CtsNetTestCasesLatestSdk:android.net.cts.ConnectivityManagerTest# \
testRegisterNetworkCallback
on tm-qpr-dev devices
Fix: 258471863
Change-Id: Ifb3d1ac45ebde727ad719b45497ab458ad0a4b7a
1 file changed