test-regression

Execute regression tests across DecideDesk apps and generate Markdown reports.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill test-regression-conductionnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-regression
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/test-regression
Command: npx skills add https://github.com/ConductionNL/decidesk --skill test-regression-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates regression testing across the DecideDesk ecosystem, catching unintended changes before they impact users.

Core Features & Use Cases

  • Deterministic regression runs across core apps (OpenRegister, OpenCatalogi, SoftwareCatalog) and cross-app flows.
  • Flexible scope: run full regression or targeted tests by app or feature.
  • Automated regression reporting with a structured Markdown report and artifact storage.

Quick Start

Run a full regression pass by invoking the test-regression skill with no arguments to cover all affected apps.

Frequently Asked Questions about test-regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate regression tests across DecideDesk apps?

You can automate regression tests across DecideDesk by invoking the test-regression skill, which identifies, executes, and aggregates deterministic test results for core apps like OpenRegister, OpenCatalogi, and SoftwareCatalog.

What is included in an automated regression report for cross-app flows?

An automated regression report includes a structured Markdown file with aggregated test results, covering cross-app integrations, navigation paths, and data integrity checks, while also storing the test artifacts.

Can I run targeted regression tests for specific DecideDesk features instead of a full suite?

Yes, you can run targeted regression tests by specifying optional scopes for individual apps or features, allowing you to focus on specific code changes rather than executing a full regression pass.

How do browser interaction steps work during regression testing?

Browser interaction steps are executed deterministically during regression testing to validate user navigation paths and cross-app integrations, ensuring code changes do not introduce unintended UI or workflow regressions.

When should I run data integrity checks after code changes?

You should run data integrity checks after code changes to verify that core apps like OpenRegister and OpenCatalogi maintain valid cross-app data flows, catching unintended data regressions before they impact users.