testing-web-forms

Tests web form submission, validation, error states, and accessibility using Playwright-driven browser automation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/celikgo/webmobai --skill testing-web-forms-celikgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-web-forms
Source: https://github.com/celikgo/webmobai/tree/main/.claude/skills/testing-web-forms
Command: npx skills add https://github.com/celikgo/webmobai --skill testing-web-forms-celikgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying that login, signup, checkout, and contact forms behave correctly across happy paths, invalid inputs, and error states is repetitive and error-prone. This Skill automates form testing in a real browser, catching silent submission failures, missing validation, and accessibility gaps before users do. ## Core Features & Use Cases - Happy Path & Validation Matrix: Fills fields, submits, and verifies outcomes, then runs a default matrix of invalid inputs per field type (email, password, number, date, phone, checkbox). - Multi-Step Flow Testing: Walks checkout and onboarding wizards step by step, checking back-navigation data retention and final confirmation states. - Form Accessibility Audit: Verifies keyboard navigation, Enter-to-submit, input labels, and screen-reader error announcements using the accessibility tree and audit tools. - Use Case: Before launching a new signup funnel, point the Skill at the staging URL with test credentials — it reports which validation cases the form blocks, which sneak through, and whether error messages are announced to screen readers, with screenshots and an HTML report. ## Quick Start Test the login form at https://staging.example.com/login using the provided test credentials and report validation and accessibility issues.

Frequently Asked Questions about testing-web-forms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a login or signup form automatically?▼

Provide the form URL, test credentials, and the expected success outcome such as a redirect or success message. The Skill fills fields with webmobai_type, submits, waits for the success signal, then runs a validation matrix of invalid inputs per field type.

How to test a form that sits behind a login page?▼

Capture an authenticated session once with webmobai_save_storage_state, then launch the browser with storage_state_path pointing to that file. This avoids re-driving the login for every validation case, which is slow and risks account lockout.

Can automated form testing handle captchas and file uploads?▼

No. reCAPTCHA and similar tools block automation, so the test stops there and the gap is reported with a recommendation to disable captcha in the test environment. File upload fields also cannot be fully tested and are noted as a gap.

Is it safe to run form tests against a production site?▼

Only with explicit confirmation. Real signups create real accounts and real checkouts may trigger charges, so the Skill asks whether the target is staging or production before submitting and never invents credentials against production systems.

Why does clicking the submit button sometimes do nothing?▼

Many forms disable the submit button until all inputs are valid, so the click silently no-ops. Check the button state with webmobai_evaluate using document.querySelector('button[type=submit]').disabled to confirm.