Source Projects
The production projects these testing patterns were extracted from -- what each one is, the patterns it contributed, and why a testing approach has to match its deployment target.
Production-Tested Approaches
The patterns in this guide come from real production projects, not theoretical best practices. Each pattern has been used in shipped software and refined through actual bugs and failures.
They are organized into four categories: Tool Patterns for tool- and implementation-specific technique, Project Recipes for patterns shaped by a repo type, CI Operations for running suites across CI, deploys, and releases, and Test Integrity for the ways tests deceive and the discipline that prevents it.
The Projects
This table is the reference entry for the project code-names that recur throughout the guide: what each one is, whether its source is public, and the patterns it contributed. Pages that cite a project carry a one-line gloss at first mention; the fuller description lives here.
| Project | What It Is | Key Testing Patterns |
|---|---|---|
| zudo-text | Tauri desktop text editor; private monorepo. | Vitest unit across workspace packages, Rust cargo test core crate, dual-browser Playwright (Chromium CI / WebKit local), mock backend adapter + console-error monitoring, stateful in-memory fake service, walking-skeleton e2e, MCP contract tests (in-memory SDK client, inventory lock), tiered e2e tags |
Takazudo Modular (zzmod) | Takazudo's own hardware webshop / product-catalog site (zfb + Preact islands). Source is not public; live at the link above. | Vitest unit (jsdom, Testing Library/Preact, MSW), production-build Playwright, tag-based @smoke/@heavy lanes, CI image interception, heavy E2E off-CI via local b4push |
| pgen | GPU pattern generator with a Cloudflare Workers backend; private (zudolab/zudo-pattern-gen). | Deterministic PNG rendering, Miniflare + D1/R2 worker integration, tag-tiered Playwright e2e, GPU visual-regression (SSIM drift, GLSL parity), MCP contract tests (in-memory SDK client, inventory lock) |
| mdx-formatter | Markdown/MDX formatter -- Node CLI + npm library over a Rust (napi) engine. | Contract-testing the Rust engine via Vitest, idempotency invariant, snapshot regression vs committed baselines, CLI integration via execFile |
| zfb | Rust-based frontend build orchestrator / static-site generator; the build tool this site runs on. | Rust workspace cargo test (primary), binding-shape stubs, emitted-code dynamic import, single-source-of-truth guard, happy-dom router quirks, node-free Docker smoke E2E |
| zudo-doc | The doc-site framework this guide is built with, on top of zfb. | 6-level test taxonomy (Vitest unit → static dist reads → Playwright multi-fixture E2E → verify-ui), remark/rehype golden-fixture corpus + mdast tree factories |
| zmanuals | Takazudo Modular's hardware-manual site -- Japanese translations plus a PDF pipeline. | Crawl-all-pages Playwright spec + fast HTTP smoke crawler, plus pdf:verify/pdf:validate data-pipeline consistency checks |
| zudosg | Component library + style-guide monorepo (@zudo-sg/ui, plus demo and doc sites). | Strict link-check + html-validate run together as a Level 3 build-output gate on every PR |
| zdtp | Design-token inspection panel component (@takazudo/zdtp); its test setup is a source for these patterns, but it is not a dependency of this site. | jsdom/browser project split for component tests -- jsdom for the bulk, a browser project for the handful that assert real computed styles |
| takazudo-auth | Session-gated auth app; private. | Environment-tiered login flows with Playwright storageState session reuse across dev, preview, and production |
Common Theme
Across all these projects, one theme emerges: the testing approach must match the deployment target. A web app needs browser-level testing. A CLI tool needs output verification. A Tauri app needs WebKit-specific testing. There is no universal test setup -- only appropriate test setups for specific contexts.