release on Abbreviatory.com https://abbreviatory.com/tags/release/ Recent content in release on Abbreviatory.com Hugo -- gohugo.io en-us Sun, 18 Oct 2026 00:00:00 +0000 Abbreviatory 0.2 Tells You What Changed Since the Last Test Run https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ The first release made one run’s output short. This one compares it with the run before. Abbreviatory v0.2.0 keeps a history per command, and every report now opens with what changed: which failures are new, which got fixed, which are still failing and for how long, and which tests are flaky. Most CI runs aren’t news. The same three tests failed yesterday and they fail today. Reading the full report again, or having a coding agent read it again, mostly confirms what everyone already knows. Abbreviatory Launches as an Open Source Tool That Cuts Test Runs and Logs Down to What Matters https://abbreviatory.com/abbreviatory-launches-as-an-open-source-tool-that-cuts-test-runs-and-logs-down-to-what-matters/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-launches-as-an-open-source-tool-that-cuts-test-runs-and-logs-down-to-what-matters/ Abbreviatory v0.1.0 is out. It’s a small command-line tool that takes a big pile of tool output, a test run, a build log, a JSON response, and turns it into a short report that keeps the failures, errors and warnings. It’s open source under the Apache License 2.0 and comes as a single static binary for Linux, macOS and Windows. The problem is familiar to anyone who has scrolled a CI log. How Abbreviatory Was Tested Against Its Four Promises https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-abbreviatory-was-tested-against-its-four-promises/ 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.