Slash Command

/test

Runs full pytest test suite (unit, E2E, subprocess) for cli-anything-web CLI at <app-path> with auth verification, updates TEST.md with results, analyzes failures.

Python

Playwright

Bash

testing

From cli-anything-web

Install

Run in your terminal

npx claudepluginhub itamarzand88/cli-anything-web --plugin cli-anything-web

Details

Argument<app-path>

Allowed Tools

Bash(*)ReadWriteEdit

Command Content

Other plugins with /test

/test

Runs pytest tests for CLI harness on local path or GitHub repo, verifies CLI resolution, and updates TEST.md with results if all pass.

cli-anything

27.6k

/test

sc/

Executes unit, integration, or e2e tests with coverage analysis, quality metrics, failure diagnostics, and optional watch mode or auto-fixes.

claude-scholar

3.1k

/test

commands/

Runs TDD workflow for features (red-green-refactor) or bugs (Prove-It pattern): writes failing tests, implements, verifies with full suite. Handles browser issues via DevTools.

agent-skills

2.6k

/test

Generates test strategy overview, unit and integration test code, coverage analysis, execution plan, and maintenance roadmap for a specified component or feature.

essentials

2.4k

/test

Launches Chrome for manual UI testing at given URL, monitors console errors during interaction, generates report with screenshots and logs on completion.

sprint

1.8k

/test

Invokes the testing-coach agent to provide guidance on screen reader, keyboard navigation, and automated testing based on the request.

accessibility-agents

205

Stats

Parent Repo Stars59

Parent Repo Forks11

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Process

This command invokes the testing skill for Phase 3.

Verify auth is working FIRST — this is mandatory before any E2E test:

cli-web-<app> auth login              # playwright-cli (recommended)
cli-web-<app> auth login --cookies-json <file>  # manual fallback
cli-web-<app> auth status

Auth status MUST show live validation succeeded. If it fails:

Ensure playwright-cli is available (npx @playwright/cli@latest --version)
Fix auth before running any tests
Do NOT proceed with "auth not configured" — that is a broken test

Locate test directory: <app>/agent-harness/cli_web/<app>/tests/

Run full test suite:

cd <app>/agent-harness
python -m pytest cli_web/<app>/tests/ -v --tb=short 2>&1

If installed, also run subprocess tests:

CLI_WEB_FORCE_INSTALLED=1 python -m pytest cli_web/<app>/tests/ -v -s -k subprocess 2>&1

After running, verify the subprocess backend was used:

Check output for [_resolve_cli] Using installed command: — this confirms the installed package is being tested, not the source fallback
If this line is absent, the installed CLI was not found in PATH

Parse test output: count passed, failed, skipped, errors

Update TEST.md with results in standard format

If failures exist, analyze and suggest fixes

See the testing skill for detailed testing patterns and the standards skill for quality checks.

# Test Results — cli-web-<app> ## Summary - **Total**: X tests - **Passed**: X - **Failed**: X - **Date**: YYYY-MM-DD ## Unit Tests (test_core.py) <list of test results> ## E2E Tests (test_e2e.py) <list of test results> ## CLI Subprocess Tests <list of test results>

Process

This command invokes the testing skill for Phase 3.

Verify auth is working FIRST — this is mandatory before any E2E test:

cli-web-<app> auth login              # playwright-cli (recommended)
cli-web-<app> auth login --cookies-json <file>  # manual fallback
cli-web-<app> auth status

Auth status MUST show live validation succeeded. If it fails:

Ensure playwright-cli is available (npx @playwright/cli@latest --version)
Fix auth before running any tests
Do NOT proceed with "auth not configured" — that is a broken test

Locate test directory: <app>/agent-harness/cli_web/<app>/tests/

Run full test suite:

cd <app>/agent-harness
python -m pytest cli_web/<app>/tests/ -v --tb=short 2>&1

If installed, also run subprocess tests:

CLI_WEB_FORCE_INSTALLED=1 python -m pytest cli_web/<app>/tests/ -v -s -k subprocess 2>&1

After running, verify the subprocess backend was used:

Check output for [_resolve_cli] Using installed command: — this confirms the installed package is being tested, not the source fallback
If this line is absent, the installed CLI was not found in PATH

Parse test output: count passed, failed, skipped, errors

Update TEST.md with results in standard format

If failures exist, analyze and suggest fixes

See the testing skill for detailed testing patterns and the standards skill for quality checks.

/test

/test

CLI-Anything-Web: Test Runner

Process

TEST.md Format

Failure Handling

CLI-Anything-Web: Test Runner

Process

TEST.md Format

Failure Handling