Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By desplega-ai
Automate E2E browser testing via CLI: explore pages and navigation goals, record interactions into YAML tests, initialize and run tests with AI self-healing and real-time monitoring, verify features or GitHub PR frontend changes with sequential sessions, screenshots, and Markdown reports.
npx claudepluginhub joshuarweaver/cascade-code-testing-misc --plugin desplega-ai-qa-useExplore a web page using browser automation
Record browser interactions and generate test YAML, or edit existing tests with AI assistance.
Initialize qa-use test directory with example test
Execute E2E tests with real-time progress monitoring.
Verify a pull request's frontend changes through automated browser testing.
Autonomous browsing agent for multi-step web tasks. Use when: (1) User describes a browsing goal (e.g., "find the pricing page"), (2) Complex navigation requires multiple snapshot-action cycles, (3) AI-powered element discovery is needed.
Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.
Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.
Generate test steps from natural language descriptions. Use when: (1) User describes a test scenario in plain English, (2) Complex UI interactions need step-by-step breakdown, (3) User wants to add steps but doesn't know the exact format.
Deep analysis of E2E test failures and results. Use when: (1) A test has failed and needs root cause analysis, (2) User wants to understand why a step failed, (3) Complex multi-step failures need investigation.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
End-to-end test automation with Playwright, Cypress, and Selenium for browser-based testing
Playwright E2E test debugging and interactive browser exploration. Runs tests with action capture (DOM snapshots, network, console, screenshots), diagnoses failures, and provides browser tools for navigating, clicking, and inspecting pages through ARIA snapshots.
End-to-end test execution and recording for web applications
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.
Run E2E browser tests using natural language test definitions powered by Claude Code SDK and agent-browser with video recording
Inter-session communication for Claude Code — session registry, messaging, and coordination
Git worktree management expert for @desplega.ai/wts
Launch file-review GUI for reviewing markdown files with inline comments
Push and pull files from reMarkable tablet via rmapi
Multi-agent coordination with agent-swarm MCP
QA automation CLI for browser testing and E2E test management.
# Install globally
npm install -g @desplega.ai/qa-use
# Or use with npx
npx @desplega.ai/qa-use setup
qa-use setup # Configure your API key
qa-use test init # Initialize test directory with example
Create qa-tests/login.yaml:
name: Login Test
app_config: your-app-config-id
steps:
- action: goto
url: /login
- action: fill
target: email input
value: test@example.com
- action: click
target: login button
- action: to_be_visible
target: dashboard
qa-use test run login # Run single test
qa-use test run --all # Run all tests
| Command | Description |
|---|---|
qa-use test init | Initialize test directory with example |
qa-use test run <name> | Run a test by name |
qa-use test run --all | Run all tests in qa-tests/ |
qa-use test list | List local tests |
qa-use test list --cloud | List cloud tests |
qa-use test validate <name> | Validate test syntax |
qa-use test sync --push | Push local tests to cloud |
qa-use test sync --pull | Pull cloud tests to local |
qa-use test export <id> | Export cloud test to local file |
Run qa-use test --help for all options.
Interactive browser control for test development and debugging:
qa-use browser create # Start browser session
qa-use browser goto https://example.com
qa-use browser snapshot # Get element refs like [ref=e3]
qa-use browser click e3 # Click by element ref
qa-use browser fill e5 "hello" # Fill input field
qa-use browser run # Interactive REPL mode
| Command | Description |
|---|---|
qa-use browser create | Start browser session |
qa-use browser goto <url> | Navigate to URL |
qa-use browser snapshot | Get page element refs |
qa-use browser click <ref> | Click element by ref |
qa-use browser fill <ref> <value> | Fill input field |
qa-use browser screenshot <path> | Save screenshot |
qa-use browser run | Interactive REPL mode |
qa-use browser close | Close browser session |
Run qa-use browser --help for the full list of 29 browser commands.
Dynamic API access powered by live OpenAPI (/api/v1/openapi.json) with local cache fallback.
qa-use api ls # List endpoints from live/cached OpenAPI
qa-use api /api/v1/tests # Call endpoint (method inferred)
qa-use api -X POST /api/v1/tests-actions/run --input body.json
qa-use api ls --refresh # Force refresh OpenAPI cache
qa-use api ls --offline # Use cached OpenAPI only
| Command | Description |
|---|---|
qa-use api ls | List /api/v1/* endpoints from OpenAPI |
qa-use api <path> | Send API request to endpoint |
qa-use api ... --refresh | Force OpenAPI spec refresh |
qa-use api ... --offline | Use cached spec without network |
If live spec fetch fails, qa-use falls back to the last cached spec and prints a stale-cache warning.
| Command | Description |
|---|---|
qa-use setup | Interactive configuration (API key, base URL, etc.) |
qa-use info | Show current configuration |
qa-use install-deps | Install Playwright browsers |
Tests are YAML files with steps that describe user interactions:
name: Checkout Flow
app_config: your-app-id
variables:
email: test@example.com
depends_on: login-test # Optional dependency
steps:
- action: goto
url: /cart
- action: click
target: checkout button
- action: fill
target: email input
value: $email
- action: to_be_visible
target: order confirmation
Supported actions:
| Category | Actions |
|---|---|
| Navigation | goto, go_back, go_forward, reload |
| Input | fill, type, click, hover, press, check, uncheck, select_option |
| Waiting | wait_for_selector, wait_for_timeout, wait_for_load_state |
| Assertions | to_be_visible, to_have_text, to_have_url, to_contain_text, to_be_checked |
| Advanced | ai_action, ai_assertion, extract_structured_data |
See SETUP.md for the complete test definition guide.