Habilidades webapp-testing
📦

webapp-testing

Seguro ⚡ Contém scripts⚙️ Comandos externos📁 Acesso ao sistema de arquivos

Test web applications with Playwright automation

Também disponível em: Azeem-2,7Spade,7Spade,ZhanlinCui,ArtemisAI,davila7,anthropics,DYAI2025,ComposioHQ,Cam10001110101,AutumnsGrove

Local web application testing requires managing servers and automating browser interactions. This skill provides Playwright scripts and server helpers to streamline frontend testing workflows.

Suporta: Claude Codex Code(CC)
🥉 76 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "webapp-testing". Discover all interactive elements on a login page

Resultado esperado:

  • Found 3 input fields: email (type=email), password (type=password), remember (type=checkbox)
  • Found 2 buttons: 'Sign In' (submit), 'Forgot Password?' (link)
  • Screenshot saved to /tmp/login_page.png showing form layout

A utilizar "webapp-testing". Test form submission with server running

Resultado esperado:

  • Server started on port 3000
  • Navigated to http://localhost:3000/login
  • Filled email field with 'test@example.com'
  • Clicked Sign In button
  • Verified navigation to /dashboard
  • Server stopped cleanly

Auditoria de Segurança

Seguro
v1 • 2/25/2026

Static analysis detected 42 patterns but all are false positives. LICENSE.txt URLs are standard Apache 2.0 license references. 'Weak cryptographic algorithm' findings incorrectly flagged license text and argparse code. subprocess usage in with_server.py is legitimate for server management. SKILL.md code blocks are documentation examples, not executable code. Skill is safe for publication.

3
Arquivos analisados
410
Linhas analisadas
4
achados
1
Total de auditorias
Problemas de Baixo Risco (1)
Subprocess execution with shell=True
with_server.py uses subprocess.Popen with shell=True to start development servers. This is expected behavior for a server management helper script that needs to support commands with cd and && operators.

Fatores de risco

⚡ Contém scripts
Nenhuma localização específica registrada
⚙️ Comandos externos (2)
📁 Acesso ao sistema de arquivos (1)
Auditado por: claude

Pontuação de qualidade

45
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
100
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Frontend Developer Testing UI Components

Automate testing of React or Vue components by starting the dev server and verifying UI behavior with Playwright scripts.

Full-Stack Integration Testing

Run backend API server and frontend dev server simultaneously, then execute end-to-end tests against the integrated application.

Visual Regression Detection

Capture screenshots of web application states and compare visually to detect unintended UI changes during development.

Tente Estes Prompts

Basic HTML Element Discovery
Use the webapp-testing skill to inspect a local HTML file and find all button elements. Navigate to the file, wait for the page to load, then list all buttons with their text content.
Dev Server Automation
Start a React dev server on port 3000 using with_server.py, then write a Playwright script that navigates to the app, clicks the login button, and verifies the dashboard appears.
Multi-Server Integration Test
Use with_server.py to start a Python Flask backend on port 5000 and a Vite frontend on port 5173. Write a test that submits a form on the frontend and verifies the data appears in the backend response.
Visual Debugging Session
Navigate to a local webapp, wait for networkidle, capture a full-page screenshot to /tmp/debug.png, and extract the page content HTML. Identify all input fields and their associated labels.

Melhores Práticas

  • Always wait for networkidle state before inspecting dynamic web applications
  • Use the with_server.py helper as a black box - run --help first to understand usage
  • Capture screenshots before DOM inspection for visual debugging context

Evitar

  • Inspecting the DOM before waiting for networkidle on JavaScript-heavy applications
  • Reading script source code into context when --help provides sufficient usage information
  • Using file:// URLs for dynamic applications that require a running server

Perguntas Frequentes

Do I need to install Playwright separately?
Yes, install Playwright with 'pip install playwright' and run 'playwright install' to download browser binaries before using this skill.
How do I test a static HTML file without a server?
Use file:// URLs directly in your Playwright script. Navigate to 'file:///path/to/file.html' without using the with_server.py helper.
Can I test multiple servers at once?
Yes, with_server.py supports multiple --server and --port pairs. Each server starts sequentially and waits for readiness before starting the next.
What if my server takes longer than 30 seconds to start?
Use the --timeout argument to increase the wait time. Example: --timeout 60 for 60 seconds per server.
Why use headless mode for browser testing?
Headless mode runs faster and works in environments without a display. Remove headless=True if you need to visually observe browser behavior.
How do I debug failing tests?
Use page.screenshot() to capture the page state at failure points. Enable browser console logging to see JavaScript errors. Run with headless=False to observe browser behavior visually.

Detalhes do Desenvolvedor

Estrutura de arquivos