Improve OpenImageFiles FilesAppBrowserTest speed
Significant test-time can be shaved by testing one image for now since testing two images (previous code) makes MSAN unhappy. Some better way for testing the gallery-open-select-image case seems possible, and one that could also be fast (that case is being removed in the CL). That may be the focus of a future CL, but here our goal is to make the test suite fast by testing one thing in a fixture, not multiple things (see previous code). Herein, test open-an-image-in-gallery meaning one image only, not two (since two costs us 2 x O(1)secs [1]), which might help to get this test re-enabled on MSAN again (issue 837551). As a reminder to future readers, this FilesApp test fixture only tests opening and closing the Gallery from FileApp and that's all that needs testing here. Refer to GalleryBrowserTest for the integration tests of the Gallery features. [1] The time it takes to decode and draw the JPEG image (~1sec) in the test step is way longer than the time it takes libjpeg_turbo to decode it (at most 10ms). Something else is taking up a lot of time, but I am not sure what it is yet: thumb-nailing? image resizing? ... Bug: 837551 Cq-Include-Trybots: luci.chromium.try:closure_compilation Change-Id: I9ac3b0433d8f5fbd2f04516af21bf17482eb8401 Reviewed-on: https://chromium-review.googlesource.com/1106178 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:Naoki Fukino <fukino@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#568798}
Showing
Please register or sign in to comment