<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tooling on gotest</title><link>https://mvrahden.github.io/go-test/tags/tooling/</link><description>Recent content in Tooling 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/tooling/feed.xml" rel="self" type="application/rss+xml"/><item><title>gotest VS Code Extension: Suite-Aware Go Testing</title><link>https://mvrahden.github.io/go-test/blog/your-editor-knows-your-tests/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://mvrahden.github.io/go-test/blog/your-editor-knows-your-tests/</guid><description>&lt;p&gt;You write gotest suites, open VS Code&amp;rsquo;s Testing sidebar — and it&amp;rsquo;s empty. No test tree, no CodeLens Run buttons above your suite methods, nothing to debug. Standard Go tooling has nothing to show you, because as far as gopls and the Go Test Explorer are concerned, your suites aren&amp;rsquo;t tests at all.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://marketplace.visualstudio.com/items?itemName=mvrahden.gotest"&gt;gotest VS Code extension&lt;/a&gt; exists to close this gap. Because it&amp;rsquo;s purpose-built for suite-based testing rather than a generic test runner, it can surface things standard tooling can&amp;rsquo;t: the suite hierarchy, the behavioral spec view, and coverage that survives across runs.&lt;/p&gt;</description></item></channel></rss>