book

JUnit in Action, Third Edition

Name: JUnit in Action, Third Edition
Author: Catalin Tudose
ISBN: 9781617297045

by Catalin Tudose

January 2021

Intermediate to advanced

560 pages

15h 13m

English

Manning Publications

Read now

Unlock full access

JUnit in Action
Copyright
dedication
contents
front matter
prefaceacknowledgmentsabout this bookWho should read this bookHow this book is organized: A roadmapAbout the codeliveBook discussion forumabout the authorabout the cover illustration
Part 1. JUnit
1 JUnit jump-start
1.1 Proving that a program works1.2 Starting from scratch1.2.1 Understanding unit testing frameworks1.2.2 Adding unit tests1.3 Setting up JUnit1.4 Testing with JUnitSummary
2 Exploring core JUnit
2.1 Core annotations2.1.1 The @DisplayName annotation2.1.2 The @Disabled annotation2.2 Nested tests2.3 Tagged tests2.4 Assertions2.5 Assumptions2.6 Dependency injection in JUnit 52.6.1 TestInfoParameterResolver2.6.2 TestReporterParameterResolver2.6.3 RepetitionInfoParameterResolver2.7 Repeated tests2.8 Parameterized tests2.9 Dynamic tests2.10 Using Hamcrest matchersSummary
3 JUnit architecture
3.1 The concept and importance of software architecture3.1.1 Story 1: The telephone directories3.1.2 Story 2: The sneakers manufacturer3.2 The JUnit 4 architecture3.2.1 JUnit 4 modularity3.2.2 JUnit 4 runners3.2.3 JUnit 4 rules3.2.4 Shortcomings of the JUnit 4 architecture3.3 The JUnit 5 architecture3.3.1 JUnit 5 modularity3.3.2 JUnit Platform3.3.3 JUnit Jupiter3.3.4 JUnit Vintage3.3.5 The big picture of the JUnit 5 architectureSummary
4 Migrating from JUnit 4 to JUnit 5
4.1 Migration steps between JUnit 4 and JUnit 54.2 Needed dependencies4.3 Annotations, classes, and methods4.3.1 Equivalent annotations, classes, and methods4.3.2 Categories vs. tags4.3.3 Migrating Hamcrest matcher functionality4.3.4 Rules vs. the extension model4.3.5 Custom rulesSummary

