Adds tests for exception handling in queued jobs in the Laravel 9 fixture
I've used docker's init feature to allow running multiple processes in the same docker container. This simplifies the fixture setup as otherwise we'd need 2 more containers — a database and queue worker
When using the init flag docker will spawn an init process as PID 1, which can then spawn more processes. This lets us run the HTTP server and queue worker in the same database. I've configured the fixture to use an sqlite database as well, to avoid having to run a separate database server
The queue worker is started by a new "I start the laravel queue worker" step, which uses docker compose exec to run the actual command in the same container that's running the HTTP server. I've monkey patched this into the Maze::Docker class, but am intending on contributing it back at some point — the change is done but needs some tests in MR itself
The same test will be implemented in other fixtures in separate PRs to avoid this being unreviewable
Goal
Adds tests for exception handling in queued jobs in the Laravel 9 fixture
I've used docker's init feature to allow running multiple processes in the same docker container. This simplifies the fixture setup as otherwise we'd need 2 more containers — a database and queue worker
When using the init flag docker will spawn an init process as PID 1, which can then spawn more processes. This lets us run the HTTP server and queue worker in the same database. I've configured the fixture to use an sqlite database as well, to avoid having to run a separate database server
The queue worker is started by a new "I start the laravel queue worker" step, which uses
docker compose execto run the actual command in the same container that's running the HTTP server. I've monkey patched this into theMaze::Dockerclass, but am intending on contributing it back at some point — the change is done but needs some tests in MR itselfThe same test will be implemented in other fixtures in separate PRs to avoid this being unreviewable