Junit Framework / Test Suite

Front 1

fixture

Back 1

• to create a set of objects initialized to certain states
• ensure that there is a well known and fixed environment in which tests are run so that results are repeatable
• Examples of fixtures:
• Loading a database with a specific, known set of data
• Copying a specific known set of filesPreparation of input data
• Setup/creation of fake or mock objects
  

Front 2

annotation to check for an exception

Back 2

@Test(expected= IndexOutOfBoundsException.class)

Front 3

assertArrayEquals() method

Back 3

• will test whether two arrays are equal to each other (same values)
• assertArrayEquals(expectedAry,resultAry);

Front 4

The assertEquals() method

Back 4

• compares two objects for equality, using their equals() method
  
• assertEquals(expected,result);
• has overloaded option to compare primitive values as well

Front 5

assertThat() method

Back 5

• compares an object to an org.hamcrest.Matcher
• assertThat("this string", is("this string"));
• assertThat(123, is(123));.
  

Front 6

Chanining Matcher

Back 6

assertThat(123, not( is(345) ) );

Front 7

Core matchers

Back 7

• any() - Matches anything
• is() - object equality
• describeAs() - adds a descrip

Front 8

Logical matchers (Hamcrest)

Back 8

• allOf() - Takes an array of matchers, and all matchers must match the target object
• anyOf() - Takes an array of matchers, and at least one of the matchers must report that it matches the target object
• not() - Negates the output of the previous matcher.
  

Front 9

2 key goals of jUnit

Back 9

• to make developers write tests for once!
• to make tests that are valid over time

Front 10

tests must be leveraged

Back 10

must be written so new tests can use the original tests

Front 11

Fluent Builder Test Pattern

Back 11

• Person testPerson =
• new PersonBuilder() .SetFirstName("Jason") .SetLastName("Fauchelle") .Build();
• only really used for unit testing and constructors with lots of parameters
  

Front 12

Database Test Pattern

Back 12

• The easiest way to test databases is throught the use of an ORM!!
  
• Hibernate!
• when ORM not an option use database mocking framework
• https://dzone.com/articles/unit-testing-patterns-common-patterns-to-follow-fo
  
• great referencel on combing builder pattern with ORM

Front 13

A fake

Back 13

• is our own implementation that functions just enough for the unit tests to work.
• 
  

Front 14

A mock

Back 14

is an object that we can setup with hard-coded responses to various method calls.

Front 15

order tests run

Back 15

random