Re: Quo Vadis JUnit
| Newsgroups | gmane.comp.java.junit.user |
|---|---|
| Message-ID | <CALrw-PwEAdfLSRgZ+s-SYVN7GbFh5_sRTX9pDYXNRApBKyyaSA@mail.gmail.com> |
Thanks for this! I think this is a good summary of many of the challenges and opportunities that lie ahead, although a few others come to mind. The "XUnit" philosophy tends to encourage test frameworks to "follow the grain" of the host language, and Java 8 will be altering the "grain" of Java significantly. I put a lot of time into a prototype Java-with-lambdas test framework a year ago, and there are some surprises about what turns out to be easy and hard. I would encourage interested people to proceed without forcing themselves to produce a "JUnit 5" or "JUnit 4.x", however. JUnit 4 was in many ways a completely new framework that had strong interoperability with JUnit 3 as a high-priority design goal, and living with two different frameworks in the same namespace has had benefits and drawbacks. It might be the case that "JUnit 5" ends up the perfect name for what comes out of the discussion, but I wouldn't stress it from the beginning. Jens, might it make sense to create a new mailing list called "Testing Java 8" or something like that, so that people can opt-in to what promises to be an interested and spirited conversation? David On Thu, Oct 23, 2014 at 1:10 AM, [email protected] [junit] < [email protected]> wrote: > > > We had a mighty interesting discussion at the XP-Days about the future of > JUnit or as it was named "Unit & Lambdas" > > > As agreed with Marc and Stefan I put the result in the wiki page: > https://github.com/junit-team/junit/wiki/Quo-Vadis-JUnit > > > Start to discuss NOW :-) > > > Jens > > > > >