Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
sickn33 avatar

Webapp Testing

  • 695 installs
  • 44.4k repo stars
  • Updated August 4, 2026
  • sickn33/antigravity-awesome-skills

webapp-testing is a Playwright automation skill that writes Python browser scripts and manages dev-server lifecycles for developers verifying local or deployed web app UI behavior.

About

webapp-testing is a structured browser QA skill built around native Python Playwright scripts. It includes scripts/with_server.py to spin up one or more dev servers— for example npm run dev on port 5173 or paired backend/frontend processes—before running headless Chromium automation. A decision tree routes static HTML (read files, pick selectors) versus dynamic apps (wait for networkidle, screenshot DOM, discover selectors, then act). Example scripts cover element_discovery.py, static_html_automation.py, and console_logging.py under examples/. Developers reach for webapp-testing before shipping or after frontend changes when manual clicks cannot cover every flow. Run bundled helpers with --help first to avoid loading large script sources into context.

  • Agent-oriented web application testing workflow packaged as a reusable skill
  • Fits solo builders validating SaaS, dashboards, and marketing sites without a full QA hire
  • Pairs with agent coding loops to reproduce user flows instead of one-off manual clicks
  • Apache 2.0 licensed skill from the Antigravity Awesome Skills collection
  • Intended for integration with Claude Code, Cursor, and similar coding agents

Webapp Testing by the numbers

  • 695 all-time installs (skills.sh)
  • +19 installs in the week ending Jul 11, 2026 (Skillselion tracking)
  • Ranked #573 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill webapp-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs695
repo stars44.4k
Security audit2 / 3 scanners passed
Last updatedAugust 4, 2026
Repositorysickn33/antigravity-awesome-skills

How do you test local web apps with Playwright?

Run structured browser-based checks on local or deployed web apps before you ship or iterate on UI regressions.

Who is it for?

Frontend and full-stack developers who need Python Playwright smoke tests on localhost before shipping web app changes.

Skip if: API-only services without a browser UI, native mobile app testing, or teams standardized on JavaScript Playwright Test runners only.

When should I use this skill?

User needs Playwright browser tests, UI regression checks, screenshots, or console log capture on a running web app.

What you get

Playwright automation scripts, DOM screenshots, console log captures, and verified UI interaction results.

  • Playwright test scripts
  • screenshots
  • console log captures

By the numbers

  • Bundles with_server.py server lifecycle helper supporting multiple servers
  • Includes three example scripts: element_discovery.py, static_html_automation.py, console_logging.py

Files

SKILL.mdMarkdownGitHub ↗

Web Application Testing

To test local web applications, write native Python Playwright scripts.

Helper Scripts Available:

  • scripts/with_server.py - Manages server lifecycle (supports multiple servers)

Always run scripts with `--help` first to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.

Decision Tree: Choosing Your Approach

User task → Is it static HTML?
    ├─ Yes → Read HTML file directly to identify selectors
    │         ├─ Success → Write Playwright script using selectors
    │         └─ Fails/Incomplete → Treat as dynamic (below)
    │
    └─ No (dynamic webapp) → Is the server already running?
        ├─ No → Run: python scripts/with_server.py --help
        │        Then use the helper + write simplified Playwright script
        │
        └─ Yes → Reconnaissance-then-action:
            1. Navigate and wait for networkidle
            2. Take screenshot or inspect DOM
            3. Identify selectors from rendered state
            4. Execute actions with discovered selectors

Example: Using with_server.py

To start a server, run --help first, then use the helper:

Single server:

python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py

Multiple servers (e.g., backend + frontend):

python scripts/with_server.py \
  --server "cd backend && python server.py" --port 3000 \
  --server "cd frontend && npm run dev" --port 5173 \
  -- python your_automation.py

To create an automation script, include only Playwright logic (servers are managed automatically):

from playwright.sync_api import sync_playwright

with sync_playwright() as p:
    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
    page = browser.new_page()
    page.goto('http://localhost:5173') # Server already running and ready
    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
    # ... your automation logic
    browser.close()

Reconnaissance-Then-Action Pattern

1. Inspect rendered DOM:

   page.screenshot(path='/tmp/inspect.png', full_page=True)
   content = page.content()
   page.locator('button').all()

2. Identify selectors from inspection results

3. Execute actions using discovered selectors

Common Pitfall

Don't inspect the DOM before waiting for networkidle on dynamic apps ✅ Do wait for page.wait_for_load_state('networkidle') before inspection

Best Practices

  • Use bundled scripts as black boxes - To accomplish a task, consider whether one of the scripts available in scripts/ can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use --help to see usage, then invoke directly.
  • Use sync_playwright() for synchronous scripts
  • Always close the browser when done
  • Use descriptive selectors: text=, role=, CSS selectors, or IDs
  • Add appropriate waits: page.wait_for_selector() or page.wait_for_timeout()

Reference Files

  • examples/ - Examples showing common patterns:
  • element_discovery.py - Discovering buttons, links, and inputs on a page
  • static_html_automation.py - Using file:// URLs for local HTML
  • console_logging.py - Capturing console logs during automation

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related skills

FAQ

What helper does webapp-testing bundle for dev servers?

webapp-testing ships scripts/with_server.py to start one or more servers—such as npm run dev on port 5173—then run Playwright automation. Run --help first; the helper supports multi-server backend plus frontend setups.

How does webapp-testing handle dynamic SPAs?

webapp-testing waits for page.wait_for_load_state('networkidle'), screenshots or inspects the rendered DOM, discovers selectors, then executes actions—avoiding premature DOM reads before JavaScript finishes on dynamic apps.

Is Webapp Testing safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Testing & QAtestingfrontend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.