<?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: Furkan ERASLAN</title>
    <description>The latest articles on DEV Community by Furkan ERASLAN (@errtudev).</description>
    <link>https://dev.to/errtudev</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%2F4259205%2F7ec6bdce-1d57-41e3-9c04-6b9efec8e8b7.jpg</url>
      <title>DEV Community: Furkan ERASLAN</title>
      <link>https://dev.to/errtudev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/errtudev"/>
    <language>en</language>
    <item>
      <title>I Built tensgo: A Zero-Dependency Go CLI &amp; TUI for CI/CD API Load Testing</title>
      <dc:creator>Furkan ERASLAN</dc:creator>
      <pubDate>Sun, 22 Nov 2026 19:23:58 +0000</pubDate>
      <link>https://dev.to/errtudev/i-built-tensgo-a-zero-dependency-go-cli-tui-for-cicd-api-load-testing-1b40</link>
      <guid>https://dev.to/errtudev/i-built-tensgo-a-zero-dependency-go-cli-tui-for-cicd-api-load-testing-1b40</guid>
      <description>&lt;p&gt;When adding automated load testing to CI/CD pipelines, I kept running into a trade-off:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Lightweight CLI tools like &lt;code&gt;hey&lt;/code&gt; and &lt;code&gt;wrk&lt;/code&gt; are fast and single-binary, but they lack multi-step stateful flows (e.g., logging in and reusing a Bearer token per virtual user) and strict exit-code latency gates.&lt;/li&gt;
&lt;li&gt;Heavyweights like &lt;code&gt;k6&lt;/code&gt; or &lt;code&gt;JMeter&lt;/code&gt; are powerful, but pulling in a JavaScript runtime or JVM just to fail a build when P95 latency spikes felt excessive.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So I built &lt;strong&gt;tensgo&lt;/strong&gt; (&lt;code&gt;v0.2.0&lt;/code&gt;) under Larch Studios—a zero-dependency, single-binary API load and stress testing CLI with an interactive terminal UI written in Go.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Makes &lt;code&gt;tensgo&lt;/code&gt; Different?
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Strict CI/CD Quality Gates:&lt;/strong&gt; Fail GitHub Actions or GitLab CI builds automatically with non-zero exit codes if P95 latency or error rates cross your SLA thresholds (&lt;code&gt;--max-p95 250ms --max-error-rate 1.0&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OpenAPI / Swagger Auto-Discovery:&lt;/strong&gt; Point &lt;code&gt;--openapi&lt;/code&gt; at your spec URL or local file. &lt;code&gt;tensgo&lt;/code&gt; parses endpoints, generates realistic sample payloads, and automatically handles login token extraction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chaos Profiles &amp;amp; Stateful YAML Flows:&lt;/strong&gt; Run built-in &lt;strong&gt;Spike&lt;/strong&gt;, &lt;strong&gt;Ramp-Up&lt;/strong&gt;, and &lt;strong&gt;Soak&lt;/strong&gt; chaos profiles, or define multi-step YAML scenarios (&lt;code&gt;Login -&amp;gt; Profile -&amp;gt; Checkout&lt;/code&gt;) with per-VU isolated state.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Live Bubble Tea TUI + Single-File HTML Export:&lt;/strong&gt; Monitor live RPS, P50/P95/P99 latencies, and HTTP status distributions in the terminal, and press &lt;code&gt;[h]&lt;/code&gt; at any time to export a self-contained HTML report.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Quick Start
&lt;/h3&gt;

&lt;p&gt;Install via Go:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;go install github.com/Errtu0/tensgo@latest
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Or grab pre-built binaries for Linux, macOS, and Windows from GitHub Releases.&lt;/p&gt;

&lt;p&gt;Run a quick load test with a P95 CI gate:&lt;/p&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;tensgo run &lt;a href="https://api.example.com/v1/health" rel="noopener noreferrer"&gt;https://api.example.com/v1/health&lt;/a&gt; -c 50 -d 30s --max-p95 200ms&lt;br&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;h3&gt;
&lt;br&gt;
  &lt;br&gt;
  &lt;br&gt;
  Links &amp;amp; Interactive Playground&lt;br&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Repository:&lt;/strong&gt; &lt;a href="https://github.com/Errtu0/tensgo" rel="noopener noreferrer"&gt;https://github.com/Errtu0/tensgo&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Documentation &amp;amp; Playground:&lt;/strong&gt; &lt;a href="https://tensgo.dev" rel="noopener noreferrer"&gt;https://tensgo.dev&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;code&gt;tensgo&lt;/code&gt; is MIT-licensed and open to contributions. If you enforce performance budgets in your CI/CD pipelines, I’d love to hear what output formats (JUnit XML, Prometheus metrics, JSON summaries) would make it fit your workflow best!&lt;/p&gt;

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