-
-
Notifications
You must be signed in to change notification settings - Fork 682
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
Add @Ignore to track unit tests other than first one #101
Comments
I'm not sure we could tell gradle to ignore the ignores, but we could do a A lot of tracks write a script to copy everything to tmp/ first, and then do whatever manipulations, and then finally run all the tests. Not sure if that's the way to go here. |
I think that's pretty much what we're doing with ES and JS. (temp dirs) @jtigger what do you think about that? |
I think we could whip up something using JUnit categories, which are supported by Gradle. Instead of using (We'd need to ship some artifact into maven central or somewhere that includes our category marker interface, |
@sit that sounds like a great idea. Is this something you have time to help with? If not I can give it a try. |
@jtigger @matthewmorgan Took me a while to get around to it, but put together a PR that does what I suggested. It'd require a little work to get a little artifact with the |
Let's just include the annotation file in the source trees. I can't think of a way to get the PGP key onto CI. |
That's a really good point. |
While you can't ignore
|
Reviewed this with @matthewmorgan, this morning (see #139). We discussed that it could be overwhelming to see a 500+ line We've captured that improvement in #141. |
In the JS and ES tracks, all tests except the first for any given problem are disabled by default. This way the user is encouraged to make their solution pass one test at a time, enabling the next test as he or she proceeds.
In JUnit we could use
@Ignore
in front of the@Test
annotation to enable this.There's a second step, how do we tell gradle to ignore
@Ignore
so all the tests get run during development and CI builds?The text was updated successfully, but these errors were encountered: