{"enrichment":{"faq":[{"a":"webapp-testing enables you to write and execute Playwright scripts that automate verification of web application UI behavior and user interactions. Start by launching a browser instance, navigating to your target URL, and using Playwright's locator methods to find and interact with page elements. You can assert on element visibility, text content, and DOM state to validate that your application behaves as expected. The skill supports comprehensive browser-based testing workflows directly within Claude Code, letting you build end-to-end tests without leaving your coding environment.","q":"How do I test a web application using Playwright?"},{"a":"webapp-testing teaches best practices for reliable end-to-end browser automation. Key recommendations include using proper waiting strategies instead of fixed delays, selecting stable and semantic selectors rather than brittle XPath or CSS chains, and avoiding common anti-patterns that lead to flaky tests. Implement explicit waits for elements to be actionable, use data-testid attributes when possible, and structure your tests to be independent and deterministic. The skill guides you away from practices that cause intermittent failures and toward patterns that make your automation robust across dynamic web applications.","q":"What are the best practices and anti-patterns to avoid when using Playwright?"},{"a":"webapp-testing covers waiting strategies and selector patterns essential for testing dynamic pages. Rather than relying on sleep timers, use Playwright's built-in wait methods such as waiting for elements to be visible, enabled, or stable. For selectors, prefer semantic approaches like role-based queries or data attributes over fragile CSS or XPath expressions. When testing single-page applications or pages with frequent DOM updates, combine explicit waits with reliable selector strategies to ensure your tests interact with the correct elements at the right time. The skill demonstrates how to handle asynchronous content loading and network-dependent UI changes.","q":"How do I implement proper waiting strategies and selector patterns for dynamic web applications?"},{"a":"webapp-testing provides debugging techniques using screenshots, logs, and DOM inspection to troubleshoot web app testing issues. Capture screenshots at critical test points to visualize the application state when assertions fail. Enable console log capture to collect browser-side messages and errors, and use Playwright's built-in inspector to examine the DOM and trace element interactions. These debugging tools help you identify why selectors fail to match, why waits timeout, or why user interactions don't produce expected results. The skill teaches you to leverage these diagnostic capabilities to quickly resolve test failures and understand application behavior.","q":"How can I debug UI issues with Playwright using screenshots and logs?"},{"a":"Yes, webapp-testing supports automating form submission, validation, and multi-page navigation testing. You can programmatically fill form fields, trigger validation by submitting forms, and assert on validation messages or page redirects. The skill enables you to navigate across multiple pages, verify that state persists correctly, and test complex user workflows that span several screens. You can also validate form behavior under various conditions\u2014such as missing required fields or invalid input\u2014to ensure your application handles edge cases properly.","q":"Can webapp-testing help me automate form submission, validation, and multi-page navigation testing?"},{"a":"webapp-testing is licensed under the MIT License, which permits you to use, modify, and distribute the skill freely for both commercial and personal projects, provided you include a copy of the license and acknowledge the original authors.","q":"What is the license for webapp-testing?"}],"shadow_tags":["browser-automation","end-to-end-testing","ui-validation","test-debugging","web-qa","frontend-testing","selector-strategies","test-patterns"],"summary_rewrite":"This skill enables you to write and run Playwright test scripts within Claude Code, automating verification of web application UI behavior and user interactions. Deploy comprehensive browser-based testing workflows without leaving your coding environment."},"files":[{"bytes":7595,"path":".claude/skills/webapp-testing/SKILL.md","sha256":"c9a24dfa5274a3dd6901eb07475ea84601397ff422916bd7d70460a2f0396249","url":"https://skillfed.io/files/curiositech/some_claude_skills/webapp-testing/5d3c3afa/SKILL.md"}],"id":"curiositech/some_claude_skills/webapp-testing","links":{"html":"https://skillfed.io/curiositech/some_claude_skills/webapp-testing","md":"https://skillfed.io/curiositech/some_claude_skills/webapp-testing.md","repo":"https://github.com/curiositech/some_claude_skills"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":27,"language":"TypeScript","last_updated":"2026-07-14","license":"MIT","name":"webapp-testing","publisher":"curiositech","stars":164},"relations":{"similar":[{"id":"bobmatnyc/claude-mpm-skills/webapp-testing"},{"id":"eyadsibai/ltk/webapp-testing"},{"id":"SpaceZephyr/myskill/webapp-testing"},{"id":"Wide-Moat/open-computer-use/webapp-testing"},{"id":"silvainfm/claude-skills/webapp-testing"},{"id":"kill136/axon/webapp-testing"},{"id":"curiositech/some_claude_skills/playwright-screenshot-inspector"},{"id":"shajith003/awesome-claude-skills/webapp-testing"},{"id":"alleneee/skill-agent/webapp-testing"},{"id":"warpdotdev/oz-skills/webapp-testing"}]},"slug":{"owner":"curiositech","repo":"some_claude_skills","skill":"webapp-testing"},"version":"5d3c3afa"}