Alternatives
Products that do what Should – Expressive Assertions for Go does
A few months ago I posted this here. Since then I've added a bunch of new assertions: BeSorted, BeSameTime, BeWithin, BeError/BeErrorIs/BeErrorAs, formatted custom messages, and some renames for clarity. The core idea is still the same — when a test fails, you should immediately know why without having to add debug prints. https://github.com/Kairum-Labs/should
- 1FA
2018 · github.com
- 2
- 3AU
2017 · github.com
- 4AM
2018 · ericgreer.info
- 5TC
2014 · github.com
- 6AC
I always strive to write better, clean and readable code. But I often find unit tests are hard to read, and especially harder to quickly identify what are the important pieces, or even what the test is testing about. So I came up with this lightweight library to help enforce unit tests with a Given-When-Then structure. I hope you find this useful. Any feedback are welcome. https://github.com/cobrakai-lab/Cobrakai.GWTUnit
2021
- 7TO
Learn how to write Rules Engines with CLIPS in your browser! I found the Tour of Go super useful when learning Go, so I went for something similar for evangelizing the awesomeness of CLIPS. A few things I'm proud of with this project: - No front-end frameworks - Compiled WASM binary; your code isn't sent to a back-end server - Code editor/syntax highlighter written from scratch (that I'm sure you'll find bugs in ;)) This is my first attempt at this, and I'd like to expand on it in the future. Let me know what you think! About CLIPS: CLIPS is a programming language useful for building…
2022 · ryjo.codes
- 8GA
Hey folks, wanted to show this off and get feedback. Still early/experimental but there are quite a few concepts I'm excited about here. This project came about while writing a program in Go and loving its approach to concurrency. Being a long-time Rubyist I immediately started to think about what similar concepts might look like in Ruby. I set out with two main design constraints: 1. Lightweight: I didn't want routines to be backed by fibers or threads. Having been involved some in the async project (https://github.com/socketry/async), I had some experience using…
2023 · github.com
- 9GL
Hello HN, I kept losing half my debugging sessions to hunting down why a request failed, or which middleware added that header, or why my JSON response was malformed—too many tools, too many context switches. So I built GoVisual, a tiny Go library that wraps your existing http.Handler and gives you a live dashboard at http://localhost:8080/__viz. - Real-time monitoring: Requests show up instantly via SSE - Deep inspection: Headers, request/response bodies, status, timing - Middleware tracing: Visualize execution order and durations - Zero external deps: Pure Go, drop-in…
2025 · github.com
- 10AN
We’re building an open-source language layer on top of Go, designed specifically for COBOL-style workloads: Native decimal arithmetic (COBOL-accurate) Record structures and copybook compatibility Batch jobs and transactional orchestration as first-class constructs Sequential / indexed file I/O baked into the runtime Compiles through Go for speed, concurrency, and cloud deployability Think of it as Kotlin for COBOL, or “COBOL on Go” familiar to mainframe engineers, powerful for modern developers. Test Results so far: NIST COBOL-85 validation: 77.61% overall (305/393 tests) NC…
Nov 2025 · github.com
- 11AS
There are plenty of good tools for load testing such as JMeter, Minigun, and plenty more - but they all have their own set of options to learn. I built this one to support a simpler workflow where you just paste your curl request (or other cli command) after your `spam` config (literally just `spam -r 2 -- curl www.google.com). It's pretty barebones but I'm 100% going to use it in my day to day - figured I'd share it here if it helped anyone else!
2023 · github.com
- 12VF
I built Valid8r because I got tired of writing the same input validation code for every CLI tool. You know the pattern: parse a string, check if it's valid, print an error if not, ask again. Repeat for every argument. The library uses Maybe monads (Success/Failure instead of exceptions) so you can chain parsers and validators: # Try it: pip install valid8r from valid8r.core import parsers, validators # Parse and validate in one pipeline result = ( parsers.parse_int(user_input) .bind(validators.minimum(1)) .bind(validators.maximum(65535)) ) match result: case Success(port): print(f"Using…
Nov 2025 · github.com
- 13GM
I built GoSMig for my own projects and open-sourced it in case it helps others. It’s a tiny generic library (no external deps except golang.org/x/term) for writing SQL migrations in Go with compile-time checks. It supports transactional and non-transactional migrations, rollback, status, version, and a small CLI handler so you can ship your own migration binary. Why another migrator? - Minimal API, no DSL or file layout to learn - Type-safe via Go generics - Works with database/sql and sqlx out of the box - Should work with any db library (or wrapper) that implements some…
Oct 2025 · github.com
- 14
Guess the print, trace the state, write the code
3d ago · reasoning.cinderwayinteractive.com
- 15IH
A simple Go-based HTTP proxy designed for detailed inspection of requests and responses. It logs traffic to the console with colorization, automatic decompression, and formatting for common content types, while remaining transparent to the client application. Ideal for debugging API interactions, understanding middleware behavior, or simply getting a clear view of HTTP traffic flow with jq-like pretty-printing & colorization of request/response. Automatically redacts parts of Authorization header to avoid token leakage.
2025 · github.com
- 16GA
Hi All, I felt like I was re-inventing the wheel by bolting similar channel architectures onto different Go structs repeatedly so I decided to extract some common types into into one library so that they would be easier to re-use: - oneshot - spsc - spmc - mpsc - mpmc - broadcast - watch The types are inspired by Rust channels so if you're coming from Rust they should feel familiar. So far I'm really enjoying using them but it'd be great to get some external feedback if you have time! https://github.com/amorey/gochan Andres
May 2026 · github.com
- 17FS
2018 · github.com
- 18WA
Hey HN! Half a year ago, I decided to learn the basics of Go and create something useful along the way. Thus, I created Wannabe, a tool that's useful for generating mock HTTP APIs used in integration and all the other kinds of testing. How it works? Wannabe functions as a standalone server. Upon receiving a request, it generates a cURL command from it based on the request matching configuration you set and generates a hash from the prepared cURL command. When in "proxy" or "mixed" mode, Wannabe proxies the request to the external provider and stores the request/response pair as a record…
2024 · github.com
- 19CA
Hi HN, I've been working with LLMs in production for a while both as a solo dev building apps for clients and working at an AI startup. The one thing that always was a pain was to pay OpenAI/Gemini/Anthropic a few dollars a month just for me to say "test" or have a CI runner validate some UI code. So I built this server called ChunkBack, that mocks the popular llm provider's functionality but allows you to type in a deterministic language: `SAY "cheese"` or `TOOLCALL "tool_name" {} "tool response"` I've had to work in some test environments and give good results for experimenting…
Nov 2025 · github.com
- 20TS
Code review is the new bottleneck. "Tests passing" is no longer sufficient to trust the changes, and the (human) cost of evaluating the quality and robustness of new agent-written contributions is skyrocketing. We built Topos to evaluate code quality based on the structural properties of the programs themselves. We map your files to graphs (AST, CFG, CPG, MDG) and calculate metrics that can characterize how simple, composable, or secure your programs are. Agents can use this tool as they write and optimize based on your preferences. And yes, the inspiration for the repository is from…
Jun 2026 · krv.ai
- 21GS
I've worked on several projects writing and implementing specifications (particularly CLN): I've found the specs I write are much better when I quote them in the implementation, so I can see what implementers need to know. Also, when specs change in development, it's almost trivial to find where to update the code. This project is a formalization of my various hacky scripts which ensure the requirements are accurately quoted, and give coverage if any are missing. Not a major Opus, but I hope someone else finds it useful!
Jul 2026 · greatspectations.org
- 22JA
I always thought Google's Just a Line experiment[1] was crazy cool and recently wanted to revisit it. But it hadn't been updated in 7 years So I upgraded all of the dependencies (including the latest version of Swift 5), added SwiftLint and SwiftFormat, and got it (mostly) working again! Hope you have some fun with it- help welcome there's still more to do! [1] https://experiments.withgoogle.com/justaline
2025 · github.com
- 23RA
A friend and I spent a month throwing together a visual rule engine product– wanted to share it with HN today. I've been building automation tooling for a few years at prefix.app and one of the messier things both to support and to teach users was around encoding logic in their automations– most folks get a hold of the basic concepts quite easily, but every (visual) automation tool out there seems to have their own way of actually pulling it all together. For small decisions those work great! But for bigger decisions and more complex logic we don’t think it makes much sense to be embedding…
2022 · rulebricks.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →