Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.6] Switch execution order of testsuites, unit tests first #4687

Merged
merged 1 commit into from Jun 18, 2018
Merged

[5.6] Switch execution order of testsuites, unit tests first #4687

merged 1 commit into from Jun 18, 2018

Conversation

spawnia
Copy link
Contributor

@spawnia spawnia commented Jun 18, 2018

Unit tests usually run faster and provide more fine-granular feedback if something is broken. If some small part of the application is broken, it may easily cause all the feature tests to fail, while not providing useful feedback.

Unit tests usually run faster and provide more fine-granular feedback if something is broken. If some small part of the application is broken, it may easily cause all the feature tests to fail, while not providing useful feedback.
@GrahamCampbell GrahamCampbell changed the title Switch execution order of testsuites, unit tests first [5.6] Switch execution order of testsuites, unit tests first Jun 18, 2018
@taylorotwell taylorotwell merged commit d53539b into laravel:master Jun 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants