Small, standalone sample projects that run Markdown oaths as tests with Varar — one project per language/test-framework combination. Each is a complete project you can copy as the starting point for your own.

The .md files in each project's varar/ directory are the oaths — plain Markdown prose that runs as tests. They are first-class: readable by anyone, owned by the whole team, and checked against the code on every test run.

Project	Stack	Run with	CI
typescript-vitest	TypeScript + vitest	pnpm test
kotlin-junit	Kotlin + JUnit + Gradle	./gradlew test
kotlin-kotest	Kotlin + Kotest + Gradle	./gradlew test
java-junit-maven	Java + JUnit + Maven	mvn test
java-junit-gradle	Java + JUnit + Gradle	./gradlew test
python-pytest	Python + pytest	uv run pytest
python-unittest	Python + unittest	uv run python -m unittest
ruby-rspec	Ruby + RSpec	bundle exec rspec
ruby-minitest	Ruby + Minitest	bundle exec rake test
rust-cargotest	Rust + cargo test	cargo test
csharp-vstest	C# + dotnet test	dotnet test
go-gotest	Go + go test	go test

typescript-vitest implements the full example set; the other projects implement a feature-covering subset — hello-varar (basic steps), deep-thought (a one-sensor oath), tables-and-docstrings (whole tables + doc strings), yahtzee and roman-numerals (header-bound table rows), and library (custom parameter types that pair parse with format, so a mismatch renders in the document's own notation — money, dates, and an emphasised title where the markup is the parameter).

The source of truth is the varar-dev/varar monorepo's examples/ directory, where the projects run against the local build on every push (in there, the subset projects' varar/*.md files are symlinks to the typescript-vitest originals). On every release they are synced — symlinks resolved, versions pinned to the release — to varar-dev/varar-examples. Send changes to varar-dev/varar.