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

**Self-validation** in writing unit tests is the most important part of the `FIRST` principle. This principle states that the tests should be written such that the developer won’t need to check them manually, regardless of whether they passed or not.

Below is a dialogue between a recently recruited developer and his manager:

# Automating the tests
Tests aren’t tests unless they assert that things went as expected. We write unit tests to save time, not take more of our time. Manually verifying the results of tests is a time-consuming process that can also introduce more risk. It’s easy to get tired and gloss over important signs when we pour over the voluminous output that pseudo-tests can produce. 

## Importance of automation
Tests should be:
* self-validating
* self-arranging

We have to be sure we don’t make a mistake like designing a test to require **manual arrange** steps before we can run it. Instead, we want to automate any setup our test requires. Remember,  requiring an external setup in order to run a test violates the Isolated part of the FIRST acronym. 

Keep the theme of self-validation in mind as much as possible. Our tests will run as part of a larger suite of unit tests for our system. We might run these tests manually on occasion, but we can save ourselves time and effort by automating the process of when and how the tests are run.

## Automation tools
If we use Eclipse or IntelliJ IDEA, consider incorporating a tool like Infinitest.

> As we make changes to our system, Infinitest identifies and runs any tests that are potentially impacted in the background.

This lesson will cover the importance of self-validation in writing tests.

FIR[S]T: [S]elf-Validating 

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

FIR[S]T: [S]elf-Validating