tree f3918f24b49efd8ee627e0abe4e1d78878491896
parent 132bd8508a6357b3a7ec349067ce07c1f29de187
author Remi NGUYEN VAN <reminv@google.com> 1642576241 +0000
committer Android Build Coastguard Worker <android-build-coastguard-worker@google.com> 1644453720 +0000

Do not verify field count in tests used in CTS

Original change: https://android-review.googlesource.com/c/platform/packages/modules/Connectivity/+/1952107

Tests in tests/common and tests/cts are run as part of CtsNetTestCases.
Many used assertFieldCountEquals in parceling/unparceling tests to
ensure that unexpected fields were not added, or that they were not
missed when testing parceling/unparceling.

However with many of the classes updatable through module updates, the
field count may change in the future, breaking CTS tests.

Stop checking for the field count, as it would break on module releases,
and its value is lower than the maintenance cost.

Bug: 205901761
Test: atest CtsNetTestCases

Merged-In: Ie53474eecf0a836788ee15b45adc7a7980c12355
Merged-In: I79854741f7e834574d4825bb737ef507785310fe
Merged-In: Ib1701358f9058aeaaa336be8d074cfaa700c4309
(cherry picked from commit 9a2a8e5205d3aad8c16037f440770a979ca4b103)
(cherry picked from commit 64dd2c35f1606b5431a0d37dc3e6037e6974aff0)

Change-Id: I74d43b3ede00f893cf30a18c58fba32a897530e1
(cherry picked from commit b020e552d834171e3bd844d342c7c4ef2b9320c6)
Merged-In:I74d43b3ede00f893cf30a18c58fba32a897530e1