Book Image

Mastering Software Testing with JUnit 5

By : Boni Garcia
Book Image

Mastering Software Testing with JUnit 5

By: Boni Garcia

Overview of this book

When building an application it is of utmost importance to have clean code, a productive environment and efficient systems in place. Having automated unit testing in place helps developers to achieve these goals. The JUnit testing framework is a popular choice among Java developers and has recently released a major version update with JUnit 5. This book shows you how to make use of the power of JUnit 5 to write better software. The book begins with an introduction to software quality and software testing. After that, you will see an in-depth analysis of all the features of Jupiter, the new programming and extension model provided by JUnit 5. You will learn how to integrate JUnit 5 with other frameworks such as Mockito, Spring, Selenium, Cucumber, and Docker. After the technical features of JUnit 5, the final part of this book will train you for the daily work of a software tester. You will learn best practices for writing meaningful tests. Finally, you will learn how software testing fits into the overall software development process, and sits alongside continuous integration, defect tracking, and test reporting.
Table of Contents (8 chapters)

Summary

This chapter contains a comprehensive summary of the advance capabilities to write rich Jupiter tests driven by examples. First, we have learned that parameters can be injected in constructor and methods in test classes. JUnit 5 provides three parameter resolvers out of the box, namely resolver for parameters of the type TestInfo (to retrieve information about the current test), resolver for parameters of the type RepetitionInfo (to retrieve information about the current repetition), and resolver for parameters of the type TestReporter (to publish additional data about the current test run).

Another new feature implemented in Jupiter is the concept of dynamic tests. So far in JUnit 3 and 4, tests are defined at compile time (that is static tests). Jupiter introduces the annotation @TestFactory that allows to generate test at runtime. Another new concept...