The chrome/browser/devtools code looks good to me but I think someone familiar with Android implementation needs to take a look. I have only had a few questions about test expectations.
[PASS FAIL] test_activate_client_windowsis this test flaky now?
[PASS FAIL] test_switch_between_contexts[tab]is this flaky now?
AssertionErrorthere still seems to be an error, as well as for test_multiple_activation, what is the reason for this?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[PASS FAIL] test_activate_client_windowsis this test flaky now?
I reran this with --repeat-each 10 on Android and did not observe a pass. The test now gets past the previously broken windowState path, but still fails consistently on Android activation state
[PASS FAIL] test_switch_between_contexts[tab]Julio Piubellois this flaky now?
I reran the same test on the parent with --repeat-each 10 and saw both PASS and FAIL on main, the flakyness was already there, I updated to match the behavior but if u prefer to keep the CL narrower I can leave it as FAIL, but it would still have a known unexpected-pass
AssertionErrorthere still seems to be an error, as well as for test_multiple_activation, what is the reason for this?
The remaining test_switch_between_contexts[window] failure is the existing Android focus/visibility behavior. The parent shows the same failure; this CL just fixes the Browser window bounds path enough for the test to reach that assertion.
test_multiple_activation was incorrectly listed in the expectation file. It passes repeatedly on both parent and this patch, so I removed that expectation
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Leaving review to meiliang@, please add me if needed / for other uncovered files.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |