<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Grails on ilikeorangutans</title><link>https://kuelzer.ca/tags/grails/</link><description>Recent content in Grails on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 12 Apr 2026 14:49:25 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/grails/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Golang and Graphviz to Visualize Complex Grails Applications</title><link>https://kuelzer.ca/posts/2014/05/03/using-golang-and-graphviz-to-visualize-complex-grails-applications/</link><pubDate>Sat, 03 May 2014 13:59:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2014/05/03/using-golang-and-graphviz-to-visualize-complex-grails-applications/</guid><description>&lt;p&gt;At work we are maintaining several large and complex grails applications. In order to improve stability and reliability, we&amp;rsquo;re trying to increase test coverage. But as with all projects, time and resources are limited. In order to get a better understanding of what parts of the application are more important than others, I decided to use &lt;a href="http://www.graphviz.org/"&gt;Graphviz&lt;/a&gt; to help me get a better overview of our applications.&lt;/p&gt;
&lt;h3 id="meet-graphviz"&gt;Meet Graphviz&lt;/h3&gt;
&lt;p&gt;I discovered my love for the &lt;a href="http://www.graphviz.org/content/dot-language"&gt;dot language&lt;/a&gt; when I used it years ago to analyze template hierarchies in a proprietary CMS system I worked on. In a nutshell, it lets you specify a graph with nodes and edges plus some extra attributes for labels, shapes etc. It&amp;rsquo;s really a concise little language:&lt;/p&gt;</description></item><item><title>Grails 2 Testing Guide</title><link>https://kuelzer.ca/posts/2014/02/06/grails-2-testing-guide/</link><pubDate>Thu, 06 Feb 2014 13:59:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2014/02/06/grails-2-testing-guide/</guid><description>&lt;p&gt;&lt;strong&gt;Note: I&amp;rsquo;m still working on this post, but I already use it as a reference so there&amp;rsquo;ll be more content over time.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been quite busy at work with updating a Grails 1.3 application to 2.3.4. While writing a test harness it became apparent that lots of things have changed since I&amp;rsquo;ve last worked with Grails. Many changes are for the better, especially the integration of Spock framework. However, there were some issues that took me a while to figure out. The Grails docs on &lt;a href="http://grails.org/doc/latest/guide/testing.html"&gt;testing&lt;/a&gt; are comprehensive, but long. Here&amp;rsquo;s my cheat sheet.&lt;/p&gt;</description></item></channel></rss>