Adding this caught a couple of important things:
- The sound integration tests have a `.only` in them
- The project-saver-hoc tests had two tests with the same description, causing possible confusion if that test broke

These were causing the tests to fail and should be fixed by the update to FindByXpath function.

They're spammy — happy to put this back but they were unhelpful while fixing tests IMO.

Fix integration tests for the recent chrome stable update

Adding `import 'chromedriver';` causes the module to register the path
to `chromedriver` / `chromedriver.exe` automatically, fixing this error:
```
The ChromeDriver could not be found on the current PATH. Please download the latest version of the ChromeDriver from http://chromedriver.storage.googleapis.com/index.html and ensure it can be found on your PATH.
        at Error (native)
```

This should fix the integration test failures on the extensions branch.
Thanks @paulkaplan for figuring this out!