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)

Testing Management

The important thing is not to stop questioning.
- Albert Einstein

This is the final chapter of the book, and its objective is to guide how to understand when and how software testing activities are managed in a living software project. To that aim, this chapter is structured into the following sections:

  • Software development processes: In this section we study when tests are executed in different methodologies: Behavior-Driven Development (BDD), Test-Driven Development (TDD), Test-First Development (TFD) and Test-Last Development (TLD).
  • Continuous Integration (CI): In this section, we will discover CI, the software development practice, in which the process of build, test, and integration is carried out continuously. The common trigger of this process is usually the commit of new changes (patches) to a source code repository (for example, GitHub). In addition...