Database Testing
DB Test with Testcontainers
@SpringBootTest
class DatabaseTest {
@Container
static PostgreSQLContainer<?> db = new PostgreSQLContainer<>("postgres:15");
@Autowired private UserRepository userRepository;
@Test
@Transactional
void shouldPersistUser() {
User user = new User("alice", "alice@example.com");
userRepository.save(user);
Optional<User> found = userRepository.findByUsername("alice");
assertThat(found).isPresent();
assertThat(found.get().getEmail()).isEqualTo("alice@example.com");
}
}
Testing Strategies
Testing Pyramid
/ E2E \
/----------\
/ Integration \
/----------------\
/ Unit \
/--------------------
Test Types
- Unit: Individual components
- Integration: Component interactions
- E2E: Full user workflows
- Performance: Load/stress testing
Best Practices
- Write tests first (TDD)
- Aim for 80% coverage
- Test edge cases
- Keep tests fast and isolated
Key Points
- Understanding Database Testing is essential for production systems
- Always consider scalability and maintainability
- Test thoroughly before deploying to production
- Monitor performance and set up alerting
Common Patterns
- Validation: Always validate input at the boundary
- Error Handling: Use structured error responses
- Logging: Log key events for debugging
- Testing: Unit, integration, and load tests
- Documentation: Keep docs updated with code changes
Practice Problems
Design and implement a solution for Database Testing in a backend system. Consider scalability, error handling, and production readiness.
Solution
// Database Testing implementation
// Key aspects: validation, error handling, logging, testing
public class DatabaseTesting {
// Production-ready implementation
}Identify and handle edge cases for Database Testing. What happens under high load, with invalid input, or during failures?
Solution
// Edge case handling:
// 1. Null/empty input -> validation
// 2. High load -> rate limiting, queuing
// 3. Failures -> retries, circuit breaker
// 4. Concurrent access -> locks, idempotencyWrite a testing strategy for Database Testing. Include unit tests, integration tests, and performance tests.
Solution
// Test plan:
// - Unit: 80% coverage target
// - Integration: API contracts
// - Performance: latency, throughput
// - Chaos: failure injectionQuiz
1. @Transactional on test does?
2. Database testing verifies?
3. What is the primary purpose of Database Testing?
4. What is a common mistake when implementing Database Testing?
Flashcards
Question
@Transactional on test?
Click to reveal answer
Answer
Rolls back after test
Question
Database testing verifies?
Click to reveal answer
Answer
Data persistence and queries
Question
What is Database Testing?
Click to reveal answer
Answer
Database Testing is a key concept in backend development.
Question
When to use Database Testing?
Click to reveal answer
Answer
Use Database Testing when building production systems that require reliability, scalability, and maintainability.
Question
Database Testing best practices
Click to reveal answer
Answer
Follow SOLID principles, write clean code, test thoroughly, document decisions, and monitor in production.
Revision Notes
Key Takeaways
- 1.Test data persistence and queries
- 2.@Transactional rolls back after test
- 3.Testcontainers for real DB
- 4.Verify both read and write operations
Interview Tips
- •Test database layer
- •Use Testcontainers
Cheat Sheet
Database Testing
- Verify: persistence and queries
- @Transactional: rollback after test
- Testcontainers: real DB
- Test: read and write ops