58 lines
1.3 KiB
Markdown
58 lines
1.3 KiB
Markdown
---
|
|
title: "Web Application Testing Skill"
|
|
contributor: "@f"
|
|
tags: #general, #f
|
|
---
|
|
|
|
---
|
|
name: web-application-testing-skill
|
|
description: A toolkit for interacting with and testing local web applications using Playwright.
|
|
---
|
|
|
|
# Web Application Testing
|
|
|
|
This skill enables comprehensive testing and debugging of local web applications using Playwright automation.
|
|
|
|
## When to Use This Skill
|
|
|
|
Use this skill when you need to:
|
|
- Test frontend functionality in a real browser
|
|
- Verify UI behavior and interactions
|
|
- Debug web application issues
|
|
- Capture screenshots for documentation or debugging
|
|
- Inspect browser console logs
|
|
- Validate form submissions and user flows
|
|
- Check responsive design across viewports
|
|
|
|
## Prerequisites
|
|
|
|
- Node.js installed on the system
|
|
- A locally running web application (or accessible URL)
|
|
- Playwright will be installed automatically if not present
|
|
|
|
## Core Capabilities
|
|
|
|
### 1. Browser Automation
|
|
- Navigate to URLs
|
|
- Click buttons and links
|
|
- Fill form fields
|
|
- Select dropdowns
|
|
- Handle dialogs and alerts
|
|
|
|
### 2. Verification
|
|
- Assert element presence
|
|
- Verify text content
|
|
- Check element visibility
|
|
- Validate URLs
|
|
- Test responsive behavior
|
|
|
|
### 3. Debugging
|
|
- Capture screenshots
|
|
- View console logs
|
|
- Inspect network requests
|
|
- Debug failed tests
|
|
|
|
## Usage Examples
|
|
|
|
### Example 1: Basic Navigation Test
|