Reorder AshTestHelper setup/teardown.
This is in preparation for making AshTestHelper an AuraTestHelper subclass. The primary purpose here is to move the parts of setup/ teardown that will be handled by the AuraTestHelper to the start/end of the ash setup/teardown phases, respectively, so that moving them into AuraTestHelper will not change the relative order of anything. The secondary purpose, subject to the above, is to better group related functionality and add a few comments about ordering requirements. I didn't aim for perfection, just something better. This is split into its own CL since reordering setup/teardown is risky; there are many implicit dependencies. There are some trivial changes: * Removed a null-check of the cursor manager that was only needed for MASH. * Explicitly reset all unique_ptrs during TearDown() rather than waiting until destruction for a few. * Removed CHECK(!::wm::CaptureController::Get()) during teardown; it's not clear to me why we CHECK this but none of the other many bits of state destruction on teardown. Otherwise, should be no functional change. Bug: none Change-Id: Ief088e58606b83e127e93daad0a60f90601b9866 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121085 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#753811}
Showing
This diff is collapsed.
Please register or sign in to comment