Alternatives
Products that do what A C# library to help you enforce a Given-When-Then structured Unit test does
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
- 1
- 2
- 3
- 4CG
2019 · github.com
- 5
- 6ST
We're a couple of software engineers who believe that to build great software you need to write good tests, but we also sympathise when engineers say things like: - "Writing tests was too time consuming on my tight schedule", or - "Unit tests don't catch enough bugs, so they're useless", or - "I've inherited a legacy code base without tests and have no idea where to start" To tackle this we're building Symbolica (https://www.symbolica.dev), a symbolic code executor [1], that lets you run your code for all possible inputs. This means you can do things like: - Assert properties about…
2021
- 7BA
2015 · bud.urbas.si
- 8DT
https://github.com/onqtam/doctest version 1.1 brings the following major changes: - HUGE improvements in compile time of asserts - 70-95% faster than the original one! https://github.com/onqtam/doctest/blob/master/doc/markdown/benchmarks.md#cost-of-an-assertion-macro - wrote a FAQ - and the much requested differences with Catch section - https://github.com/onqtam/doctest/blob/master/doc/markdown/faq.md#how-is-doctest-different-from-catch - MANY minor fixes - it didn't compile when…
2016
- 9GA
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
- 10GA
I started working on this back in 2019, mostly as a design idea. Over the last month I made a big push to make it 100% usable and replace C# in all my personal projects. I now feel it's solid enough to gather feedback from other developers. If you take it for a spin, I hope you enjoy it and send your thoughts!
Jun 2026 · davidobando.github.io
- 11TI
Spent a week in the break building a pre-compiler that brings type safety to runtime. Still pretty early, but generally does what it says. Looking for feedback, code that breaks it (check out the playground), ideas etc.
Jan 2026 · typical.elliots.dev
- 12CS
2015 · volatileread.com
- 13CL
Hi everyone. I've recently released control-components, a C++ library I've been using for most of my embedded projects. It is written in C++17 (with some features from C++20) and uses STL and FreeRTOS under the hood. It contains a lot of building blocks that is commonly used in embedded and IoT projects: finite state machines (FSM), various counters, synchronisation primitives, system loops, sensors, schedulers, HTTP, WiFi, Web GUI, and much more. It also provides GitHub CI workflows for build automation (ccache, various checks). In general, it's a good starting point for an ESP32 project.…
2025 · github.com
- 14AS
Hi HN, I’ve been working on an experimental programming language called XXML. The project started from a frustration I kept running into across systems languages: Languages with strong ownership tend to avoid runtime reflection. Languages with rich reflection usually rely on GC or give up memory guarantees. Compile-time code generation often requires a separate macro language. I wanted to explore whether those tradeoffs are truly necessary. What XXML is trying to do XXML is a statically-typed, native language that: Uses explicit ownership and borrowing (no garbage collector) Supports runtime…
Dec 2025 · xxml-language.com
- 15BU
2012 · github.com
- 16V1
A simple, fast, extensible python library for data validation. New features: * union validator * dynamic dict validator * timedelta validator * enum validator * slug validator * fqdn validator * nested model class GitHub: https://github.com/guyskk/validr Document: https://github.com/guyskk/validr/wiki Usage: https://github.com/guyskk/validr/wiki/Scenario-&-Example
2020
- 17AM
I wrote a free book (CC BY license) on software architecture. It classifies architectural patterns / system designs into groups according to their structure, so that each group features a specific set of goals and properties, as structure and function correlate. That results in a kind of inheritance for patterns, making it easy to learn them and even iterate over all the known architectures to analyze their properties. Any feedback and ideas on how to promote the book is warmly welcome!
2024 · github.com
- 18AS
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
- 19IV
I wanted to evaluate C# source generators to see whether "compile time PetaPoco like" project can be built with it.
2024 · github.com
- 20TD
Hello HN, I'd like to share an idea and a library that implements it. As a fan of "Specification by Example" (as described in Gojko Adzic's renowned book), I faced numerous challenges trying to introduce these ideas at work or in hobby projects. Surprisingly, the most challenging part was writing specifications and examples in Gherkin/Cucumber syntax and producing readable living documentation out of them. I believe that the Given... When... Then... format is not the best for user-facing documentation. Personally, I find novel-like narratives, filled with code examples, design…
2025 · github.com
- 21TT
Hi HN, I’m one of the creators of Erudyte, a platform providing computer science teaching tools. We’re excited to share it with HN! Our website is https://erudyte.io/ and you can try it now without creating an account. As students we didn't like the traditional method of coding on paper. Not being able to test our code and the inconsistencies in grading made the process frustrating for both us and our teachers. Therefore, we developed a platform that simplifies authoring and grading questions. You can generate hundreds of test cases easily using a no-code visual test case…
2023 · erudyte.io
- 22WC
Hi all, I'm Ivan, and together with Alex, we're building a diagram visualization tool for codebases. Alex and I are devs, and we've noticed that recently we've been super productive at writing code (prompting :D). But when it comes to understanding big systems, prompting doesn't work that well — for that, diagrams are best imo. Most tools out there don't scale to big projects (e.g. PyTorch), so we're building CodeBoarding — a recursive visualizer for codebases. It starts from the highest level of abstractions and lets you dive deeper. We use static analysis and LLM agents. The control-flow…
2025 · github.com
- 23GS
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
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →