JUnit 5 @ Solutions HH

956c7d246841e8507a1e1b96842994db?s=47 Marc Philipp
September 06, 2017

JUnit 5 @ Solutions HH

956c7d246841e8507a1e1b96842994db?s=128

Marc Philipp

September 06, 2017
Tweet

Transcript

  1. 1.
  2. 2.

    Christian Stein • Software developer @ MICROMATA Kassel/Bonn • JUnit

    5 core team member since 2017 • Github: https://github.com/sormuras • Twitter: @sormuras
  3. 3.

    Marc Philipp • Staff Software Engineer @ in Karlsruhe •

    JUnit Maintainer since 2012 • Twitter: @marcphilipp • Web: http://www.marcphilipp.de
  4. 6.

    Meta Annotations Annotations can be combined to enable re-use:
 


    @Target(ElementType.METHOD)
 @Retention(RetentionPolicy.RUNTIME)
 @Tag("integration")
 @Test
 public @interface IntegrationTest {} Usage:
 
 @IntegrationTest
 void test() {}
 Equivalent:
 
 @Tag("integration")
 @Test
 void test() {}
  5. 7.

    @ParameterizedTest Sources • @ValueSource(ints = { 1, 2, 3 })

    • @EnumSource(TimeUnit.class) • @MethodSource(names = "myProviderMethod") • @CsvSource({ "foo, 1", "bar, 2", "'baz, qux', 3" }) • @CsvFileSource(resources = "/two-column.csv") • @ArgumentsSource(MyArgumentsProvider.class) • @YourCustomSource
  6. 8.

    @Nested Tests @DisplayName("A stack") class TestingAStackDemo { @Test @DisplayName("is instantiated

    with new Stack()") void isInstantiatedWithNew() {/* ... */} @Nested @DisplayName("when new") class WhenNew { @BeforeEach void createNewStack() {/* ... */} @Test @DisplayName("is empty") void isEmpty() {/* ... */} // ... @Nested @DisplayName("after pushing an element") class AfterPushing { @BeforeEach void pushAnElement() {/* ... */} @Test @DisplayName("it is no longer empty") void isNotEmpty() {/* ... */} // ... } } }
  7. 9.

    Dynamic Tests @TestFactory Stream<DynamicTest> dynamicTestsFromStream() { return IntStream.iterate(0, n ->

    n + 2).limit(100) .mapToObj(n -> dynamicTest("test" + n, () -> { assertTrue(n % 2 == 0); })); }
  8. 12.

    Runner • Very powerful: Almost every aspect of test execution

    can be changed • But: You can only have one Runner per test class! • You can’t combine Runners, e.g.
 SpringJUnit4ClassRunner + Parameterized
  9. 13.

    Rules • Extension mechanism introduced in JUnit 4.7 • Wraps

    execution of a test (@Rule) or a test class (@ClassRule) • Designed to be combined — great for simple use cases • But: a single rule cannot be used for method-level and class-level callbacks, no support for instance-level callbacks
  10. 18.

    Design Goals for JUnit 5 • Modern programming model for

    writing tests (Java 8!) • Powerful extension model with a focus on composability • API Segregation: Decouple test execution/reporting from test definition • Compatibility with older releases + migration path • Modularization + no external dependencies
  11. 20.

    Separation of Concerns 1. An API to write tests (Jupiter

    API) 2. Extensible mechanisms to discover and execute tests (Test Engine SPI) 3. An API for test execution by tools (Launcher API)
  12. 21.

    P L AT F O R M J U P

    I T E R V I N TA G E P A R T Y T H I R D
  13. 22.

    P L AT F O R M J U P

    I T E R V I N TA G E P A R T Y T H I R D
  14. 25.

    IDE Support • IntelliJ supports JUnit 5 ≥ M2 since

    2016.2 • Eclipse support is available on Eclipse Marketplace:
 https://marketplace.eclipse.org/content/junit-5-support- beta-oxygen
 Will be integrated without requiring any additional work in Oxygen.1a • Interim solution for other IDEs: JUnitPlatform Runner
  15. 27.

    Compatibility • Backward compatibility (junit-vintage-engine) enables gradual migration of tests

    to Jupiter API • Forward compatibility (JUnitPlatform Runner) allows test execution with “old” tools
  16. 29.

    Extension Registration • Declarative: Annotate your test classes or methods

    with @ExtendWith to register extensions • Supports an arbitrary number of extensions at the same time • May be used as a meta-annotation • Global: Opt-in support for registration via ServiceLoader
  17. 31.

    Extension Points • Conditional Test Execution • ExecutionCondition • General

    Purpose • TestInstancePostProcessor • ParameterResolver • TestTemplateInvocationContext- Provider • Test Lifecycle Callbacks • BeforeAllCallback • BeforeEachCallback • BeforeTestExecutionCallback • TestExecutionExceptionHandler • AfterTestExecutionCallback • AfterEachCallback • AfterAllCallback
  18. 32.

    Roadmap • 5.0 M4 (April 2017): parameterized and repeated tests

    ✔ • 5.0 M5 (June 2017): dynamic containers, test instance lifecycle management, and minor API changes ✔ • 5.0 M6 (July 2017): Java 9 compatibility, validation (e.g. tag syntax), and bug fixes ✔ • 5.0 RC1, RC2, RC3 (July/August 2017): bug fixes and documentation improvements before GA. ✔ • 5.0 GA (this week, really!): First general availability release • 5.1 (October?): additional features
  19. 33.
  20. 34.

    What’s in it for me? • Modern programming model •

    Powerful extension points • Gentle migration path • Good tool support • Flexible platform/plugin architecture
  21. 35.

    Getting Started User Guide:
 http://junit.org/junit5/docs/current/user-guide/ Sample projects for Gradle and

    Maven:
 https://github.com/junit-team/junit5-samples Javadoc:
 http://junit.org/junit5/docs/current/api/