This PR implements a significant update to how tok test runs. In particular:
Nightwatch (NW) is now run from inside Tokaido, rather than trying to run on the user's host
If not running, a Chromedriver container is added to docker-compose which is then restarted
NW is pointed at the haproxy container, and the user is alerted if they need to change the core NW config files to support HTTPS-based tests (Drupal core only works with HTTP at the moment, it seems)
A mysql Service is added which can be used to automatically created a 'tests' database so that the main tokaido database isn't changed by the tests
Added a lot more debug output to show what is going on
This definitely isn't the end of our 'tok test' functionality, and I've now labelled the feature as 'beta' and asked users for help and feedback when using it. Overall Nightwatch feels like the wrong fit for what we want, and we might end up swapping to Behat or some other framework depending on what users have to say.
This PR implements a significant update to how
tok testruns. In particular:This definitely isn't the end of our 'tok test' functionality, and I've now labelled the feature as 'beta' and asked users for help and feedback when using it. Overall Nightwatch feels like the wrong fit for what we want, and we might end up swapping to Behat or some other framework depending on what users have to say.