Automated Tests with Laravel Dusk on Gitlab CI/CD

I think the problem with the MySQL service is that the 5.7 tag is expose multiple ports. Gitlab has an open issue with services that expose multiple ports.
I was able to get the MySQL service running by specifying an explicit version, eg: 5.7.21
I also had a problem with the ENV variables being passed to Laravel when Dusk was running. I recommend not using the `variables` section for Laravel variables, and instead create a dedicated `.env.dusk.*` file.
- Dusk: laravel.com/do...
- Gitlab CI/CD: docs.gitlab.co...
---
Thanks for watching!
Twitter: / owenconti
Website: owenconti.com

[@lynic-0091]

Oh my god I'm so close to getting this to work thanks to you, however, my dusk says it cant see the text I'm trying to assert.
How can I see the screenshots the gitlab CI is making? Or how can I fix this?
PS the test turns out OK locally, but not on GitLab

[@owenconti]

Make sure you are publishing artifacts when you're tests fail, like this: gist.github.com/owenconti/988fbbb93873f7698a57735893d255d0
Then you can view the artifacts from the job in the Gitlab UI once the job fails.

[@johnmurfett3813]

Did you manage to get this working? Not much point in running dusk in a system that does uses a memory database, except for purely academic purposes.

[@owenconti]

Yes, I did. Check the description of the video. I had to specify the exact MySQL version, eg: 5.7.21