At the moment (Nov 4th 2019) GeckoDriver and FireFox testing is only possible by using the detour via selenium,
and even then it's not really reliable.
### Run codeception tests
#### Start chromedriver
We are running chromedriver in ddev, so if you use ddev everything is just working ;)
In one terminal window, start the chromedriver and leave it running. Port 4444 and url-base `/wd/hub` are taken from
old selenium standards and are default in codeception.
```
chromedriver --url-base=/wd/hub --port=4444
```
### Run codeception tests
#### Run the tests
```
vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance
ddev run --service web vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance
```
With `--steps`, all run steps are outputted to the command line. All errors are reported even if you don't use the
...
...
@@ -65,13 +52,13 @@ a screenshot and the html output of the page the moment a test failed.
To run a single feature just add the path to the feature file to your command, e.g.
```
vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance extensions/t3omy_test/Tests/acceptance/Features/Login.feature
ddev run --service web vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance extensions/t3omy_test/Tests/acceptance/Features/Login.feature
```
You can also run single scenarios by providing line numbers, e.g.
```
vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance extensions/t3omy_test/Tests/acceptance/Features/Login.feature:10
ddev run --service web vendor/bin/codecept -c extensions/t3omy_test/Configuration/codeception.yml --steps run acceptance extensions/t3omy_test/Tests/acceptance/Features/Login.feature:10
```
### Writing tests
...
...
@@ -81,7 +68,7 @@ group your tests.
To get all the available step definitions just run the command