test-functional

Execute browser-based acceptance criteria tests against authenticated user flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that features meet acceptance criteria by executing browser-based tests against authenticated user flows, reducing manual QA effort and ensuring consistent behavior across apps.

Core Features & Use Cases

  • Automates acceptance-criteria validation across web apps using an MCP browser session.
  • Supports plan.json-driven task identification, files_likely_affected analysis, and automated evidence collection through screenshots and logs.
  • Ideal for regression checks, smoke tests, and end-to-end verification of critical workflows in OpenRegister-like environments.

Quick Start

Run functional tests against the active change using the MCP browser with configured credentials.

Frequently Asked Questions about test-functional

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

FAQPage Schema
How do I automate functional testing for acceptance criteria in a browser?

Automate functional testing by executing acceptance criteria in a browser-based environment using an MCP browser session. The Skill validates authenticated user flows and collects evidence through screenshots and logs to verify features meet requirements.

What is browser-based acceptance criteria validation and how does it work?

Browser-based acceptance criteria validation automates test execution against web apps to verify feature behavior. It uses a plan.json file to drive task identification and selects tests based on files_likely_affected analysis, reducing manual QA effort.

Do I need login credentials to run browser-based functional tests?

Yes, login credentials are required to run browser-based functional tests. The Skill executes tests against authenticated user flows across apps, so valid credentials must be configured in the MCP browser session to access and verify protected workflows.

What's the best way to generate test reports for automated regression checks?

Generate test reports by running the functional tests and logging results automatically. The Skill collects evidence through screenshots and logs during execution, producing reports ideal for regression checks, smoke tests, and end-to-end workflow verification.

Can I use a plan.json file to drive task selection for automated QA testing?

Yes, plan.json-driven task selection is supported for automated QA testing. The Skill reads the plan.json file to identify tasks, analyzes files_likely_affected, and executes the corresponding acceptance criteria validation in the browser environment.

When should I not use browser automation for acceptance testing?

Browser automation for acceptance testing is not suitable when no MCP browser workflow is available or when login credentials cannot be provided. It also requires a plan.json file for task identification, so environments lacking these inputs cannot execute the functional tests.