<?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>Webapplicationfactory on .NET wat we zoeken</title><link>https://blog.netwatwezoeken.nl/tags/webapplicationfactory/</link><description>Recent content in Webapplicationfactory on .NET wat we zoeken</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 08 Feb 2026 12:35:00 +0100</lastBuildDate><atom:link href="https://blog.netwatwezoeken.nl/tags/webapplicationfactory/index.xml" rel="self" type="application/rss+xml"/><item><title>Integration testing with Playwright just got easier</title><link>https://blog.netwatwezoeken.nl/posts/integration-testing-with-playwright-just-got-a-lot-easier/</link><pubDate>Sun, 08 Feb 2026 12:35:00 +0100</pubDate><guid>https://blog.netwatwezoeken.nl/posts/integration-testing-with-playwright-just-got-a-lot-easier/</guid><description>&lt;p&gt;In a &lt;a href="https://blog.netwatwezoeken.nl/simplifying-integration-testing-with-dotnet-and-playwright/"&gt;previous blog post&lt;/a&gt;, I introduced the NuGet package &lt;code&gt;Nwwz.Mvc.Testing&lt;/code&gt;. This package was designed to make it possible to make the &lt;code&gt;WebApplicationFactory&lt;/code&gt; listen on a rela port to that you can use it with Playwright.&lt;/p&gt;
&lt;p&gt;The package implements a different &lt;code&gt;WebApplicationFactory&lt;/code&gt; that spin up a Kestrel instance instead ot the in-memory &lt;code&gt;TestServer&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;With the release of &lt;strong&gt;.NET 10&lt;/strong&gt;, this workaround is no longer necessary. Microsoft has introduced a native way to run &lt;code&gt;WebApplicationFactory&lt;/code&gt; using Kestrel.&lt;/p&gt;</description></item><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></channel></rss>