diff options
| author | 2024-01-22 18:16:04 +0000 | |
|---|---|---|
| committer | 2024-01-22 19:14:33 +0000 | |
| commit | 843503ba07542b3b46e936855c006b15324cf71e (patch) | |
| tree | 7ccce8cd7e30ba75494f278e0952547bf3bb430e /libs/input/PointerController.cpp | |
| parent | 8750ab191547cb398d25fd96193fbe7a250c4c27 (diff) | |
Merge together the two LockPatternUtilsTest
There are two LockPatternUtilsTest classes, one in coretests (module:
FrameworksCoreTests) and one in utiltests (module: FrameworksUtilTests).
It is not necessary to have two. The "correct" place seems to be
coretests, since utiltests is intended for tests of simple Java utility
classes that aren't very closely tied to Android. LockPatternUtils is
closely tied to Android. Another issue with the utiltests version of
the test is that it's not currently assigned to the locksettings OWNERS.
Therefore, this CL moves the test cases of the utiltests version of the
test to the coretests version, then deletes the utiltests version.
Bug: 321737173
Ignore-AOSP-First: Conflict due to security fix ag/25939141
Test: atest FrameworksCoreTests:LockPatternUtilsTest
Change-Id: Idf562f9fa65c1d9cc0e9205217f6b8da7627f122
Diffstat (limited to 'libs/input/PointerController.cpp')
0 files changed, 0 insertions, 0 deletions