Improve flicker memory consumption with the following: - Use a static factory for better compatibility with JUnit4 ParameterizedRunner - Ensure `cleanUp` is always called, even when an exception occurs Bug: 178572522 Test: atest FlickerTests WMShellFlickerTests Change-Id: Id9e539c0e8bce350f94811cab58a726e47aac525
WM Shell Flicker Test Package
Please reference the following links
on what is Flicker Test and how to write a Flicker Test
To run the Flicker Tests for WM Shell, simply run atest WMShellFlickerTests