5 Software testing principles
5.1 The need for unit tests5.1.1 Allowing greater test coverage5.1.2 Increasing team productivity5.1.3 Detecting regressions and limiting debugging5.1.4 Refactoring with confidence5.1.5 Improving implementation5.1.6 Documenting expected behavior5.1.7 Enabling code coverage and other metrics5.2 Test types5.2.1 Unit testing5.2.2 Integration software testingSystem software testingAcceptance software testing5.3 Black-box vs. white-box testing5.3.1 Black-box testing5.3.2 White-box testing5.3.3 Pros and consSummary
Part 2. Different testing strategies
6 Test quality
6.1 Measuring test coverage6.1.1 Introduction to test coverage6.1.2 Tools for measuring code coverage6.2 Writing testable code6.2.1 Understanding that public APIs are contracts6.2.2 Reducing dependencies6.2.3 Creating simple constructors6.2.4 Following the Law of Demeter (Principle of Least Knowledge)6.2.5 Avoiding hidden dependencies and global state6.2.6 Favoring generic methods6.2.7 Favoring composition over inheritance6.2.8 Favoring polymorphism over conditionals6.3 Test-driven development6.3.1 Adapting the development cycle6.3.2 Doing the TDD two-step6.4 Behavior-driven development6.5 Mutation testing6.6 Testing in the development cycleSummary
7 Coarse-grained testing with stubs
7.1 Introducing stubs7.2 Stubbing an HTTP connection7.2.1 Choosing a stubbing solution7.2.2 Using Jetty as an embedded server7.3 Stubbing the web server resources7.3.1 Setting up the first stub test7.3.2 Reviewing the first stub test7.4 Stubbing the connection7.4.1 Producing a custom URL protocol handler7.4.2 Creating a JDK HttpURLConnection stub7.4.3 Running the testSummary
8 Testing with mock objects
8.1 Introducing mock objects8.2 Unit testing with mock objects8.3 Refactoring with mock objects8.3.1 Refactoring example8.3.2 Refactoring considerations8.4 Mocking an HTTP connection8.4.1 Defining the mock objects8.4.2 Testing a sample method8.4.3 Try #1: Easy refactoring technique8.4.4 Try #2: Refactoring by using a class factory8.5 Using mocks as Trojan horses8.6 Introducing mock frameworks8.6.1 Using EasyMock8.6.2 Using JMock8.6.3 Using MockitoSummary
9 In-container testing
9.1 Limitations of standard unit testing9.2 The mock-objects solution9.3 The step to in-container testing9.3.1 Implementation strategies9.3.2 In-container testing frameworks9.4 Comparing stubs, mock objects, and in-container testing9.4.1 Stubs evaluation9.4.2 Mock-objects evaluation9.4.3 In-container testing evaluation9.5 Testing with ArquillianSummary
Part 3. Working with JUnit 5 and other tools
10 Running JUnit tests from Maven 3
10.1 Setting up a Maven project10.2 Using the Maven plugins10.2.1 Maven compiler plugin10.2.2 Maven Surefire plugin10.2.3 Generating HTML JUnit reports with Maven10.3 Putting it all together10.4 Maven challengesSummary
11 Running JUnit tests from Gradle 6
11.1 Introducing Gradle11.2 Setting up a Gradle project11.3 Using Gradle plugins11.4 Creating a Gradle project from scratch and testing it with JUnit 511.5 Comparing Gradle and MavenSummary
12 JUnit 5 IDE support
12.1 Using JUnit 5 with IntelliJ IDEA12.2 Using JUnit 5 with Eclipse12.3 Using JUnit 5 with NetBeans12.4 Comparing JUnit 5 usage in IntelliJ, Eclipse, and NetBeansSummary
13 Continuous integration with JUnit 5
13.1 Continuous integration testing13.2 Introducing Jenkins13.3 Practicing CI on a team13.4 Configuring Jenkins13.5 Working on tasks in a CI environmentSummary
Part 4. Working with modern frameworks and JUnit 5
14 JUnit 5 extension model
14.1 Introducing the JUnit 5 extension model14.2 Creating a JUnit 5 extension14.3 Writing JUnit 5 tests using the available extension points14.3.1 Persisting passengers to a database14.3.2 Checking the uniqueness of passengersSummary
15 Presentation-layer testing
15.1 Choosing a testing framework15.2 Introducing HtmlUnit15.2.1 A live example15.3 Writing HtmlUnit tests15.3.1 HTML assertions15.3.2 Testing for a specific web browser15.3.3 Testing more than one web browser15.3.4 Creating standalone tests15.3.5 Testing forms15.3.6 Testing JavaScript15.4 Introducing Selenium15.5 Writing Selenium tests15.5.1 Testing for a specific web browser15.5.2 Testing navigation using a web browser15.5.3 Testing more than one web browser15.5.4 Testing Google search and navigation using different web browsers15.5.5 Testing website authentication15.6 HtmlUnit vs. SeleniumSummary
16 Testing Spring applications
16.1 Introducing the Spring Framework16.2 Introducing dependency injection16.3 Using and testing a Spring application16.3.1 Creating the Spring context programmatically16.3.2 Using the Spring TestContext framework16.4 Using SpringExtension for JUnit Jupiter16.5 Adding a new feature and testing it with JUnit 5Summary
17 Testing Spring Boot applications
17.1 Introducing Spring Boot17.2 Creating a project with Spring Initializr17.3 Moving the Spring application to Spring Boot17.4 Implementing a test-specific configuration for Spring Boot17.5 Adding and testing a new feature in the Spring Boot applicationSummary
18 Testing a REST API
18.1 Introducing REST applications18.2 Creating a RESTful API to manage one entity18.3 Creating a RESTful API to manage two related entities18.4 Testing the RESTful APISummary
19 Testing database applications
19.1 The database unit testing impedance mismatch19.1.1 Unit tests must exercise code in isolation19.1.2 Unit tests must be easy to write and run19.1.3 Unit tests must be fast to run19.2 Testing a JDBC application19.3 Testing a Spring JDBC application19.4 Testing a Hibernate application19.5 Testing a Spring Hibernate application19.6 Comparing the approaches for testing database applicationsSummary
Part 5. Developing applicationswith JUnit 5
20 Test-driven development with JUnit 5
20.1 TDD main concepts20.2 The flight-management application20.3 Preparing the flight-management application for TDD20.4 Refactoring the flight-management application20.5 Introducing new features using TDD20.5.1 Adding a premium flight20.5.2 Adding a passenger only onceSummary
21 Behavior-driven development with JUnit 5
21.1 Introducing behavior-driven development21.1.1 Introducing a new feature21.1.2 From requirements analysis to acceptance criteria21.1.3 BDD benefits and challenges21.2 Working BDD style with Cucumber and JUnit 521.2.1 Introducing Cucumber21.2.2 Moving a TDD feature to Cucumber21.2.3 Adding a new feature with the help of Cucumber21.3 Working BDD style with JBehave and JUnit 521.3.1 Introducing JBehave21.3.2 Moving a TDD feature to JBehave21.3.3 Adding a new feature with the help of JBehave21.4 Comparing Cucumber and JBehaveSummary
22 Implementing a test pyramid strategy with JUnit 5
22.1 Software testing levels22.2 Unit testing: Basic components working in isolation22.3 Integration testing: Units combined into a group22.4 System testing: Looking at the complete software22.4.1 Testing with a mock external dependency22.4.2 Testing with a partially implemented external dependency22.4.3 Testing with the fully implemented external dependency22.5 Acceptance testing: Compliance with business requirementsSummary
appendix A. Maven
A.1 Convention over configurationA.2 Strong dependency managementA.3 Maven build life cyclesA.4 Plugin-based architectureA.5 The Maven project object model (POM)A.6 Installing Maven
appendix B. Gradle
B.1 Installing GradleB.2 Creating Gradle tasks
appendix C. IDEs
C.1 Installing IntelliJ IDEAC.2 Installing EclipseC.3 Installing NetBeans
appendix D. Jenkins
index

