Test execution and cleanup<\/h3>\n
After the container is ready and the client is configured, the code seeds test data through\u00a0 Finally, the\u00a0 With the right tools, the complexity of integration testing can be tamed. Testcontainers bridges this gap by making it easier to test against containerised services while maintaining isolation, repeatability, and eliminating the need for shared infrastructure.<\/p>\n While this example focused on Azure Cosmos DB, the patterns apply broadly to any service that offers Docker containers, including PostgreSQL, Kafka, and more. Start with a single service and expand your test coverage gradually.<\/p>\n Although the Azure Cosmos DB emulator is a powerful tool for local development and testing, but it does not support every feature available in the full Azure Cosmos DB service. You can can read on the Differences between the emulator and cloud service<\/a>, or consult the\u00a0documentation<\/a>\u00a0to understand the subset of features that are supported in the emulator.<\/p>\n The full example code is available in the\u00a0GitHub repository<\/a>, and the\u00a0testcontainers-go documentation<\/a>\u00a0provides comprehensive guidance for exploring more.<\/p>\n Happy building!<\/p>\n Azure Cosmos DB is a fully managed and serverless distributed database for modern app development, with SLA-backed speed and availability, automatic and instant scalability, and support for open-source PostgreSQL, MongoDB, and Apache Cassandra. To stay in the loop on Azure Cosmos DB updates, follow us on\u00a0X<\/a>,\u00a0YouTube<\/a>, and\u00a0LinkedIn<\/a>.<\/p>\n To easily build your first database, watch our\u00a0Get Started videos<\/a>\u00a0on YouTube and explore ways to\u00a0dev\/test free.<\/a><\/p>\n<\/div>\n<\/article>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Integration testing has always presented a fundamental challenge: how do you test your application against real dependencies without the complexity of managing external services? Traditional approaches often involve either mocking dependencies (which can miss integration issues) or maintaining separate test environments (which can be expensive and difficult to manage consistently). Hello Testcontainers! Testcontainers\u00a0solves this problem […]<\/p>\n","protected":false},"author":181737,"featured_media":10755,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,1935],"tags":[499,1933,1783],"class_list":["post-10754","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-core-sql-api","category-go-sdk","tag-azure-cosmos-db","tag-devops","tag-docker"],"acf":[],"blog_post_summary":" Integration testing has always presented a fundamental challenge: how do you test your application against real dependencies without the complexity of managing external services? Traditional approaches often involve either mocking dependencies (which can miss integration issues) or maintaining separate test environments (which can be expensive and difficult to manage consistently). Hello Testcontainers! Testcontainers\u00a0solves this problem […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts\/10754","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/users\/181737"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/comments?post=10754"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/posts\/10754\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/media\/10755"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/media?parent=10754"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/categories?post=10754"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-json\/wp\/v2\/tags?post=10754"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}seedTestData()<\/code>\u00a0to provide known items for the tests to work with.\u00a0m.Run()<\/code>\u00a0then executes all the actual test functions, returning an exit code that indicates whether the tests passed or failed.<\/p>\nemulator.Terminate(ctx)<\/code>\u00a0call in the cleanup section ensures that\u00a0testcontainers<\/code>\u00a0properly stops and removes the Docker container, regardless of the test results. This cleanup is essential for preventing resource leaks and ensuring that subsequent test runs start with a clean slate.<\/p>\n<\/a>Conclusion<\/h2>\n
About Azure Cosmos DB<\/h2>\n