<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration on gotest</title><link>https://mvrahden.github.io/go-test/tags/migration/</link><description>Recent content in Migration 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/migration/feed.xml" rel="self" type="application/rss+xml"/><item><title>Migrating from `testify/suite` to gotest</title><link>https://mvrahden.github.io/go-test/blog/testify-migration-guide/</link><pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate><guid>https://mvrahden.github.io/go-test/blog/testify-migration-guide/</guid><description>&lt;p&gt;&lt;code&gt;gotest migrate ./...&lt;/code&gt; rewrites most of a testify/suite codebase automatically: struct renames, lifecycle hooks, assertion calls, imports, and the &lt;code&gt;suite.Run&lt;/code&gt; boilerplate. The catch is a handful of patterns it can&amp;rsquo;t convert safely and leaves for manual review. This guide shows what the tool converts, what it leaves for you, and how to migrate package by package without breaking the rest of the codebase.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;testify/suite&lt;/code&gt; is the most widely used Go test suite framework, and for good reason. It gives you struct-based test grouping and lifecycle hooks on top of the standard library. Many teams have hundreds of suites built on it. This guide is for teams that have decided to try gotest alongside or in place of those suites.&lt;/p&gt;</description></item></channel></rss>