detecting and preventing use of only() in production CI

[ceejayoz]

We occasionally use ->only() during development. Even more occasionally, it makes it into a commit, which results in our CI happily running just the one test instead of the entire suite.

I'd hoped --fail-on-skipped would catch this scenario, but apparently not. Is it possible to do something similar for ->only() usage? Or something in the arch() architecture testing abilities?

[markhuot]

Just came across this same issue. I was hoping arch() would solve it with something like this but didn't find anything,

arch()->expect('./tests')->not->toUse('only');

But that doesn't work for a number of reasons. Probably need a dedicated expectation for this?