CLI companion for the SpeQ architectural specification format

promise-happy test DSL

Public contract for speq plugins. Types only — no runtime.

Scaffold a speq plugin: source, tests against the real kernel, and nothing else.

Test a speq plugin against the real kernel, without a project.

YAML loader and the speq 1.x codemod. The default authoring format — and proof that the format is a plugin.

The kernel: loads plugins and gets out of the way.

JUnit XML from the run's event stream. What CI reads.

The terminal surface: run, validate, list. One surface among several, not the framework.

Which tests answer for the work in hand, and whose fault it is when they are red.

Resolves plugins against the npm registry, verifies them, and puts them in the store. No npm CLI involved.

Where values come from: generated test data, the environment, and project variables.

The project in a browser: the suite tree, what each step is, and every run that happened.

Allure results from the run's event stream. What `allure serve` reads.

Browser steps, scoped browser/context/page resources and screenshot artifacts.

HTTP steps and the smoke assertion set that ships in the box.

One self-contained HTML report, opened with a double click and no server.

Composition as a plugin: shared blocks, module actions and fixtures, called from a test with `use`.

The run as one JSON file — the shape a workflow reads with jq.

A simple web-based plaintext calculator harnessing the power of math.js for intuitive free-form calculations. Now with a command-line interface (CLI) for testing purposes.