FYI: I'm going to run the CQ but it will still fail on the previous test because I did not fix it yet. However I added more unit tests, which I want to run on Win/Mac to see if they pass.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
FYI: I'm going to run the CQ but it will still fail on the previous test because I did not fix it yet. However I added more unit tests, which I want to run on Win/Mac to see if they pass.
Sorry, just Windows (since macOS doesn't use Aura).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
recording_view->exit_location());I think you need to test this in interactive_u_tests, which generates actual native events. I also think you need a child (embedded) window as a target of the native window?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
youI
sorry for incomplete comment. Could you also verify that added tests fails without your patch?
ui::test::EventGenerator generator(Shell::GetPrimaryRootWindow(),Apparently `ui_controls` is not supported on ChromeOS.
Oshima-san, is `ui::test::EventGenerator` the recommended approach on CrOS?
base::RunLoop run_loop;Oshima-san, I know `base::RunLoop`'s are generally discouraged in production code, but here it doesn't seem too bad to use. WDYT?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
ui::test::EventGenerator generator(Shell::GetPrimaryRootWindow(),Apparently `ui_controls` is not supported on ChromeOS.
Oshima-san, is `ui::test::EventGenerator` the recommended approach on CrOS?
It is supported. You have to addd test to interactive_ui_tests. please see
ash/drag_drop/drag_drop_interactive_uitest.cc
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |