← Browse

@kxiandaoyan/webapp-testing

B

Automated web application testing using browser automation. Use when asked to test a web app, verify UI behavior, check for regressions, or automate browser interactions such as clicking, form filling, navigation, and screenshot capture.

skillclaude

Install

agr install @kxiandaoyan/webapp-testing --target claude

Writes 1 file into .claude/skills/, pinned to git-5c317d82.

  • .claude/skills/webapp-testing/SKILL.md

Document


name: webapp-testing description: Automated web application testing using browser automation. Use when asked to test a web app, verify UI behavior, check for regressions, or automate browser interactions such as clicking, form filling, navigation, and screenshot capture.

Web App Testing

Test web applications through browser automation.

Quick Start

# Launch browser and navigate
exec: agent-browser open https://example.com

# Take screenshot
exec: agent-browser screenshot --output /data/screenshot.png

# Click element
exec: agent-browser click --selector "#submit-btn"

# Fill form
exec: agent-browser fill --selector "input[name=email]" --value "test@example.com"

# Assert text present
exec: agent-browser assert-text --text "Success"

Testing Workflow

  1. Setup: Navigate to the target URL
  2. Interact: Perform user actions (click, fill, navigate)
  3. Assert: Verify expected outcomes (text, elements, URL)
  4. Screenshot: Capture evidence of results
  5. Report: Summarize pass/fail with screenshots

Common Patterns

Login flow

open URL → fill username → fill password → click submit → assert dashboard visible

Form submission

fill fields → click submit → assert success message or error handling

Navigation

click nav link → assert URL changed → assert page content

Guidelines

  • Always take a screenshot after key interactions as evidence
  • Test both happy paths and error cases
  • Use specific CSS selectors over generic ones
  • Report failures with the exact selector and expected vs actual state

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicensecopyleft/unknown — index-and-link only

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-5c317d828a542026-07-31