Do not manually include fixture files during tests so one plugin can't break tests of another #8906
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…during tests. Fixes case when one plugin has issue in fixture class making it impossible to run tests (since the tests:run will just fail).
diosmosis
added
Bug
diosmosis
added a commit
that referenced
this pull request
Oct 4, 2015
Do not manually include fixture files during tests so one plugin can't break tests of another
mattab
added
the
not-in-changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since autoloading is used now, we do not need to manually include fixture files during tests.
Fixes the case when one plugin has issue in fixture class making it impossible to run tests (since the tests:run will just fail).