Disable built-in TTS engine during Chrome OS accessibility E2E tests
All of these tests were triggering starting the "real" TTS engine, even though a mock TTS engine was installed. I ran all of the ChromeVoxBackground tests before and after this change on my system with --test-launcher-jobs=20. If the speech engine is installed, the average test time drops 30%, from 8200 ms to 6200 ms. Even if the speech engine is not installed, it still drops 25% from 7700 ms to 6200 ms. Bug: none Change-Id: Iea23951ce397176cd1fda64d801422f3031a1fba AX-Relnotes: N/A Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422585 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#810437}
Showing
Please register or sign in to comment