<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: budment</title>
    <description>The latest articles on DEV Community by budment (@budment).</description>
    <link>https://dev.to/budment</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4118698%2F0b67dd69-106b-4949-bbe3-55f4d969f0ae.png</url>
      <title>DEV Community: budment</title>
      <link>https://dev.to/budment</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/budment"/>
    <language>en</language>
    <item>
      <title>What if API testing worked like Terraform? (An experiment in Go)</title>
      <dc:creator>budment</dc:creator>
      <pubDate>Mon, 14 Sep 2026 16:06:55 +0000</pubDate>
      <link>https://dev.to/budment/what-if-api-testing-worked-like-terraform-an-experiment-in-go-5ep5</link>
      <guid>https://dev.to/budment/what-if-api-testing-worked-like-terraform-an-experiment-in-go-5ep5</guid>
      <description>&lt;p&gt;I’ve been learning Go recently and wanted to try a Terraform-like workflow for API testing: write scenarios as code, compile them into a static plan, then execute that plan.&lt;/p&gt;

&lt;p&gt;So I built a small project. You define workflows in TypeScript, run &lt;code&gt;budment plan&lt;/code&gt; to inspect the execution hierarchy and hooks without making network requests, then execute the compiled AST natively in Go.&lt;/p&gt;

&lt;p&gt;“Scenario-as-code” isn’t new, but I’m interested in whether a plan-first approach can make test suites easier to inspect, audit, and maintain.&lt;/p&gt;

&lt;p&gt;I’m still getting comfortable with Go, so I’d appreciate any feedback on the architecture, concurrency, or anything that looks questionable.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/budment/budment" rel="noopener noreferrer"&gt;https://github.com/budment/budment&lt;/a&gt;&lt;br&gt;
Docs: &lt;a href="https://budment.com" rel="noopener noreferrer"&gt;https://budment.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>go</category>
      <category>testing</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
