About

Imported from limit5/OmniSight-Productizer (configs/skills/webapp-testing/SKILL.md). Install upstream with npx skills add limit5/OmniSight-Productizer --skill webapp-testing. Copyright stays with the author.

Web Application Testing

Name: webapp-testing
Author: limit5

Test local or remote web applications through Playwright scripts.

Decision Framework

Static HTML? → Read file directly with read_file
Dev server running? → Navigate directly
Need to start server? → Use run_bash("npm run dev &") then test

Workflow

Phase 1: Reconnaissance

Navigate to target URL
Wait for networkidle before inspecting DOM
Capture page state: title, visible elements, console errors

Phase 2: Element Discovery

Use descriptive selectors: text content > role > CSS > ID
Verify elements exist before interacting
Log selector strategy for reproducibility

Phase 3: Interaction & Verification

Click, type, select — always wait for response
Assert expected outcomes (text, URL, element state)
Capture screenshots on failure

Phase 4: Report

Summarize: total tests, passed, failed
Include failure details with selectors and expected vs actual

Key Principles

Always wait for networkidle on dynamic apps before DOM inspection
Use synchronous Playwright (sync_playwright())
Include appropriate waits before actions
Treat test scripts as black-box tools — run with --help first

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/limit5-omnisight-productizer-webapp-testing/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

limit5-omnisight-productizer-webapp-testing.ocm.jsonjson

{
  "ocm": "1",
  "id": "limit5-omnisight-productizer-webapp-testing",
  "kind": "skill",
  "name": "webapp-testing",
  "description": "Test web applications using Playwright automation. Use when tasks mention testing UI, frontend, web app, browser testing, or E2E.",
  "publisher": "limit5",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "playwright",
      "browser",
      "e2e",
      "ui-test",
      "web-test",
      "frontend-test",
      "selenium",
      "cypress",
      "webapp"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Test web applications using Playwright automation. Use when tasks mention testing UI, frontend, web app, browser testing, or E2E."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/limit5/OmniSight-Productizer",
      "path": "configs/skills/webapp-testing/SKILL.md",
      "ref": "524419b30e95dfff4d34c229b1be941a30ed58c7",
      "url": "https://github.com/limit5/OmniSight-Productizer/blob/524419b30e95dfff4d34c229b1be941a30ed58c7/configs/skills/webapp-testing/SKILL.md",
      "key": "limit5/OmniSight-Productizer/configs/skills/webapp-testing/SKILL.md"
    }
  },
  "instructions": "# Web Application Testing\n\nTest local or remote web applications through Playwright scripts.\n\n## Decision Framework\n\n1. **Static HTML?** → Read file directly with `read_file`\n2. **Dev server running?** → Navigate directly\n3. **Need to start server?** → Use `run_bash(\"npm run dev &\")` then test\n\n## Workflow\n\n### Phase 1: Reconnaissance\n- Navigate to target URL\n- Wait for `networkidle` before inspecting DOM\n- Capture page state: title, visible elements, console errors\n\n### Phase 2: Element Discovery\n- Use descriptive selectors: text content > role > CSS > ID\n- Verify elements exist before intera",
  "cost": {
    "context_tokens": 300
  }
}

Fetch it by URL: GET /api/v1/registry/limit5-omnisight-productizer-webapp-testing/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.