Functional tests start before Selenium is ready

[schrolla]

🐛 Summary

The functional test framework relies on the Selenium web testing framework and associated ChromeDriver to function. Sometimes, the first test is run before the ChromeDriver and Selenium are fully ready and listening locally for interaction. As a result, the first test in a testplan may fail with an error.

To reproduce

Steps to reproduce the behavior:

1. Run functional tests
2. Review results for testplans with failures in the first test that indicates "Unable to connect to remote server"

Expected behavior

Selenium and the chrome driver to be up and ready by the time tests need it and execute without error.

Any helpful log output or screenshots

Example of the error seen when this bug is triggered.

[james-garriss]

Should this issue be linked to #1525? If we replace Selenium with something else, say Beautiful Soup, then possibly this issue will just go away.