← Back to Skills Marketplace
zhanghengyi1986-afk

Web Tester

by zhanghengyi1986-afk · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
92
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install web-tester
Description
Web UI testing and browser automation using Playwright or Selenium. Navigate pages, interact with elements, take screenshots, validate UI state, generate E2E...
README (SKILL.md)

Web Tester

Browser-based UI testing and E2E automation.

When to Use

USE this skill when:

  • Testing web page functionality (click, fill, navigate)
  • Writing E2E test scripts (Playwright/Selenium)
  • Taking screenshots for visual regression
  • Validating page content, forms, navigation
  • Accessibility testing
  • "帮我测试这个页面" / "写个E2E自动化脚本"

DON'T use this skill when:

  • API testing → use api-tester
  • Mobile app testing → use dedicated mobile tools
  • Load/stress testing → use k6/JMeter/locust

Quick Start: Playwright

One-shot Page Test

# Navigate and screenshot
npx -y playwright@latest test --browser=chromium -g "test name"

# Or write inline script
node -e "
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ headless: true });
  const page = await browser.newPage();
  await page.goto('https://example.com');
  console.log('Title:', await page.title());
  await page.screenshot({ path: '/tmp/screenshot.png' });
  await browser.close();
})();
"

Generate Playwright Test Script

When user provides a page URL and test scenario, generate:

// tests/example.spec.js
const { test, expect } = require('@playwright/test');

test.describe('Login Page Tests', () => {

  test('TC001: Successful login', async ({ page }) => {
    await page.goto('https://app.example.com/login');

    // Fill form
    await page.fill('input[name="username"]', 'admin');
    await page.fill('input[name="password"]', 'Admin@123');
    await page.click('button[type="submit"]');

    // Verify redirect
    await expect(page).toHaveURL(/dashboard/);
    await expect(page.locator('h1')).toContainText('Welcome');
  });

  test('TC002: Login with empty fields', async ({ page }) => {
    await page.goto('https://app.example.com/login');
    await page.click('button[type="submit"]');

    // Verify validation messages
    await expect(page.locator('.error-message')).toBeVisible();
  });

  test('TC003: Login with wrong password', async ({ page }) => {
    await page.goto('https://app.example.com/login');
    await page.fill('input[name="username"]', 'admin');
    await page.fill('input[name="password"]', 'wrongpass');
    await page.click('button[type="submit"]');

    await expect(page.locator('.error-alert')).toContainText('Invalid');
  });
});

Run tests:

# Install Playwright browsers (first time)
npx playwright install chromium

# Run tests
npx playwright test tests/example.spec.js --reporter=list

# Run with headed browser (visible)
npx playwright test --headed

# Run specific test
npx playwright test -g "TC001"

# Generate HTML report
npx playwright test --reporter=html
npx playwright show-report

Common UI Test Patterns

Element Locator Strategies (priority order)

  1. data-testid attribute (most stable)
  2. role + accessible name
  3. placeholder / label text
  4. CSS selector
  5. XPath (last resort)
// Preferred
page.getByTestId('submit-btn')
page.getByRole('button', { name: 'Submit' })
page.getByPlaceholder('Enter email')
page.getByLabel('Username')

// Fallback
page.locator('button.submit-btn')
page.locator('//button[contains(text(),"Submit")]')

Wait Strategies

// Wait for element
await page.waitForSelector('.result-list');

// Wait for navigation
await page.waitForURL('**/dashboard');

// Wait for network idle
await page.waitForLoadState('networkidle');

// Wait for specific response
const response = await page.waitForResponse('**/api/users');

Screenshot & Visual Comparison

// Full page screenshot
await page.screenshot({ path: 'full-page.png', fullPage: true });

// Element screenshot
await page.locator('.chart').screenshot({ path: 'chart.png' });

// Visual comparison (Playwright built-in)
await expect(page).toHaveScreenshot('homepage.png');

Test Scenarios Checklist

For any web page, consider testing:

Category Test Points
Navigation Links work, breadcrumbs correct, back button, deep links
Forms Required fields, validation messages, submit, reset
Auth Login, logout, session expiry, role-based access
Responsive Mobile viewport, tablet, desktop breakpoints
Accessibility Tab order, screen reader, color contrast, ARIA
Error States 404 page, network error, empty state, timeout
Data Display Pagination, sorting, filtering, search
File Operations Upload, download, preview

Accessibility Quick Check

// Install axe-core for a11y testing
// npm install @axe-core/playwright

const { test, expect } = require('@playwright/test');
const AxeBuilder = require('@axe-core/playwright').default;

test('accessibility scan', async ({ page }) => {
  await page.goto('https://example.com');
  const results = await new AxeBuilder({ page }).analyze();
  expect(results.violations).toEqual([]);
});

