#187: When writing tests that need to talk to a data source, you’re usually faced with a couple of options. The first one is that you setup a database server on your machine. The problem with that is what happens when other developers need to run those same tests? They have to setup the database too.
The other option is you can mock your database connections. However, it’s hard to keep your mock up to date with the latest features of the database you are using. What if there was another option you could use? Enter Testcontainers.
In this episode we speak with Sergei Egorov from AtomicJar about the history of Testcontainers and how to implement it into your development processes.
Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.
His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).
He often speaks at community gatherings and conferences (latest can be found here).
His random thoughts and tutorials can be found in his blog TechnologyConversations.com.
If you like our podcast, please consider rating and reviewing our show! Click here, scroll to the bottom, tap to rate with five stars, and select “Write a Review.” Then be sure to let us know what you liked most about the episode!
Also, if you haven’t done so already, subscribe to the podcast. We're adding a bunch of bonus episodes to the feed and, if you’re not subscribed, there’s a good chance you’ll miss out. Subscribe now!