Test containers for database testing in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of using test containers in database testing?

Test containers provide a lightweight, disposable database environment for tests. They help ensure tests run in isolation with a real database instance, improving reliability and consistency.

intermediate

How do test containers improve integration testing in Spring Boot applications?

They start a real database inside a container before tests run, so the application interacts with a real database. This avoids using mocks and catches real issues with SQL and schema.

beginner

Which Java library is commonly used to manage test containers in Spring Boot tests?

The 'Testcontainers' Java library is widely used. It provides easy APIs to start, stop, and configure containers for databases like PostgreSQL, MySQL, and others.

intermediate

What annotation is typically used in Spring Boot tests to integrate test containers with the test lifecycle?

The @Testcontainers annotation is used on the test class to enable automatic startup and shutdown of containers during tests.

advanced

Why is it important to configure the datasource URL dynamically when using test containers?

Because the container's database URL, port, and credentials are assigned at runtime, the Spring Boot datasource must be configured dynamically to connect to the running container instance.

What does a test container provide for database testing?

A A real, isolated database instance inside a container

B A mock database that simulates queries

C A cloud-hosted database service

D A static database snapshot

Test containers run a real database inside a container, ensuring tests use an actual database environment.

Which annotation enables automatic container lifecycle management in Spring Boot tests?

A @SpringBootTest

B @Container

C @DataJpaTest

D @Testcontainers

@Testcontainers manages starting and stopping containers automatically during tests.

Why must datasource properties be set dynamically when using test containers?

A Because container ports and URLs are assigned at runtime

B Because the database schema changes automatically

C Because test containers use fixed ports

D Because Spring Boot does not support static URLs

Test containers assign ports and URLs dynamically, so datasource config must adapt to connect correctly.

Which library is commonly used to create and manage test containers in Java?

A JUnit

B Testcontainers

C Mockito

D Spring Data

Testcontainers is the Java library designed for managing containers in tests.

What is a key benefit of using test containers over in-memory databases for testing?

A They require no configuration

B They run faster than in-memory databases

C They provide a real database environment matching production

D They do not need Docker installed

Test containers run real databases, so tests catch issues that in-memory databases might miss.

Explain how test containers help improve database integration testing in Spring Boot.

Think about how a real database inside a container differs from mocks or in-memory databases.

Describe the steps to set up a PostgreSQL test container in a Spring Boot test class.

Focus on annotations, container declaration, and datasource setup.

Practice

1. What is the main purpose of using Testcontainers in Spring Boot database testing?

easy

A. To run real database instances in temporary containers for reliable tests

B. To mock database calls without any real database

C. To speed up unit tests by skipping database interactions

D. To deploy databases permanently on production servers

Solution

1. Step 1: Understand Testcontainers role

   Testcontainers run real database instances inside temporary containers during tests.

2. Step 2: Compare with other options

   Mocking or skipping databases is not what Testcontainers do; they provide real environments temporarily.

3. Final Answer:

   To run real database instances in temporary containers for reliable tests -> Option A

4. Quick Check:

   Testcontainers purpose = run real temporary databases [OK]

Hint: Testcontainers run real temporary databases, not mocks [OK]

Common Mistakes:

• Confusing Testcontainers with mocking frameworks
• Thinking Testcontainers deploy permanent databases
• Assuming Testcontainers skip database usage

2. Which of the following is the correct way to start a PostgreSQL Testcontainer in a Spring Boot test class?

easy

A. static PostgreSQLContainer postgres = new PostgreSQLContainer<>("postgres:latest").start();

B. PostgreSQLContainer postgres = new PostgreSQLContainer("postgres:latest").run();

C. static PostgreSQLContainer postgres = new PostgreSQLContainer("postgres:latest").begin();

D. PostgreSQLContainer postgres = new PostgreSQLContainer().start();

Solution

1. Step 1: Check correct instantiation and start method

   The correct way is to create a static container with generic type and call start().

