<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Testcontainers on .NET wat we zoeken</title><link>https://blog.netwatwezoeken.nl/tags/testcontainers/</link><description>Recent content in Testcontainers on .NET wat we zoeken</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 28 Dec 2024 13:45:04 +0200</lastBuildDate><atom:link href="https://blog.netwatwezoeken.nl/tags/testcontainers/index.xml" rel="self" type="application/rss+xml"/><item><title>Simplifying integration testing with .NET and Playwright</title><link>https://blog.netwatwezoeken.nl/posts/simplifying-integration-testing-with-dotnet-and-playwright/</link><pubDate>Sat, 28 Dec 2024 13:45:04 +0200</pubDate><guid>https://blog.netwatwezoeken.nl/posts/simplifying-integration-testing-with-dotnet-and-playwright/</guid><description>&lt;p&gt;In my earlier blog, &lt;a href="https://blog.netwatwezoeken.nl/integration-testing-with-playwright-and-testcontainers/"&gt;Integration Testing with Playwright and Testcontainers&lt;/a&gt;, I shared how to use a WebApplicationFactory with TestContainers and Playwright to set up integration tests. While this approach works well, I encountered a problem: the setup inadvertently spins up two separate hosts, leading to unwanted behaviour.&lt;/p&gt;
&lt;h2 id="nwwzmvctesting"&gt;Nwwz.Mvc.Testing&lt;/h2&gt;
&lt;p&gt;I am introducing NuGet package &lt;a href="https://www.nuget.org/packages/Nwwz.Mvc.Testing"&gt;Nwwz.Mvc.Testing&lt;/a&gt; to solve those issue.It&amp;rsquo;s a simple helper to easily setup a .NET application fro integration testing while allowing a browser to connect to it.&lt;/p&gt;</description></item><item><title>Integration testing with Playwright and Testcontainers in ASP.NET</title><link>https://blog.netwatwezoeken.nl/posts/integration-testing-with-playwright-and-testcontainers/</link><pubDate>Mon, 13 Mar 2023 12:45:04 +0200</pubDate><guid>https://blog.netwatwezoeken.nl/posts/integration-testing-with-playwright-and-testcontainers/</guid><description>&lt;p&gt;Testing plays a crucial role in software development and we strive to test as much as possible using isolated unittests. However, there are times when these unittests fail to capture issues that arise when the entire application is tested. Such issues may include discrepancies between front-end and back-end implementation of APIs, or differences in behavior between real and mocked databases. These problems can be easily identified by running a series of scenarios that test the entire application, including the front-end, back-end, and database. Many developers resort to manual testing to achieve this, but automated testing offers greater repeatability and the ability to integrate checks into the development pipeline.&lt;/p&gt;</description></item></channel></rss>