functional-test

Automate browser-based functional testing of dashboard routes and log defects to DASHBOARD_BUGS.md.

Updated Jan 21, 2026

Search Tags:#automation #qa #dashboard #regression #browser #functional-testing #bug-logging

Ready to run

npx skills add https://github.com/Michal-J-Kolodziej/WalkWithMe --skill functional-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: functional-test
Source: https://github.com/Michal-J-Kolodziej/WalkWithMe/tree/main/.agent/skills/functional-test
Command: npx skills add https://github.com/Michal-J-Kolodziej/WalkWithMe --skill functional-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates comprehensive validation of the dashboard UI, ensuring routes load correctly, data displays are accurate, and interactions behave as expected.

Core Features & Use Cases

Automated route verification across dashboard pages (Home, Dogs, Profile, Settings, Friends, Discover, Chat, Meetings, Map, Walks)
Centralized bug reporting workflow that appends findings to DASHBOARD_BUGS.md with a consistent structure
Prerequisite checks and guidance for running the local dev server and authenticating
Regression testing support to quickly verify fixes after code changes

Quick Start

Launch the app locally and run the functional-test workflow to generate the DASHBOARD_BUGS.md bug report.

Frequently Asked Questions about functional-test

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

FAQPage Schema

How do I automate functional testing for dashboard routes and log UI bugs?▼

You can automate dashboard functional testing by running a structured workflow that verifies routes load correctly, checks data displays, and logs defects to a central DASHBOARD_BUGS.md report. It guides step-by-step route testing and appends findings with a consistent structure.

What is functional regression testing for dashboard UI features?▼

Functional regression testing for dashboard UI involves systematically re-validating routes, data displays, and interactions after code changes. This workflow automates that validation, ensuring previous bug fixes remain intact and new feature releases do not break existing UI flows.

Do I need a local dev server running to test dashboard routes?▼

Yes, you need a local dev server running to test dashboard routes. The workflow enforces prerequisite checks and provides guidance for starting the local environment and completing authentication before it can validate UI flows and interactivity.

Can I use browser automation to verify user reports of dashboard display issues?▼

Yes, you can use browser automation to verify user reports of dashboard display issues. The workflow systematically tests UI flows, data display accuracy, and interactivity across all dashboard routes, logging any confirmed defects to a central report.

What's the best way to log bugs found during dashboard UI regression cycles?▼

The best way to log bugs during dashboard UI regression cycles is to append findings to a centralized DASHBOARD_BUGS.md file. This workflow enforces a consistent bug-logging structure, ensuring all discovered defects from route testing are documented systematically.