ivanursul

Trying new JUnit 5 - let's extend everything

  Comments  

General idea

</a>

Recently, new JUnit version has been released. I found many useful things. Besides, there’re lot’s of useless features. At least, I think something won’t be used in new JUnit version. By the way, here the new version - JUnit 5

JUnit Goal

</a>

It’s obvious, that JUnit decided to make their product more opensource - by releasing instruments, which will allow junit users to create lot’s of extensions

Restrictions

</a>

Story about another package

</a>

New version has new package - org.junit.jupiter.*. This was done, mostly, for separating new version from previous versions, which completely differs.

Transformations

</a>

All core annotation are located under org.junit.jupiter.api

As you can see, JUnit made a lot of work on renaming it’s annotation

Nested tests

</a>

Now, you can write tests classes inside your test classes. Purposes ? Don’t know :)

@DisplayName("A stack")
class TestingAStackDemo {

    Stack<Object> stack;
    boolean isRun = false;

    @Test
    @DisplayName("is instantiated with new Stack()")
    void isInstantiatedWithNew() {
        new Stack<Object>();
    }

    @Nested
    @DisplayName("when new")
    class WhenNew {

        @BeforeEach
        void init() {
            stack = new Stack<Object>();
        }

        @Test
        @DisplayName("is empty")
        void isEmpty() {
            Assertions.assertTrue(stack.isEmpty());
        }

        @Test
        @DisplayName("throws EmptyStackException when popped")
        void throwsExceptionWhenPopped() {
            Assertions.expectThrows(EmptyStackException.class, () -> stack.pop());
        }

        @Test
        @DisplayName("throws EmptyStackException when peeked")
        void throwsExceptionWhenPeeked() {
            Assertions.expectThrows(EmptyStackException.class, () -> stack.peek());
        }

        @Nested
        @DisplayName("after pushing an element")
        class AfterPushing {

            String anElement = "an element";

            @BeforeEach
            void init() {
                stack.push(anElement);
            }

            @Test
            @DisplayName("it is no longer empty")
            void isEmpty() {
                Assertions.assertFalse(stack.isEmpty());
            }

            @Test
            @DisplayName("returns the element when popped and is empty")
            void returnElementWhenPopped() {
                Assertions.assertEquals(anElement, stack.pop());
                Assertions.assertTrue(stack.isEmpty());
            }

            @Test
            @DisplayName("returns the element when peeked but remains not empty")
            void returnElementWhenPeeked() {
                Assertions.assertEquals(anElement, stack.peek());
                Assertions.assertFalse(stack.isEmpty());
            }
        }
    }
}

Extensions instead of abstract before/after classes

</a>

The idea of extensions is to provide an abstractions for operations, which had place before or after test execution in JUnit 3,4. This allows you to move all non-business logic from before/after sections to extensions

The following interfaces define the APIs for extending tests at various points in the test execution lifecycle. Consult the following sections for examples and the Javadoc for each of these interfaces in the org.junit.jupiter.api.extension package for further details:

Dependency injection. Injection test context

</a>

This version of Junit brings dependency injection for constructors and methods. ParameterResolver is an API you should implement for your extension in order to use Dependency injection. Junit 5 ships with two pre-build parameter resolvers:

How to migrate. JUnit Vintage.

</a>

You should have junit-vintage jar in your project. Juniter Platform Launcer will automaticalyy pick up all tests then.

</a>

![](assets/images/