Skip to main content

Writing Unit Tests in Groovy with Spock Framework

The Spock Framework is an excellent tool for writing unit tests in Groovy and Java. It's highly expressive, making it easier to write and read tests. In this post, we'll provide a basic example of how to use Spock to write unit tests, along with a simple demonstration of the Given/When/Then structure.

What is Spock?

Spock is a Groovy-based testing framework that allows you to write tests in a natural and readable way. Its syntax is concise and expressive, which makes writing and understanding tests easier. It’s also capable of testing Java applications and can be used to write tests for both functional and unit testing scenarios.


Basic Example: Unit Testing with Spock

Let’s consider a basic example: a service that calculates the total price of items in a shopping cart.


Class to be Tested

class ShoppingCart {


    // Method to calculate the total price of items in the cart

    BigDecimal calculateTotal(List<BigDecimal> items) {

        // Return 0 if the cart is empty

        if (items.isEmpty()) {

            return BigDecimal.ZERO

        }

        

        // Sum up the prices of all items in the cart

        return items.sum()

    }

}

 

Writing the Test Using Spock


import spock.lang.Specification


class ShoppingCartTest extends Specification {


    // This is a test case to check the behavior of the calculateTotal method

    def "should return 0 if the cart is empty"() {

        

        // Given: setup any preconditions for the test

        given: "an empty shopping cart"

        def shoppingCart = new ShoppingCart()

        def items = []  // Empty cart

        

        // When: execute the action that triggers the behavior you're testing

        when: "calculating total for an empty cart"

        def total = shoppingCart.calculateTotal(items)

        

        // Then: assertions or expectations for the result

        then: "the total should be 0"

        total == BigDecimal.ZERO

    }


    // Test case to check that the total is calculated correctly for non-empty cart

    def "should return the correct total for the cart"() {

        

        // Given: setup the shopping cart and items

        given: "a shopping cart with items"

        def shoppingCart = new ShoppingCart()

        def items = [BigDecimal.valueOf(10), BigDecimal.valueOf(20), BigDecimal.valueOf(30)]  // Prices of items

        

        // When: calculating the total price for the cart

        when: "calculating total for the cart"

        def total = shoppingCart.calculateTotal(items)

        

        // Then: assert that the total matches the expected sum of items

        then: "the total should be the sum of all items"

        total == BigDecimal.valueOf(60)  // 10 + 20 + 30 = 60

    }


    // Test case to check for a single item in the cart

    def "should return the price of a single item"() {

        

        // Given: a shopping cart with one item

        given: "a shopping cart with one item"

        def shoppingCart = new ShoppingCart()

        def items = [BigDecimal.valueOf(50)]  // One item worth 50

        

        // When: calculating the total for the cart

        when: "calculating total for the cart with one item"

        def total = shoppingCart.calculateTotal(items)

        

        // Then: assert that the total is the price of the single item

        then: "the total should be the price of the single item"

        total == BigDecimal.valueOf(50)  // The total is just the price of the one item

    }

}


Test Explanation:

  • given:: This block sets up the necessary conditions or context for the test. It's where you create objects, set variables, or mock dependencies.

  • when:: This is where the actual action or method under test is invoked. It describes the operation you're testing.

  • then:: This block defines the expected outcome of the action taken in the When block. You can write assertions here to verify the behavior of the code.


Key Features of Spock

  • Readable Syntax: The Given/When/Then structure makes it easy to express test scenarios in a readable and understandable way.
  • Data-driven Testing: Spock allows you to easily write parameterized tests by using the where: block.
  • Powerful Assertions: You can use a variety of assertions (e.g., ==, !=, throws) to check the state of the system under test.

 




Comments

Popular posts from this blog

Advanced Kafka Resilience: Dead-Letter Queues, Circuit Breakers, and Exactly-Once Delivery

Introduction In distributed systems, failures are inevitable—network partitions, broker crashes, or consumer lag can disrupt data flow. While retries help recover from transient issues, you need stronger guarantees for mission-critical systems. This guide covers three advanced Kafka resilience patterns: Dead-Letter Queues (DLQs) – Handle poison pills and unprocessable messages. Circuit Breakers – Prevent cascading failures when Kafka is unhealthy. Exactly-Once Delivery – Avoid duplicates in financial/transactional systems. Let's dive in! 1. Dead-Letter Queues (DLQs) in Kafka What is a DLQ? A dedicated Kafka topic where "failed" messages are sent after max retries (e.g., malformed payloads, unrecoverable errors). ...

Project Reactor Important Methods Cheat Sheet

🔹 1️⃣ subscribeOn – "Decides WHERE the Pipeline Starts" 📝 Definition: subscribeOn influences the thread where the data source (upstream) (e.g., data generation, API calls) runs . It affects the source and everything downstream (until a publishOn switches it). Flux<Integer> flux = Flux.range(1, 3) .doOnNext(i -> System.out.println("[Generating] " + i + " on " + Thread.currentThread().getName())) .subscribeOn(Schedulers.boundedElastic()) // Change starting thread .map(i -> { System.out.println("[Processing] " + i + " on " + Thread.currentThread().getName()); return i * 10; }); flux.blockLast(); Output: [Generating] 1 on boundedElastic-1 [Processing] 1 on boundedElastic-1 [Generating] 2 on boundedElastic-1 [Processing] 2 on boundedElastic-1 [Generating] 3 on boundedElastic-1 [Processing] 3 on boundedElastic-1 📢 Key Insight: ...

🔄 Kafka Producer Internals: send() Explained with Delivery Semantics and Transactions

Kafka Producer Internal Working Apache Kafka is known for its high-throughput, fault-tolerant message streaming system. At the heart of Kafka's data pipeline is the Producer —responsible for publishing data to Kafka topics. This blog dives deep into the internal workings of the Kafka Producer, especially what happens under the hood when send() is called. We'll also break down different delivery guarantees and transactional semantics with diagrams. 🧠 Table of Contents Kafka Producer Architecture Overview What Happens When send() is Called Delivery Semantics Kafka Transactions & Idempotence Error Handling and Retries Diagram: Kafka Producer Internals Conclusion 🏗️ Kafka Producer Architecture Overview Kafka Producer is composed of the following core components: Serializer : Converts key/value to bytes. Partitioner : Determines which partition a record should go to. Accumulator : Buffers the records in memory be...