diff options
| author | Remi NGUYEN VAN <reminv@google.com> | 2022-01-19 07:10:41 +0000 |
|---|---|---|
| committer | Remi NGUYEN VAN <reminv@google.com> | 2022-08-31 02:30:55 +0000 |
| commit | 81209cff57cca714a08b6f997cc3a29f53fae182 (patch) | |
| tree | 9a10a4e6fbb4b481ec8b239641b7cb0cd49ab541 /tests/common/java/android/net/NetworkStackTest.java | |
| parent | f0e4039c2f05a2f695a7f78f23f7d203ab03906f (diff) | |
Do not verify field count in tests used in CTS
This is already in android12-tests-dev, but is necessary in this
branch as it is used for regression testing using internal test
configs which are not available on android12-tests-dev.
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: 244275971
Bug: 205901761
Test: atest CtsNetTestCases
Merged-In: Ie53474eecf0a836788ee15b45adc7a7980c12355
Merged-In: I79854741f7e834574d4825bb737ef507785310fe
Merged-In: Ib1701358f9058aeaaa336be8d074cfaa700c4309
Change-Id: I74d43b3ede00f893cf30a18c58fba32a897530e1
(cherry picked from commit b020e552d834171e3bd844d342c7c4ef2b9320c6)
Diffstat (limited to 'tests/common/java/android/net/NetworkStackTest.java')
0 files changed, 0 insertions, 0 deletions