Cli

How We Run Regression: Organizing Scenarios and Using the Dashboard

Organize BDD scenarios for smoke and full regression, use the Gwirian project dashboard to track health and gaps, and automate runs with an LLM using gwirian-cli and the Gwirian skill.

Regression suites grow fast. You need a clear way to organize what to run, when to run it, and where to see results. This post covers how we organize scenarios for regression, how we use the Gwirian project dashboard to track health and gaps, and how we automate runs with an LLM using gwirian-cli and the Gwirian skill so results show up in that same dashboard.

Part 1: Organizing scenarios for regression

Smoke vs full regression

A smoke set is a small subset of scenarios that cover critical paths: login, key flows, or the features you must not break before a release. Run it often—for example on every PR or before each deploy. A full regression is the entire suite across all features; you might run it nightly or before a major release.

Automate BDD Tests with Gwirian, Playwright, and a LLM

Learn how to set up gwirian-cli, playwright-cli, and workflow skills so an AI assistant can run your BDD scenarios in the browser and record results back to Gwirian.

An AI assistant can read your BDD scenarios from Gwirian, drive a real browser with Playwright, and record pass/fail back to Gwirian—all from your editor. This post walks through the setup and a concrete example.

Three pieces work together: gwirian-cli (terminal access to the Gwirian API), playwright-cli (browser automation from the terminal), and workflow skills (instructions that teach the LLM how to orchestrate both).

Prerequisites

• Node.js >= 18
• A Gwirian account with an API token (from the hosted app or your self-hosted instance)
• An AI assistant or editor that can run terminal commands

Install and configure gwirian-cli

Install the CLI