Setting a CI to run Laravel Dusk test on every commit.

What is the purpose of the article or tutorial?

To help people to setup their GitLab CI to run Laravel Dusk test.

What value does it offer the reader?

They can have a CI run on every test, making sure their changes did not break anything.

What can they do after reading the article?

Setup a GitLab CI to run their Laravel Dusk test on every commit.

---

Attention

Before submitting a proposal to write about this topic:

• Read through the Community Writers Program.
• Read through the Terms and Conditions.
• Please advise, for this program you'll write a technical article according to this Writing Method.

Would love to see this.

In the mean time, if anyone who stumbles here has resources to share, please sent them my way!

I join to this request.

Currently looking into this myself for my study project. Will report back when I have something useful. Shouldn't be that hard if I look in how environments work (although, not for every commit, but for every MR and staging/live branche).

assigned to @afolson

@afolson are you taking this or can we make it blog-posts~846186?

It's a lower priority than other stuff I have going right now, but if there's an immediate need then someone else is welcome to do it.

removed assignee

Thank you @afolson :)

added blog-posts~846186 label

moved from blog-posts#340 (closed)

added GitLab CI label

You can try this repo https://hub.docker.com/r/chilio/laravel-dusk-ci/