Overview

JUnit is the gold standard for unit testing Java applications. Filled with powerful new features designed to automate software testing, JUnit 5 boosts your productivity and helps avoid debugging nightmares. Whether you're just starting with JUnit or you want to ramp up on the new features, JUnit in Action, Third Edition has you covered. Extensively revised with new code and new chapters, JUnit in Action, Third Edition is an up-to-date guide to smooth software testing. Dozens of hands-on examples illustrate JUnit 5's innovations for dependency injection, nested testing, parameterized tests, and more. Throughout, you’ll learn how to use JUnit 5 to automate your testing, for a process that consumes less resources, and gives you more time for developing.

About the Technology
The JUnit framework is the gold standard for unit testing Java applications—and knowing it is an essential skill for Java developers. The latest version, JUnit 5, is a total overhaul, now supporting modern Java features like Lambdas and Streams.

About the Book
JUnit in Action, Third Edition has been completely rewritten for this release. The book is full of examples that demonstrate JUnit's modern features, including its new architecture; nested, tagged, and dynamic tests; and dependency injection. You'll benefit from author Cătălin Tudose's unique "pyramid" testing strategy, which breaks the testing process into layers and sets you on the path to bug-free code creation.

What's Inside

Migrating from JUnit 4 to 5
Effective test automation
Test-driven development and behavior-driven development
Using mocks for test isolation
Connecting JUnit 5 with Maven or Gradle

About the Reader
For intermediate Java developers.

About the Authors
Cătălin Tudose has a Ph.D. in Computer Science, and over 15 years of experience as a Senior Java Developer and Technical Team Lead. Previous editions were authored by Petar Tahchiev, Felipe Leme, Gary Gregory, and Vincent Massol.

Quotes
Every tool you need to gain a solid, comprehensive understanding of JUnit.
- Becky Huett, Big Shovel Labs

A wealth of information about JUnit 5, and about testing!
- Junilu Lacar, Accenture | SolutionsIQ

The ultimate reference book you need to migrate your unit tests to JUnit 5!
- Jean-François, MorinLaval University

Writing good code takes more than just writing unit tests, and this book shows you the way.
- Burk Hufnagel, Daugherty Business Solutions

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

JUnit and Mockito Unit Testing for Java Developers

Publisher Resources

ISBN: 9781617297045Publisher Support Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills