20
u/omgdonerkebab Sep 10 '17
I'm super excited for nested tests.
https://blog.codefx.org/libraries/junit-5-basics/#Nesting-Tests
Though I prefer Java, for the last year I've been working at a Ruby on Rails shop. But there have been some (few) things that the Ruby ecosystem has gotten right, and one of those is nested tests in Rspec.
Now I can better group my tests up, for example, to test the behavior of a service class for different users or different contexts. And more importantly, I can set up that context with a @BeforeEach method that applies only to the tests in that group.
2
u/jonhanson Sep 11 '17 edited Mar 08 '25
chronophobia ephemeral lysergic metempsychosis peremptory quantifiable retributive zenith
2
u/sormuras Sep 12 '17
That's true -- but the Platform is the basis for other test engines, like http://jqwik.net -- Example Based Testing and Property Based Testing
1
u/cryptos6 Sep 13 '17
Another option providing property based testing would be KotlinTest. However you would write tests in Kotlin (what would be more concise and fun, but is not always possible).
1
u/Feroc Sep 11 '17
Migrated one of our smaller projects this morning. Finding and using the extension for Mockito was the "hardest" part. The rest was pretty straight forward.
1
u/diroussel Sep 11 '17
Got a link for that to save me the time?
1
u/Feroc Sep 11 '17
A link to what?
1
u/diroussel Sep 11 '17
You said finding the extension to mockito was the hard bit. I was hoping you could link to it.
1
u/cryptos6 Sep 13 '17
Is there no such thing as "before suite" and "after suite" to have global setup and teardown? I'm looking for something like TestNG's @BeforeSuite or KotlinTest's beforeAll
1
u/winder Sep 14 '17
That would be @BeforeAll and @AfterAll
1
u/cryptos6 Sep 14 '17
No,
@BeforeAllis executed before all tests of the class. From the documentation:@BeforeAll: Denotes that the annotated method should be executed before all @Test, @RepeatedTest, @ParameterizedTest, and @TestFactory methods in the current class;
0
Sep 10 '17
[deleted]
2
u/secondsun Sep 10 '17
On my phone but I'll try. There's setup that isn't intuitive and it seems like a lot of breaks for no good reason at first. However it has a lot of configurability that didn't exist and parameterized tests are pretty awesome.
As an example you can look at this file and see halfway through I changed to csv parameterized tests. https://github.com/secondsun/sms4j/blob/master/src/test/java/net/saga/console/emulator/sms/sms4j/test/E03_Z80DecrementTest.java
As you can see I switched from each test being for a specific register and then went to passing in the codes as a csv set.
1
Sep 11 '17
I've been using it. Rewrote some rules into extensions. Extensions give more control than rules/runners. Also need less boilerplate code to add them all to a bunch of tests.
28
u/cypher0six Sep 10 '17 edited Sep 10 '17
Is there a list of major changes from 4 to 5 somewhere?
Edit: Found a few high level comparisons:
https://howtodoinjava.com/junit-5/junit-5-vs-junit-4/
https://howtoprogram.xyz/2016/08/10/junit-5-vs-junit-4/
https://www.ibm.com/developerworks/library/j-introducing-junit5-part1-jupiter-api/index.html