wunderspec / devconf

DevConf follow-up

Find distributed systems bugs before production… with executable specs

Thanks for attending our workshop.

Start with a 5-bullet assessment, or read on if you are considering a focused pilot project.

Executable specifications help when the hard part is not generating more inputs, but defining and exploring correct behavior. They make expected behavior executable early, so teams can find design flaws—one unlucky ordering, one stale observation, one retry at the wrong time—before they become production incidents.

Where to go from here

[01]

5-bullet assessment

If you think executable specifications may help a system you work on, send us five bullets.

We will reply with a short assessment: where your system falls on the landscape, which approaches are most likely to help, which are poor fits, and whether executable specs and model-based testing (MBT) are worth considering.

Send:

  1. What system or subsystem are you thinking about?
  2. What important behavior must never break?
  3. What makes those behaviors hard to test?
    Concurrency, retries, time, partial failure, ordering, scale, state, or external services?
  4. What are you worried your current tests miss or find too late?
  5. Who would care if this failed in production?

You can forward the assessment internally to decide whether a small pilot is worth discussing.

Send your five bullets to demo@wunderspec.com

[02]

Pilot projects after DevConf

After DevConf, we have room for 1-2 focused pilot projects.

Best fit: control planes, schedulers, databases, protocols, reconciliation loops, stateful cloud infrastructure, and distributed systems with retries, timeouts, partial failure, or important invariants.

A good pilot is time-bounded and focused on a specific subsystem. The goal is to find out whether executable models can expose meaningful behavioral gaps in your system and produce useful tests or oracles for the team.

Download the pilot project one-pager

Interested in one of the pilot slots? Email demo@wunderspec.com

[03]

Slides and follow-up guides

  1. Workshop slides

    Download the slides from the DevConf workshop.

    Download workshop slides

  2. Workshop GitHub repo

    Code and examples for the DevConf workshop.

    github.com/thpani/testing-distsys-devconf26

  3. Distributed systems testing landscape

    A short guide to where different testing approaches fit: unit tests, property-based testing, E2E tests, chaos testing, deterministic simulation, and executable models.

    Download testing landscape guide

  4. Choosing a spec language

    A technical guide for teams comparing executable models, TLA+, Quint, Lean, Python-based specs, and related tooling.

    Download spec language guide