Mastering Software Testing with JUnit 5

By : Boni Garcia

4.3 (8)

Buy this Book

Mastering Software Testing with JUnit 5

4.3 (8)

By: Boni Garcia

Buy this Book

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.

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

Retrospective On Software Quality And Java Testing

Software quality

Software testing

Testing frameworks for the JVM

Summary

What’s New In JUnit 5

Road to JUnit 5

JUnit 5 architecture

Running tests in JUnit 5

The extension model of JUnit 5

Summary

JUnit 5 Standard Tests

Test lifecycle

Assertions

Tagging and filtering tests

Conditional test execution

Nested tests

Repeated tests

Migration from JUnit 4 to JUnit 5

Summary

Simplifying Testing With Advanced JUnit Features

Dependency injection

Dynamic tests

Test interfaces

Test templates

Parameterized tests

Java 9

Beyond JUnit 5.0

Summary

Integration Of JUnit 5 With External Frameworks

Mockito

Spring

Selenium

Cucumber

Docker

Android

REST

Summary

From Requirements To Test Cases

The importance of requirements

Test planning

Test design

Software testing principles

Test anti-patterns

Summary

Testing Management

Software development processes

Continuous Integration

Test reporting

Defect-tracking systems

Static analysis

Putting all pieces together

Summary

Customer Reviews

4.3 (8)

5 star

75%

4 star

3 star

2 star

25%

1 star

Continuous Integration

The concept of CI was first coined on 1991 by Grady Booch (American software engineer, best known for the development of UML together with Ivar Jacobson and James Rumbaugh). The Extreme Programming (XP) methodology adopted this term, making it very popular. According to Martin Fowler, CI is defined as follows:

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible.

In CI systems, we can identify different parts. First, we need a source code repository, which is a file archive to host the source code of our software project, typically using a version control system. Nowadays, the preferred...