IntelliJ IDEA and JUnit: Writing, Finding, and Running Tests

Live Webinar
Webinar Agenda

Writing example programs is a good start to ensure your software does what it should do. The goal is for those example programs to be manually and automatically executable. Manual execution is usually performed locally via the command-line interface or from within an IDE, while automatic execution is done remotely via continuous integration services and headless tooling support.

JUnit 5, which consists of two major components, the JUnit Platform and Test Engines, enables software authors and tool developers alike to achieve those goals.

This session will start with build-tool-agnostic approach to finish with the "Mainrunner" test engine in order to show that plain Java programs are executable as tests.

Viewers are encouraged to

Happy testing!

Speaking to you

Christian Stein
Christian Stein works on Language Tools in Oracle’s Java Platform Group. In parallel, as a member of the JUnit Team, he explores and blogs about Testing in the Modular World, builds a module-only build tool called bach, and is also on a self-chosen mission to bring (or at least collect) Java modules to "all" open source projects.

Modules, modules everywhere

And class-path hell did shrink

Modules, modules everywhere

Let `sun.misc.Unsafe` sink