BROADCASTS.com

#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.

\xa0

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.

\xa0

In this episode we speak with Sergei Egorov from AtomicJar about the history of Testcontainers and how to implement it into your development processes.

\xa0

Sergei\u2019s contact information:

Twitter: https://twitter.com/bsideup

LinkedIn: https://www.linkedin.com/in/bsideup/

\xa0

YouTube channel:

https://youtube.com/devopsparadox/

\xa0

Books and Courses:

Catalog, Patterns, And Blueprints

https://www.devopstoolkitseries.com/posts/catalog/

\xa0

Review the podcast on Apple Podcasts:

https://www.devopsparadox.com/review-podcast/

\xa0

Slack:

https://www.devopsparadox.com/slack/

\xa0

Connect with us at:

https://www.devopsparadox.com/contact/