Automation

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.

From Spreadsheets to BDD: How to Centralize Test Scenarios

Move test cases from Excel or Google Sheets into BDD format and a dedicated tool. Step-by-step migration plus how to automate the move and run tests with AI and the Gwirian skill.

Moving from spreadsheets to BDD test management means your scenarios live in one searchable place, with execution history and collaboration built in. This guide walks you through the migration in five steps, then shows how you can automate both the move and ongoing test runs using an AI assistant and the Gwirian skill.

Why move off spreadsheets?

Spreadsheets work for a handful of test cases. Once you have many scenarios, multiple people, or a need for traceability (who ran what, when, pass or fail), they break down: no full-text search, no execution history, no clear ownership. A dedicated BDD test management tool gives you one place to create scenarios, track runs, and search across projects. The table below sums up the difference.