You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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-skippedwould catch this scenario, but apparently not. Is it possible to do something similar for->only()usage? Or something in thearch()architecture testing abilities?Beta Was this translation helpful? Give feedback.
All reactions