Allow chromedriver time to spin up before Wallaby starts firing requests off to it
Allow chromedriver time to spin up before Wallaby starts firing requests off to it

  - we reliably received "(Runtime Error) Wallaby had an internal issue with HTTPoison" on the first test that gets run
    - adding this sleep at the outset of our feature test runs is far from ideal, but it solves the problem
    - see https://github.com/keathley/wallaby/issues/365 for more context

stride-nyc/remote_retro,stride-nyc/remote_retro,stride-nyc/remote_retro