skills.rest
everruns
everrunsOFFICIAL
Explore all skills by this author →
Website𝕏@everrunshqGitHub

manual-ui-testing

Execute manual UI test cases with agent-browser against a running stack.

42|1|Updated Dec 14, 2025
Search Tags:#ui-testing#quality-assurance#browser-testing#test-cases#manual-testing#agent-browser
One-click install
npx skills add https://github.com/everruns/everruns --skill manual-ui-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-ui-testing
Source: https://github.com/everruns/everruns/tree/main/.agents/skills/manual-ui-testing
Command: npx skills add https://github.com/everruns/everruns --skill manual-ui-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual UI testing can be slow and error-prone when verifying UI flows across a running stack. This Skill enables guided manual UI testing using agent-browser, streamlining result capture and issue triage.

Core Features & Use Cases

  • Run predefined UI test flows against a live stack using agent-browser
  • Record test results and file issues for any failures to support fast remediation
  • Validate UI behavior after changes, perform ad-hoc verification, and regress UI scenarios

Quick Start

Start a UI test session by launching agent-browser against the running stack and follow prompts to record results and surface issues.

Frequently Asked Questions about manual-ui-testing

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

FAQPage Schema
How do I run manual UI tests against a running stack?▼

To run manual UI tests, you launch agent-browser via npx against your running stack, then follow prompts to navigate predefined test cases, record results, and surface issues for remediation.

What UI flows can I verify using manual UI testing?▼

Manual UI testing verifies predefined flows across admin_login, full_auth, org_creation, mcp_servers, global_chat, global_search, and scheduled_tasks by driving browser navigation and interaction.

Do I need a running stack with authentication to perform browser testing?▼

Yes, browser testing requires a running stack with proper health checks and authentication configured, along with a defined test suite under the test_cases/ui directory to drive interactions.

How does manual UI testing capture and record test results?▼

Manual UI testing captures results by executing test cases through agent-browser, recording pass/fail outcomes for UI behaviors, and filing issues for any failures to support fast remediation.

Can I re-test UI behaviors after applying fixes to verify regression?▼

Yes, you can re-test UI behaviors after applying fixes by re-executing the predefined test flows against the live stack, validating that previous issues are resolved without regressions.

What are the limitations of manual UI testing with agent-browser?▼

Manual UI testing is limited to predefined test cases under test_cases/ui and requires a running stack with proper auth, meaning it cannot test offline environments or undefined ad-hoc flows.

Related Skills

Explore More Content & Communication Skills→
XWIlluDeluXWIlluDelu

playwright

Automate browser interactions from the terminal to navigate pages, fill forms, and capture screenshots.

Community
Intermediate
dthuy62dthuy62

ck:fix

Diagnose and fix software defects with regression tests and verification.

Community
Advanced
cafe3310cafe3310
248

browser-testing

Define browser-based end-to-end testing workflows with Markdown test documentation.

Community
Intermediate
SeongHuniSeongHuni

smoke-check

Execute automated test suites and generate PASS/FAIL reports for software builds.

Community
Advanced