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
As you've probably seen in the Test-Driven Laravel course already, there's a section on integration testing that explains why you may want to run the whole suite excluding certain groups.
It would be awesome to be able to configure additional options for each of the three test types (method, class, and suite).
The text was updated successfully, but these errors were encountered:
I was wondering about that, too… At first, I was thinking it'd be nice to have inputs dedicated to each setting, but that'd probably just be a waste of time for whomever writes that code and overwhelming for users.
Text fields are probably the most flexible and simplest solution.
I'm particularly interested in seeing progress on this as I want to be able to run Laravel Dusk tests. The tests do run at present, however because you aren't able to pass additional commands, the .env.dusk.* file isn't renamed prior to the test running, which results in various testing errors.
PHPUnit allows you to pass options.
As you've probably seen in the Test-Driven Laravel course already, there's a section on integration testing that explains why you may want to run the whole suite excluding certain groups.
It would be awesome to be able to configure additional options for each of the three test types (method, class, and suite).
The text was updated successfully, but these errors were encountered: