Testing

Use quick intentions to manage imports

Often we want to test the same set of criteria with different sets of data. Data pipes is one mechanism to do this.

Data tables offer the same functionality as data pipes, but this syntax can sometimes be more readable for more complex sets of data.

Expecting Exceptions (part of tutorial)

Tests don't check just the happy paths, sometimes we want to say we're expecting a specific Exception.

Generate Test Methods (tip)

Generate a test method in your Test class

Generate a Test Class (tip)

Generate a new test class from your Java class

Given, When and Then (part of tutorial)

See how Spock tests are usually structured.

Marco Codes - Hibernate & JPA Tutorial (tutorial)

Crash course in Hibernate and JPA

Marco Codes - JUnit 5 (tutorial)

JUnit 5 Nice n Easy

Merge/Unmerge If Statements (tip)

Experiment with your code without changing the semantics

Migrating JUnit 4 to JUnit 5 (tutorial)

Migrating your JUnit 4 test suite to JUnit 5

Mocks (part of tutorial)

Mocks are a useful testing tool. We can provide "empty" objects, so we don't have to initialise the whole application to test a section, and we can use mocks to check our code is making the calls we expect.

Navigate to Test (tip)

Go to your matching test class

Setting up the Dependencies (part of tutorial)

Add Spock framework dependencies to the project

Setup and Teardown (part of tutorial)

See how to set up, or clean up, test classes and methods in Spock.

Stubs (part of tutorial)

Stub objects allow us to state from a test what values get injected into our application code. They can provide simple interfaces, so we don't have to initialise the whole application to test a section.