Seperate tests by categories, not by different folders #2333
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
koppor
added
the
status: ready-for-review
tobiasdiez
approved these changes
Dec 5, 2016
This prepares to use JUnit categories instead of separate source folders
koppor
removed
the
status: ready-for-review
4 tasks
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.
This implements JabRef#181
Tests are now contained in one folder, but some tests take
@Categoryand they are only called in Travis, not in the normal test flow.Current categories: FetcherTests, DatabaseTests, GUITests.
The integration tests have been renamed to GUITests, because we are currently testing GUI in our "integration" tests.