<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI on gotest</title><link>https://mvrahden.github.io/go-test/tags/ci/</link><description>Recent content in CI 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/ci/feed.xml" rel="self" type="application/rss+xml"/><item><title>Go Tests in GitHub Actions: The gotest CI Setup Guide</title><link>https://mvrahden.github.io/go-test/blog/gotest-in-ci/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://mvrahden.github.io/go-test/blog/gotest-in-ci/</guid><description>&lt;p&gt;Running gotest locally is straightforward. Making it work well in CI — with clear failure output, PR annotations, coverage enforcement, and safety guards — takes a bit of setup. This post covers the official GitHub Action, the &lt;code&gt;summary&lt;/code&gt; command, coverage thresholds, and the CI mode that catches debugging artifacts before they reach your main branch.&lt;/p&gt;
&lt;p&gt;If you haven&amp;rsquo;t written a gotest suite yet, start with &lt;a href="https://mvrahden.github.io/go-test/blog/zero-to-suite/"&gt;Your First Go Test Suite in 10 Minutes&lt;/a&gt; and come back — everything here builds on that workflow.&lt;/p&gt;</description></item></channel></rss>