Explore writing unit tests for Java applications using JUnit, delve into JUnit organization, assertions, quality practices, design relevance, refactoring, and using mock objects for dependencies.

Pragmatic Unit Testing in Java 8 with Junit by The Pragmatic Programmer.png

junit.tar.gz

java

test2

test4 - Our first passing test

test6

test14

test16-branch-persistence

AssertTest-13

test15

test15-profile

test15-ProfilePoolTest

test16-BearingTest

test16-RectangleTest

test16-SparseTest

test16-TransmissionTest

test16-ProfileTest

test20m-ProfileTest

test21-Profile

big1-Profile

big1-MatchSet

big4-MatchSetTest

big4-MatchSet

big6

mock-2-AddressRetrieverTest

mock-4-AddressRetrieverTest

mock-5-AddressRetrieverTest

test1-SearchTest

test3-SearchTest

tdd-1-ProfileTest.java 

tdd-2-ProfileTest.java

tdd-3-ProfileTest.java

tdd-4-Profile.java

tdd-5-ProfileTest.java

tdd-9-ProfileTest.java

tdd-10-ProfileTest.java

tdd-10-AnswerTest.java

tdd-11-ProfileTest.java

tdd-12-ProfileTest.java

tdd-14-ProfileTest.java

tdd-15-ProfileTest.java

thread-2-ProfileMatcherTest

thread-3-ProfileMatcherTest

thread-4-ProfileMatcherTest

test16-branch-persistence-redesign-QCTest

AssertHamcrest-13

test16-branch-persistence-redesign-StatCompilerTest

test16-ProfilePoolTest

test15-ProfilePoolTest-copy 16

test3-SearchTest-ContainsMatches

tdd-11-ProfileTest.java-Supporting Multiple Answers

thread-2-ProfileMatcherTest-Testing Multithreaded Code

test2-Our First passing test

test4 - AAA your way to a test

test2-final-intro-junit

In this course, you will learn how to write a unit test for Java applications using JUnit. You'll start by covering unit-testing foundations, which provide you with a starter set of information about writing basic tests in JUnit. You’ll learn about JUnit organization and assertions, and you’ll pick up a few core quality practices for unit testing such as the Right BICEP and the CORRECT way. 

Towards the end, the bigger design picture focuses on the relevance of design to unit testing and vice versa. You’ll refactor your tests, and you’ll learn how to use mock objects to deal with trouble-some dependencies.

Pragmatic Unit Testing in Java 8 with JUnit

## Expect the exceptions
The test code that comprises `testSearch()` doesn’t expect any exceptions to be thrown. It contains a number of assertions against positive facts. If the test code throws an exception, a `try/catch` block catches it, spews a stack trace onto `System.out`, and explicitly fails the test.
>In other words, exceptions are unexpected by this test method.

If our tests expect an exception to be thrown because we’ve explicitly designed the test to prepare for them, then we can simply let the exceptions fly.
 

>Don’t worry, JUnit traps any exceptions that explode out of our test. JUnit marks a test that throws an exception as an error and displays the stack trace in its output. The explicit `try/catch` block adds no additional value. 

## `try/catch` removal
In the following code, remove the `try/catch` block and modify the signature of `testSearch()` to indicate that it can throw an `IOException`.
* Remove the `try` statement from line 14.
* Replace line 13 with:
```
public void testSearch() throws IOException {
```
* Remove the `catch` block from lines 46-49.
* Now run the test.

# Expect the exceptions
The test code that comprises `testSearch()` doesn’t expect any exceptions to be thrown. It contains a number of assertions against positive facts. If the test code throws an exception, a `try/catch` block catches it, spews a stack trace onto `System.out`, and explicitly fails the test.
>In other words, exceptions are unexpected by this test method.

If our tests expect an exception to be thrown because we’ve explicitly designed the test to prepare for them, then we can simply let the exceptions fly.
 

>Don’t worry, JUnit traps any exceptions that explode out of our test. JUnit marks a test that throws an exception as an error and displays the stack trace in its output. The explicit `try/catch` block adds no additional value. 

# `try/catch` removal
In the following code, remove the `try/catch` block and modify the signature of `testSearch()` to indicate that it can throw an `IOException`.
* Remove the `try` statement from line 14.
* Replace line 13 with:
```
public void testSearch() throws IOException {
```
* Remove the `catch` block from lines 46-49.
* Now run the test.

Learn about exceptions in Search methods and how to prevent them.

Test Smell: Unnecessary Test Code

Before We Begin

JUnit Test Foundations

Digging Deeper into JUnit Assertions

Organizing Your Tests

Mastering Manic Mnemonics!

What to Test: The Right-BICEP

Boundary Conditions: The CORRECT Way

The Bigger Design Picture

Bigger Design Issues

Using Mock Objects

Refactoring Tests

The Bigger Unit-Testing Picture

Testing Some Tough Stuff

Testing on a Project

Wrapping Up

Appendix - Setting up JUnit

Test Smell: Unnecessary Test Code

Expect the exceptions