diff options
| author | Yunfan Chen <yunfanc@google.com> | 2019-02-08 16:14:14 +0900 |
|---|---|---|
| committer | Yunfan Chen <yunfanc@google.com> | 2019-02-08 20:47:17 +0900 |
| commit | db39c1668c50a14bc8ef97cbca0267f7d11da85b (patch) | |
| tree | 56ce8b9b574f4566d08292fe9f21d9c9b4e989de /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 2b635eeb51e4deec7c1d4dfa669a9a07e8b4c2d1 (diff) | |
Fix flaky testVisibleWithInsetsProvider test
The test would always fail if we wait until the handler idle. The reason
is, when layoutAndAssignWindowLayersIfNeeded is called, in
DisplayPolicy, the mTopFullscreenOpaqueWindowState will take the control
of the insets visibility back by calling onControlChanged. At that time,
the visibility will get back to true, no matter what happened before.
Mock the DC and let the function do nothing would help the test to be a
unit test and all the test will be no longer flaky.
Test: atest WindowStateTests
Bug: 74078662
Bug: 69229402
Change-Id: I91255e2e7d5c8f2dcdf3faf72aa87c4df77a94ec
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions