OLD Material to Consider - junit-team/junit-framework GitHub Wiki
Let's add existing stuff (like JUnit 4 extensions) that might be valuable input for JUnit Lambda...
External Material
- Quo Vadis JUnit
- Started by an open-space session during XP-Days Germany in October 2014
- LambdaSpec: RSpec like testing with Java lambdas.
- Jumi: Parallel test execution by default. Backwards compatible to JUnit.
- Hierarchical Context Runner: Runner for JUnit by Stefan Bechtold.
- Hierarchical testing with @Context: Also from Stefan.
- Exception testing with Lambdas - 1
- Exception testing with Lambdas - 2
- Combining matchers, streams and lambdas
- JUnit Java8 Runner: Allowing test methods in interfaces.
- JUnit Quickcheck: A quickcheck reimplementation in Java building on JUnit theories
- Better Category Support: Category support in JUnit 4.x lags behind NUnit. Specifically the need to use @SuiteClasses() puts categories back in the world of JUnit 3 where we had to predefine the suite before run time. - Mark Levison @mlevison
- Parameterization
- junit-dataprovider
- junitparams
- lambda-parameterized: Proof of concept for type safe parameterized JUnit 4 tests with the help of lambda expressions.
- Parameterized Tests based on JUnit Rules The reason why I think this is interesting, because it proves that you don't need any special test discovery mechanism to support parameterized tests. No annotations, no special add on, just a rule.
- A little repository where I play around with my ideas, how JUnit Lambda might look like: https://github.com/schauder/junit5-spike
- Tumbler-Glass, a metadata injection and reporting tool - mlschechter
- Some Java8 experiments
- Lambda-Behave: A test framework for Java 8 based on lambdas.
- lambspec, an RSpec-like assertion library for Java >= 8.
Early proposals from JUnit team
###Proposal 1 : Using initialization blocks and lambdas to define tests
###Proposal 2 : Using different kinds of decorators, categories and other ideas