<?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>Archunit on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/archunit/</link>
    <description>Recent content in Archunit on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo -- 0.147.8</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #213243b1d6e8932079e09227d3f3ed0c806cd0c9</copyright>
    <lastBuildDate>Mon, 03 Jul 2017 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/archunit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Assuring Architectural Rules with ArchUnit</title>
      <link>https://www.hascode.com/assuring-architectural-rules-with-archunit/</link>
      <pubDate>Mon, 03 Jul 2017 00:00:00 +0200</pubDate>
      <guid>https://www.hascode.com/assuring-architectural-rules-with-archunit/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Maintaining architecture rules and constraints for a specific software project or an application is not easy as textual documentation is easily forgotten after a while and hard to verify.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;ArchUnit is a testing library that allows developers and software architects to write down such rules as executable tests that may be run by the development teams and the integration servers.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;In the following article I will demonstrate the basic features of this library by applying rules and constraints to an existing application.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
