Use Postgres database for service tests

• Status: accepted
• Deciders: [Q-tal Enpro Team]

Context and Problem Statement

To ensure high test coverage within the project, functionalities that interact with the database must be tested as well. There are different approaches to testing these functionalities that require a database running.

Considered Options

• Use In-Memory database (like H2)
• Use Production-like Postgres database

Decision Outcome

Chosen option: “Use Production-like Postgres database”, because it ensures a production-like behavior.

Positive Consequences

• Almost same configuration for test and runtime.
• Less database technologies used.
• Guaranteed that production and tests behave the same.

Pros and Cons of the Alternatives

In-Memory Database

• + Potentially faster
• + Does not require external services, like Docker
• + Easy to Implement
• - The In Memory DB may behave differently than The Production DB.

PostgreSQL for testing

• + Testing and Production Environments are almost identical
• + Less Database technologies are used
• + The tests behave in the same way as the deployed application
• - Requires external Services
• - Comparably Slow (2s per test)