junit.tar.gz

Parameter

Annotation

Slow

file

json

JUnit 5 is a standard framework for unit testing in Java. Released in 2017, JUnit 5 is a major improvement over JUnit 4 and supports a lot of new methods. Many projects have migrated from JUnit 4 to JUnit 5. JUnit 5 is also the default test framework for new projects. JUnit 5 is composed of three sub-projects: JUnit Platform, JUnit Jupiter, and JUnit Vintage. Details of these sub-projects are discussed in the course.

This course first discusses the advantages of JUnit 5 over the previous versions and then jumps directly into tests. The course includes discussion on assertions, assumptions, tagging and filtering, nested tests, dependency injection, repeated tests, parameterized tests, dynamic tests, test instance lifecycle, extension model, JUnit 4 migration, JUnit platform, and test execution order. 

By the end of this course, you’ll be deeply familiar with unit testing in JUnit 5. There’s also a little project for you at the end to put your newly acquired skills to the test.

All About JUnit5

## The `ExtensionContext` interface
When building extensions, the most important concept to understand is the `ExtensionContext` interface. It contains context information about the currently running test class or method. Instances of `ExtensionContext` pass to extensions as parameters that allow them to access necessary context information. They’re organized in a hierarchical way. An `ExtensionContext` can have a parent `ExtensionContext`. For example, the `ExtensionContext` of a test class is the parent of the `ExtensionContext` of a test method in this class. The `ExtensionContext` of a nested class annotated with `@Nested` is the child of the `ExtensionContext` of its parent class.

The table below shows the methods of `ExtensionContext`.

# The `ExtensionContext` interface
When building extensions, the most important concept to understand is the `ExtensionContext` interface. It contains context information about the currently running test class or method. Instances of `ExtensionContext` pass to extensions as parameters that allow them to access necessary context information. They’re organized in a hierarchical way. An `ExtensionContext` can have a parent `ExtensionContext`. For example, the `ExtensionContext` of a test class is the parent of the `ExtensionContext` of a test method in this class. The `ExtensionContext` of a nested class annotated with `@Nested` is the child of the `ExtensionContext` of its parent class.

The table below shows the methods of `ExtensionContext`.

Understand how to build ExtensionContext in JUnit 5.

Getting Started

Writing Basic Tests

Annotations, Tagging, and Filtering

Nested tests in JUnit 5

Dependency Injections

Parameterized and Dynamic Tests

Test Instance Lifecycle in JUnit 5

Extension Model

JUnit Platform

Test Execution Order

Conclusion

Library Management System

Extension Context

The `ExtensionContext` interface