Initial POC of how to ignore all-but-first test #106
Merged
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
Introduce a new JUnit test category that lets us mark certain tests as not ready for execution. The test task in the individual project can then be configured to not run tests marked as `NotReady`. For the CI server builds, add a fullTest test task that simply runs tests as normal, and link it into the check task so it runs on builds. This is not perfect, as the class under test must still compile, so it must have at least the correct signatures of all the methods tested. Also, it may be worth finding a way to distribute the NotReady interface that doesn't require checking it into every project.
|
Having an example to talk to is very helpful, @sit; thanks! Chewing... :) |
|
@sit do you have time to flesh this out? Otherwise, either @matthewmorgan or myself could do the grunt work. |
|
@matthewmorgan and I are picking this one up. We agreed that @sit's approach is the way forward, here. Thanks! |
|
Yikes! So sorry for squatting on this issue. :( Really want to see this implemented. Recently, @matthewmorgan and I have been focusing on some amateur data science'ing, but perhaps we'll clear out some of these PRs and issues too. |
|
Starting with Emil's (@sit) work. I'm hoping this will preserve history/blame/credit. |
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.
Introduce a new JUnit test category that lets us mark certain tests as
not ready for execution. The test task in the individual project
can then be configured to not run tests marked as
NotReady.For the CI server builds, add a fullTest test task that simply runs
tests as normal, and link it into the check task so it runs on builds.
This is not perfect, as the class under test must still compile, so it
must have at least the correct signatures of all the methods tested.
Also, it may be worth finding a way to distribute the NotReady interface
that doesn't require checking it into every project.
This will fix #101.