The public API: build a driver, then check an implementation against a spec.
The public API: build a driver, then check an implementation against a spec.
Decode Quint's ITF trace files into EDN. Pure: no file or process I/O. What Quint emits, and why parts of it are odd, is in docs/notes/itf-format.md.
Decode Quint's ITF trace files into EDN. Pure: no file or process I/O. What Quint emits, and why parts of it are odd, is in docs/notes/itf-format.md.
Run the Quint CLI and collect the ITF files it writes. The only namespace that shells out.
Run the Quint CLI and collect the ITF files it writes. The only namespace that shells out.
Turn :quint/* metadata into the resolved driver replay consumes. The only
namespace that reflects, and only over the explicit :scan list. Rebuilt on
every call: no global registry, nothing cached between runs.
Turn `:quint/*` metadata into the resolved driver replay consumes. The only namespace that reflects, and only over the explicit `:scan` list. Rebuilt on every call: no global registry, nothing cached between runs.
Run one decoded trace against a resolved driver. No I/O of its own: the only effects are the ones the driver's own functions perform.
Run one decoded trace against a resolved driver. No I/O of its own: the only effects are the ones the driver's own functions perform.
Result data -> string. A consumer of what replay returns, never a second source of truth about it.
Result data -> string. A consumer of what replay returns, never a second source of truth about it.
clojure.test integration: one assertion carrying the whole failure, and the failing trace written where a regression test can replay it.
clojure.test integration: one assertion carrying the whole failure, and the failing trace written where a regression test can replay it.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |