<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tutorial on gotest</title><link>https://mvrahden.github.io/go-test/tags/tutorial/</link><description>Recent content in Tutorial on gotest</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 06 Sep 2026 10:37:08 +0200</lastBuildDate><atom:link href="https://mvrahden.github.io/go-test/tags/tutorial/feed.xml" rel="self" type="application/rss+xml"/><item><title>Your First Go Test Suite in 10 Minutes: A gotest Tutorial</title><link>https://mvrahden.github.io/go-test/blog/zero-to-suite/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://mvrahden.github.io/go-test/blog/zero-to-suite/</guid><description>&lt;p&gt;Plain &lt;code&gt;go test&lt;/code&gt; carries you a long way — until you need setup that runs before every test, related cases grouped under a shared context, and output you can actually read. At that point most of us start hand-rolling lifecycle helpers and squinting at walls of &lt;code&gt;--- PASS&lt;/code&gt; lines. In the next 10 minutes you&amp;rsquo;ll go from &lt;code&gt;go install&lt;/code&gt; to a structured test suite with lifecycle hooks, BDD-style grouping, and spec output — all running on standard &lt;code&gt;go test&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>