Also test with drud/quicksprint

[mglaman]

See https://github.com/drud/quicksprint

[mradcliffe]

I think it should be okay to drop workshop/blob/main/.ddev/docker-compose.testing.yaml and the commands directory into sites/sprint-*/drupal/.config/ after users run start_sprint.sh?

[mglaman]

That's now how I'd configure tests in a client project, though. This repo shows an example of how you'd setup tests in your own project environment.

Maybe I need to just make a PR to that project and document using it?

[mradcliffe]

It looks like the only changes would be to adopt the commands to Drupal core workflow/install rather than a Drupal core-recommended composer workflow since we're setup for core contribution.

Edit: 🙌

OK. 255  total assertions passed (3m 52s)
Done in 237.12s.

[mglaman]

Ah, shoot. I totally forgot that this is using a Composer setup and would make it impossible to do core contribution, but only contrib. Thank you for bringing that up.

I'll have to make that clear. Because this is more of an example of how to configure things. Not a full environment to do those things. Like a reference. Not to replace drud/quicksprint.

[mradcliffe]

I'll have to make that clear. Because this is more of an example of how to configure things. Not a full environment to do those things. Like a reference. Not to replace drud/quicksprint.

That's how I read this. As an example that's adaptable for docker-based workflows lando, ddev, etc... core or custom projects so that more people can create tests for their contrib or personal projects and thus we level up and write more tests for core :-)