Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ By applying design patterns, teams can:
- Simplify onboarding of new contributors.
- Adapt quickly to UI or business logic changes.

> ℹ️ The examples in this section use Playwright with JavaScript and TypeScript.

## AAA (Arrange-Act-Assert)

Every test is divided into three parts:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,6 @@ title: Overview

Web3 E2E (end-to-end) automation focuses on testing decentralized applications (dApps) from a user’s perspective, validating how smart contracts, wallets, frontends, and blockchain nodes interact in real-world scenarios. This type of automation typically involves tools like Playwright, Cypress, or Selenium, combined with test wallets, mock chains, or real testnets.

We use [Synpress with Playwright](https://docs.synpress.io/docs/setup-playwright) which combines modern e2e testing power with Web3 context. This is a powerful combination that simplifies the complexity of Web3 e2e testing by:

- Providing a reliable, scalable testing environment for dApps
- Automating browser wallet flows (MetaMask, Phantom)
- Offering a built-in mock wallet for testing without a real wallet (Ethereum Wallet Mock)
- Enabling seamless integration for launching local test networks (with Anvil)

> ✅ [Synpress with Playwright setup](https://www.notion.so/Synpress-setup-1fb9a4c092c7809fb305f33bf3b7a4fd?pvs=21)

## Best Practices

Best practices in E2E automation testing ensure that the testing process is efficient, reliable, maintainable, and scalable. Without them, automated tests can quickly become fragile, slow, or difficult to manage, defeating the purpose of automation.
Expand Down
Loading