Daniel Raniz Raneland
Three-and-a-half Ways of Testing your Repositories
#1about 5 minutes
Introduction to repositories in domain-driven design
Repositories act as an abstraction layer between the domain and infrastructure, separating business logic from data persistence concerns.
#2about 9 minutes
Mocking the client API for fast and isolated tests
The first method involves replacing the backend client, like an S3 client, with a mock object to verify that the correct methods are called.
#3about 8 minutes
Mocking the backend service for client-agnostic tests
Instead of mocking the client library, you can intercept and mock the HTTP requests it makes to the backend service, like DynamoDB.
#4about 3 minutes
The brittleness of mocking SQL statements directly
Asserting on exact SQL strings is a fragile approach because minor refactoring, like adding parameters, will break the tests.
#5about 6 minutes
Testing against a real, persistent database service
Using a shared development or staging database provides a realistic environment but introduces significant challenges with state management and cleanup.
#6about 7 minutes
Using temporary services with Testcontainers for reliable tests
Testcontainers allows you to programmatically spin up ephemeral database instances in Docker, enabling realistic and isolated roundtrip testing.
#7about 4 minutes
Comparing the pros and cons of each testing method
A final summary compares the speed, complexity, and implementation coupling of client mocking, service mocking, and testing against real or temporary services.
#8about 15 minutes
Q&A on testing strategies and CI/CD integration
The Q&A covers choosing mocking frameworks, balancing unit and integration tests, handling data migrations, and integrating repository tests into CI/CD pipelines.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
16:43 MIN
Practical strategies for testing legacy applications
Testing .NET applications a Tool box for every developer
08:37 MIN
Understanding the Test-Driven Development workflow
Yes, You Need to Unit Test your JavaScript. Here's How.
26:48 MIN
Key lessons learned from this testing approach
Using code generation for test automation – the fancy way
35:31 MIN
Q&A: Mocking external service dependencies in tests
Using code generation for test automation – the fancy way
04:55 MIN
Introducing the core principles of test-driven development
Breaking the Bug Cycle: TDD for the Win
10:04 MIN
Implementing unit, integration, and data quality tests
Modern Data Architectures need Software Engineering
12:36 MIN
How TDD builds a strong foundation of unit tests
Treat yourself - A tale about dog training and test-driven development
39:18 MIN
Adopting TDD as a design tool, not just a testing method
Treat yourself - A tale about dog training and test-driven development
Featured Partners
Related Videos
56:49Write tests you love, not hate
Jens Happe
25:36Test-Driven Development: It's easier than you think!
Eric Deandrea
58:26TDD for Vue.js Developers
Markus Oberlehner
25:18Building Reliable Serverless Applications with AWS CDK and Testing
Raphael Manke
43:07How not to test
Golo Roden
30:55Why you must use TDD now!
Alex Banul
26:02Contract Testing - How do you tame an external API that constantly breaks your tests
Vincent Hennig & Anupam Krishnamurthy
47:22Continuous testing - run automated tests for every change!
Christian Kühn
From learning to earning
Jobs that call for the skills explored in this talk.
DevOps Engineer – Kubernetes & Cloud (m/w/d)
epostbox epb GmbH
Berlin, Germany
Intermediate
Senior
DevOps
Kubernetes
Cloud (AWS/Google/Azure)
Testmanager
Dataport
Parttime Software Tester
Codevid
Working Student - Development of a Test Setup for automated testing of ADAS Functions using Carla and ROS2
FDTech GmbH
C++
Bash
Unix
Python
Docker