Is there currently a way to give neotest-phpunit a test command to run instead of the location of the binary?

[alexandersix]

Hey! I'm really enjoying neotest-phpunit so far, but I've run into one thing that is preventing me from being able to migrate fully over from vim-test.

I've seen the pinned issue for how to run tests in a Docker container (#11 for anyone who hasn't seen it), but I'd actually really like to be able to give the adapter a command to run instead of a path to the PHPUnit binary.

For example, in my vim-test configuration, I have keybinds set up to run php artisan test and sail artisan test for a few Laravel projects that I work on. The latter is great because I don't have to do any sort of configuration to make sure I'm looking at the right binary in my docker containers because Sail (a little command line program that ships with Laravel to work with their development docker setup) manages all of that for me. We have our own docker command line tool at work as well that would benefit from this same setup.

My knowledge of how Neotest and this adapter work is very, very minimal since I just discovered it literally a few days ago, so there's definitely a chance that what I'm suggesting doesn't actually work with Neotest and/or the adapters, but if it could work, I think it would help solve the docker issue, at least in my specific use-case.