Web E2E Testing FAQs

Name: Web E2E Testing
Author: Uniswap

Question 1

How does it help with debugging failed tests?

Accepted Answer

The skill integrates with Playwright MCP tools, enabling Claude to take screenshots, inspect console messages, and interact with the browser directly. It also provides guidance on using Playwright's UI and debug modes to step through failures.

Question 2

What does the Web E2E Testing skill do?

Accepted Answer

This skill provides Claude with the specialized knowledge to create, execute, and debug end-to-end Playwright tests for the Uniswap web application. It handles complex tasks like setting up local Anvil blockchain environments, mocking GraphQL responses, and managing DeFi-specific test fixtures.

Question 3

How does this skill simplify DeFi wallet testing?

Accepted Answer

It utilizes a custom 'test0' wallet configuration that automatically connects via wagmi when the Playwright environment is detected. This allows Claude to test wallet-dependent features immediately without needing manual connection steps or UI interactions.

Question 4

Can I use this skill to test blockchain-specific logic?

Accepted Answer

Yes. The skill includes advanced Anvil fixtures that allow Claude to manipulate a local blockchain state. You can programmatically set ERC20 balances, manage token allowances, mine blocks, and use snapshots to ensure test isolation.

Question 5

When should I use the /web-e2e slash command?

Accepted Answer

You should ALWAYS invoke `/web-e2e` before attempting to run, create, or debug any E2E tests. This command initializes Claude's understanding of the codebase's specific test architecture, required environment variables, and custom Playwright commands.

Web E2E Testing

Web E2E Testing

主な機能

ユースケース

主な機能

ユースケース