2. Step 2: Validate options

   static PostgreSQLContainer postgres = new PostgreSQLContainer<>("postgres:latest").start(); uses correct syntax with generic type and start(). Others use wrong method names or miss generics.

3. Final Answer:

   static PostgreSQLContainer postgres = new PostgreSQLContainer<>("postgres:latest").start(); -> Option A

4. Quick Check:

   Use start() with generic type for Testcontainers [OK]

Hint: Use start() method and generic type for containers [OK]

Common Mistakes:

• Using .run() or .begin() instead of .start()
• Omitting generic type
• Not declaring container as static when needed

3. Given this Spring Boot test snippet using Testcontainers:

 @Testcontainers
 class MyRepositoryTest {
  @Container
  static PostgreSQLContainer postgres = new PostgreSQLContainer<>("postgres:13").withDatabaseName("testdb").withUsername("user").withPassword("pass");

  @Autowired
  MyRepository repo;

  @Test
  void testCount() {
    long count = repo.count();
    System.out.println(count);
  }
}

What will System.out.println(count); print if the database is empty?

medium

A. null

B. 0

C. Throws NullPointerException

D. 1

Solution

1. Step 1: Understand repo.count() behavior

   The count() method returns the number of records in the repository's table.

2. Step 2: Database is empty so count is zero

   Since the database is fresh and empty, count() returns 0, not null or exception.

3. Final Answer:

   0 -> Option B

4. Quick Check:

   Empty DB count() = 0 [OK]

Hint: Empty database count returns zero, not null or error [OK]

Common Mistakes:

• Expecting null instead of zero
• Assuming count() throws exception on empty DB
• Confusing count() with find methods

4. You wrote this test using Testcontainers but it fails with org.testcontainers.containers.ContainerLaunchException. What is the likely cause?

 @Container
 static PostgreSQLContainer postgres = new PostgreSQLContainer<>("postgres:latest");

 @Test
 void testDb() {
   // test code
 }

medium

A. The PostgreSQL image name is incorrect

B. The container must be started manually with .start() in the test

C. Docker is not running or accessible on the test machine

D. Testcontainers do not support PostgreSQL

Solution

1. Step 1: Understand ContainerLaunchException meaning

   This exception usually means Docker cannot start the container.

2. Step 2: Check common causes

   Most common cause is Docker daemon not running or inaccessible to Testcontainers.

3. Final Answer:

   Docker is not running or accessible on the test machine -> Option C

4. Quick Check:

   ContainerLaunchException = Docker not running [OK]

Hint: Check Docker daemon is running if container launch fails [OK]

Common Mistakes:

• Thinking image name is wrong when it is correct
• Trying to start container manually when @Container does it
• Believing Testcontainers don't support PostgreSQL

5. You want to write a Spring Boot integration test using Testcontainers with a MySQL database. You want the container to start once before all tests and stop after all tests. Which setup is correct?

hard

A. Use @SpringBootTest without any container setup; rely on embedded database

B. Create a new MySQLContainer instance inside each test method and call start() manually

C. Use @BeforeEach to start a MySQLContainer and @AfterEach to stop it

D. Declare a static MySQLContainer with @Container annotation in the test class and use @Testcontainers on the class

Solution

1. Step 1: Understand lifecycle annotations

   Using static container with @Container and @Testcontainers on class starts container once before all tests and stops after all.

2. Step 2: Compare other options

   Creating container per test or starting/stopping each test is inefficient. Embedded DB is different approach.

3. Final Answer:

   Declare a static MySQLContainer with @Container annotation in the test class and use @Testcontainers on the class -> Option D

4. Quick Check:

   Static @Container + @Testcontainers = start once before all tests [OK]

Hint: Use static @Container field with @Testcontainers class annotation [OK]

Common Mistakes:

• Starting container inside each test method
• Using @BeforeEach/@AfterEach for container lifecycle
• Assuming embedded DB replaces Testcontainers