<?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>BDD on .NET wat we zoeken</title><link>https://blog.netwatwezoeken.nl/tags/bdd/</link><description>Recent content in BDD on .NET wat we zoeken</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 11 Apr 2025 13:45:04 +0200</lastBuildDate><atom:link href="https://blog.netwatwezoeken.nl/tags/bdd/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing as a First-Class Citizen of Architecture</title><link>https://blog.netwatwezoeken.nl/posts/testing-as-first-class-architecture-citizen/</link><pubDate>Fri, 11 Apr 2025 13:45:04 +0200</pubDate><guid>https://blog.netwatwezoeken.nl/posts/testing-as-first-class-architecture-citizen/</guid><description>&lt;p&gt;Gáspár Nagy dropped a few interesting ideas and thoughts during the keynote of Living Documentation Event 2025. One of them was about testing and clean architecture, Or hexagonical-, union- or port and adaptors- architecture for that matter. Here is a quick recap of what clean architecture is about.&lt;/p&gt;
&lt;p&gt;&lt;img alt="clean architecture" loading="lazy" src="https://blog.netwatwezoeken.nl/assets/images/2025/04/clean-arch.svg"&gt;&lt;/p&gt;
&lt;p&gt;The core concept is that all business rules and logic are encoded in &lt;code&gt;Application &amp;amp; Domain&lt;/code&gt;. The layers &lt;code&gt;Api / UI&lt;/code&gt;, sometimes called Presentation, and &lt;code&gt;Infra&lt;/code&gt; (Infrastructure) keep the core clean from external influence like user interfaces, database details and such. The goal is that the core stays clean from all kinds of implementation details that do not contribute to actual business logic.&lt;/p&gt;</description></item></channel></rss>