<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>testing on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/testing/</link>
    <description>Recent content in testing on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Abbreviatory Was Tested Against Its Four Promises</title>
      <link>https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/</guid>
      <description>A tool that leaves things out has to be careful about what. So the testing for v0.1.0 is built around four promises, checked over and over: the report never goes over the budget, nothing important gets lost, the same input gives the same bytes, and every reference expands back to exactly the original.
Every number in this post comes from the result files in the code repository, in test/results. They were recorded on October 18, 2026, at commit d0d473f, on a Linux machine with an Intel Xeon processor at 2.</description>
    </item>
    
  </channel>
</rss>
