Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • MOCKITO COOKBOOK
  • Toc
  • feedback
MOCKITO COOKBOOK

MOCKITO COOKBOOK

By : Grzejszczak
4.3 (4)
close
MOCKITO COOKBOOK

MOCKITO COOKBOOK

4.3 (4)
By: Grzejszczak

Overview of this book

This is a focused guide with lots of practical recipes with presentations of business issues and presentation of the whole test of the system. This book shows the use of Mockito's popular unit testing frameworks such as JUnit, PowerMock, TestNG, and so on. If you are a software developer with no testing experience (especially with Mockito) and you want to start using Mockito in the most efficient way then this book is for you. This book assumes that you have a good knowledge level and understanding of Java-based unit testing frameworks.
Table of Contents (12 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Getting Started with Mockito
chevron up
1. Getting Started with Mockito
Introduction
Adding Mockito to a project's classpath
Getting started with Mockito for JUnit
Getting started with Mockito for TestNG
Mockito best practices – test behavior not implementation
Adding Mockito hints to exception messages (JUnit) (Experimental)
Adding additional Mockito warnings to your tests (JUnit) (Experimental)
2
2. Creating Mocks
2. Creating Mocks
Introduction
Creating mocks in code
Creating mocks with annotations
Creating mocks with a different default answer
Creating mocks with different default answers with annotations
Creating mocks with custom configuration
Creating mocks of final classes with PowerMock
Creating mocks of enums with PowerMock
3
3. Creating Spies and Partial Mocks
3. Creating Spies and Partial Mocks
Introduction
Creating spies in code
Creating spies with custom configuration
Creating spies using annotations
Creating partial mocks
Creating partial mocks of final classes with delegatesTo()
Creating spies of final classes with PowerMock
4
4. Stubbing Behavior of Mocks
4. Stubbing Behavior of Mocks
Introduction
Using argument matchers for stubbing
Stubbing methods that return values
Stubbing methods so that they throw exceptions
Stubbing methods so that they return custom answers
Stubbing methods so that they call real methods
Stubbing void methods
Stubbing void methods so that they throw exceptions
Stubbing void methods so that they return custom answers
Stubbing void methods so that they call real methods
Stubbing final methods with PowerMock
Stubbing static methods with PowerMock
Stubbing object instantiation using PowerMock
5
5. Stubbing Behavior of Spies
5. Stubbing Behavior of Spies
Introduction
Stubbing methods that return values
Stubbing methods so that they throw exceptions
Stubbing methods so that they return custom answers
Stubbing void methods
Stubbing void methods so that they throw exceptions
Stubbing void methods so that they return custom answers
Stubbing final methods with PowerMock
6
6. Verifying Test Doubles
6. Verifying Test Doubles
Introduction
Verifying the method invocation count with times()
Verifying the method invocation count with atLeast()
Verifying the method invocation count with atMost()
Verifying that interactions never happened
Verifying that interactions stopped happening
Verifying the order of interactions
Verifying interactions and ignoring stubbed methods
Verifying the method invocation within the specified time
7
7. Verifying Behavior with Object Matchers
7. Verifying Behavior with Object Matchers
Introduction
Using Hamcrest matchers for assertions
Creating custom Hamcrest matchers
Using Hamcrest matchers for stubbing and verification
Using AssertJ for assertions
Creating custom AssertJ assertions
Capturing and asserting the argument
8
8. Refactoring with Mockito
8. Refactoring with Mockito
Introduction
Removing the problems with instance creation
Refactoring classes that do too much
Refactoring the classes that use the class casts
Refactoring the classes that use static methods
Refactoring the tests that use too many mocks
9
9. Integration Testing with Mockito and DI Frameworks
9. Integration Testing with Mockito and DI Frameworks
Introduction
Injecting test doubles instead of beans using Spring's code configuration
Injecting test doubles instead of beans using Spring's XML configuration
Injecting test doubles instead of beans using Springockito
Injecting test doubles instead of beans with Guice
Injecting test doubles instead of beans with Guice using Jukito
10
10. Mocking Libraries Comparison
10. Mocking Libraries Comparison
Introduction
Mockito versus EasyMock
Mockito versus JMockit
Mockito versus JMock
Mockito versus Spock
11
Index
Index

Adding additional Mockito warnings to your tests (JUnit) (Experimental)

If you would like Mockito to append some additional warning messages to the console, which would help you when your test fails, then this recipe is perfect for you. It's very much related to the previous one so, in order to understand the background, please refer to the introductory part of the previous recipe.

Note

Remember that this feature is experimental and the API, name, or anything related to it may change in time. What's more, the whole feature may get deleted in time!

How to do it...

If you want to have more information presented in your error message, you have to perform the following steps:

  1. Annotate your JUnit test with @RunWith(ConsoleSpammingMockitoJUnitRunner.class).
  2. Define your mocks and perform stubbing inside the test method (unfortunately, you can't use annotations or initialize fields outside test methods).

What happens then is that additional exception messages gets printed on the console after the exception that is thrown:

This stubbing was never used   -> at ....MeanTaxFactorCalculatorTest.should_calculate_mean_tax_factor(MeanTaxFactorCalculatorTest.java:25)

How it works...

When the test is run, ConsoleSpammingMockitoJUnitRunner appends a listener that finds all the stubs through WarningsCollector, including the unused stubs for given mocks. When all of the warnings get collected, the ConsoleMockitoLogger class prints them to the console after the test has failed.

End of Chapter 1
Next Chapter
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete