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
Thanks for the suggestion. I think this is really a matter of what is your most frequent use. Could I suggest that for convenience you create an alias in your shell of the smash command with all the switches you most frequently use? You may also want to add --keep-going to this list. For non-interactive smash invocation (e.g. some script or cron) I think it is still a better idea to invoke smash directly with all options explicitly set.
It is not for me personally but for any Dev who might want to quickly run tests while developing in core (not test development)
So far one would always expect all suites to run by default like many other frameworks do (like PHPUnit with data providers). Such devs could think the tests ran fine for them and move on and not realize that they only ran the first test case.
So it is mostly about usability and slightly reducing the barrier of entry.
Is it more common for you guys to only run the first suite than all of them ?
Many people who run the tests manually forget to add "-a" to make sure to run all test cases.
I suggest to reverse the behavior and always run all the test sets by default, unless specified otherwise.
CC @jnfrmarks
The text was updated successfully, but these errors were encountered: