testing-patterns

A set of testing guidelines for MetaMask Connect integrations. It explains how to use fake wallet providers and clients, reset shared state, wait for asynchronous setup, and choose safe test networks.

In plain words
What is it for?
Unit-testing provider requests, mocking MetaMask clients, testing events and connection flows, resetting clients between tests, and running end-to-end tests on Sepolia or Solana devnet.
Why use it?
It makes wallet tests predictable and avoids failures caused by shared singleton clients, real mainnet use, or unhandled asynchronous setup.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/metamask/metamask-connect-cursor-plugin/testing-patterns
Clone the repo
git clone --depth 1 https://github.com/MetaMask/metamask-connect-cursor-plugin
Per session 490 This file is loaded in full into every session.
When invoked 490 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00490 $0.00490
Opus 5 $0.00245 $0.00245
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured yesterday against content hash 05b0173278ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/testing-patterns.mdc · 57 lines

What it actually says

MetaMask Connect Testing Patterns

Provider Mocking

  • Mock the EIP-1193 provider's request method for unit tests
  • Create a mock provider factory that returns controlled responses
  • Example: const mockProvider = { request: vi.fn(), on: vi.fn(), removeListener: vi.fn() }
  • Mock different responses for different methods (eth_accounts, eth_chainId, etc.)

Client Mocking

  • Mock createEVMClient to return a controlled client object
  • Mock client.connect(), client.disconnect(), client.getProvider(), client.switchChain()
  • For multichain: mock createMultichainClient, client.invokeMethod(), client.on()

Singleton Cleanup

  • createMultichainClient is a singleton — tests that create clients will share state
  • Clear or reset the singleton between test runs
  • Use beforeEach/afterEach to ensure clean state

Test Networks

  • Use Sepolia (0xaa36a7) for E2E tests, never mainnet
  • For Solana E2E: use devnet — supported in the MetaMask browser extension (mobile supports mainnet only)
  • Mock RPC responses for unit tests; use real RPCs only for integration tests

Async Client Initialization

  • createEVMClient and createMultichainClient are async — tests must await them
  • In React testing, await the client before rendering components that depend on it
  • Use act() wrapper for React state updates triggered by SDK events

Error Simulation

  • Test user rejection: throw { code: 4001, message: 'User rejected' }
  • Test pending connection: throw { code: -32002, message: 'Already pending' }
  • Test network errors: simulate RPC failures
  • Test disconnect scenarios

Event Testing

  • Test that components react to accountsChanged, chainChanged events
  • Simulate events by calling the mock provider's event handlers
  • Test display_uri event handling for headless mode

Solana Testing

  • Mock wallet-standard wallet object
  • Mock signMessage, signAndSendTransaction features
  • Test wallet discovery with mocked wallet registry
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 57 lines · 490 tokens per session scan A 05b0173278ce

Subscribe to this mod's changes

testing-patterns is a cursor rule published in the GitHub repository MetaMask/metamask-connect-cursor-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 490 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.