Tips

  • Always use headless: true in CI environments
  • Set reasonable timeouts (default 30s is often too long)
  • Use page.waitForLoadState('networkidle') before assertions
  • For flaky tests: add retries in config, not in test code
  • Screenshot on failure is invaluable for debugging

Selenium (Python) Reference

When Playwright is not available or user prefers Selenium:

"""Selenium E2E Test Example"""
import pytest
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.chrome.options import Options

@pytest.fixture
def driver():
    opts = Options()
    opts.add_argument('--headless')
    opts.add_argument('--no-sandbox')
    opts.add_argument('--disable-dev-shm-usage')
    d = webdriver.Chrome(options=opts)
    d.implicitly_wait(10)
    yield d
    d.quit()

class TestLogin:
    def test_successful_login(self, driver):
        driver.get('https://app.example.com/login')
        driver.find_element(By.NAME, 'username').send_keys('admin')
        driver.find_element(By.NAME, 'password').send_keys('Admin@123')
        driver.find_element(By.CSS_SELECTOR, 'button[type=submit]').click()

        WebDriverWait(driver, 10).until(
            EC.url_contains('/dashboard')
        )
        assert 'dashboard' in driver.current_url

    def test_screenshot_on_failure(self, driver):
        driver.get('https://app.example.com/broken-page')
        driver.save_screenshot('/tmp/failure.png')

Install: pip install selenium webdriver-manager

Playwright vs Selenium — When to Choose

维度 Playwright Selenium
安装 npx playwright install 一键搞定 需要 WebDriver + 浏览器匹配
速度 更快(原生 CDP/WebSocket) 较慢(HTTP 协议通信)
自动等待 内置智能等待 需手动写 WebDriverWait
多浏览器 Chromium/Firefox/WebKit Chrome/Firefox/Edge/Safari
语言 JS/TS/Python/Java/.NET Python/Java/C#/Ruby/JS
适合 新项目、快速验证、CI 已有 Selenium 框架的团队

建议: 新项目优先 Playwright,已有 Selenium 资产的项目继续用 Selenium。

Usage Guidance
This skill is coherent for browser automation, but be cautious: it runs commands (node/npx) that will download packages and browser binaries, visit URLs you provide, and may create files (screenshots, reports). Never run tests against production sites or supply real user credentials—use isolated test/staging environments and test accounts. Review any generated test scripts before executing and run them in a sandbox/CI runner or VM if you want to limit side effects.
Capability Analysis
Type: OpenClaw Skill Name: web-tester Version: 1.0.0 The 'web-tester' skill bundle is a standard tool for web UI automation and E2E testing using Playwright and Selenium. The instructions in SKILL.md provide legitimate code snippets for browser navigation, form interaction, and screenshot capture, all aligned with the stated purpose. No evidence of data exfiltration, malicious execution, or prompt injection was found.
Capability Assessment
Purpose & Capability
Name/description ask for browser automation and Playwright usage and the SKILL.md only requires Node.js and npx usage consistent with Playwright workflows. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
Instructions are focused on navigating pages, interacting with elements, screenshots, and generating tests. They include runnable examples (node -e, npx playwright commands) and example test cases that use placeholder credentials. This is within scope, but it means the agent's runtime actions will visit arbitrary URLs, execute JS, write screenshots to disk, and may prompt for or embed credentials—so users should avoid running against production or providing real secrets.
Install Mechanism
This is an instruction-only skill with no install spec. It relies on npx/node at runtime; running the provided commands (npx playwright install, npx playwright test) will cause npm/npx to download packages and browser binaries, which is expected for Playwright but is a network download step to be aware of.
Credentials
The skill declares no required environment variables or credentials (proportionate). However, example tests include plaintext placeholder usernames/passwords; the agent or user could be tempted to use real credentials—do not supply production secrets. The skill may ask for target URLs and credentials at runtime, which are natural for this domain but should be scoped to test/staging accounts.
Persistence & Privilege
always is false and the skill does not request persistent/system-wide configuration or elevated privileges. Model invocation is enabled by default (normal) so the agent could run the described commands autonomously when invoked.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install web-tester
  3. After installation, invoke the skill by name or use /web-tester
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Playwright & Selenium E2E testing, UI automation, accessibility checks, screenshot comparison
Metadata
Slug web-tester
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Web Tester?

Web UI testing and browser automation using Playwright or Selenium. Navigate pages, interact with elements, take screenshots, validate UI state, generate E2E... It is an AI Agent Skill for Claude Code / OpenClaw, with 92 downloads so far.

How do I install Web Tester?

Run "/install web-tester" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Web Tester free?

Yes, Web Tester is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Web Tester support?

Web Tester is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Web Tester?

It is built and maintained by zhanghengyi1986-afk (@zhanghengyi1986-afk); the current version is v1.0.0.

💬 Comments