E2E TESTING FOR WEB3 APPS

Wallet flows are the hardest thing to test. They're what I test.

Start with a fixed-scope Wallet Flow Audit: your critical flows exercised against a real MetaMask, every failure documented and prioritized — two weeks, fixed price. Then build only what the evidence says you need.

Real MetaMask extension · Live app.aave.com · Headless in GitHub Actions · Read the code →

THE GAP

Your coverage stops where the money starts.

Unit tests

They can't see the wallet

The MetaMask popup, the reject path, the network switch — all of it lives outside your app's code. Unit tests never touch it.

Every deploy

A refactor breaks it silently

A UI change kills connect, supply, or withdraw — and nothing turns red. Your users find out first, on-chain.

Hiring

A QA hire takes months

The search runs; the risk stays open. The audit closes it in two weeks — and hands your team a prioritized plan instead of guesses.

THE AUDIT

Two weeks. Three steps. Evidence, not opinions.

Days 1–2 · Map

We pick the flows that matter

A 60-minute call with your team, plus a staging URL or repo access. That's all I need from you.

Days 3–10 · Test

Real wallet, real flows

Every critical flow driven against a real MetaMask: connect, transactions, rejections, failure states. Each break documented with a reproduction and a severity.

Days 11–14 · Report

Findings you can act on

A prioritized findings report, working starter specs your team keeps, and a scoped fixed-price plan for full coverage — with the audit fee credited if you build.

WHAT'S INCLUDED

What the audit hands you.

Critical wallet flows exercised on a real MetaMask — connect / reject / disconnect, transactions, failure states
Every failure documented with a reproduction and a severity
Coverage map: what's tested, what's exposed, what breaks first
Working starter specs (Playwright + Synpress) your team keeps
A scoped, fixed-price plan for the full suite build
Audit fee credited 100% against a build within 60 days

DE-RISKED

The audit pays for itself.

Commission the suite build within 60 days and 100% of the audit fee is credited against it.

Book 20 minutes →

PRICING

Fixed scope. Fixed price. No surprises.

3 FOUNDING SLOTS — 50% OFF

Wallet Flow Audit

€4,900

fixed · two weeks · founding rate €2,450

  • Critical flows tested on a real wallet
  • Findings with reproductions & severity
  • Starter specs your team keeps
  • Fee credited against a build (60 days)
Book the audit

E2E Suite Build

from €12k

fixed · scoped from the audit

  • Full suite in your repo & CI
  • Wallet + app flows, alerts, reporting
  • Everything a hire builds in a quarter
  • 50/50 payment · scope fixed upfront
Scope a build

Retainer

€2,500

per month · 3-month minimum

  • Your suite maintained as you ship
  • Drift fixed fast; new flows monthly
  • Existing suites from €3,500/mo
  • Priority response on breakage
Ask about retainers

Shipping a wallet SDK? Ask about SDK Integration Assurance — continuous E2E across your integration examples. From €4k/mo.

WHO YOU'RE HIRING

No agency. No handoffs. One engineer.

I'm André Guerra, a QA automation engineer. End-to-end and regression testing is my day-to-day craft; wallet-flow automation is the specialty I've built in public — including replacing most of a broken Synpress release to get a real MetaMask signing real transactions, headless in CI, verified against on-chain balances.

Whether it's the audit, the build, or the retainer — the person who scopes it, writes it, and answers on Slack is me.

andre@prumada.pt · X · LinkedIn · GitHub

Why “Prumada”?

On a building site, the prumada is the plumb line — the vertical reference every wall is checked against. That's what a test suite is for your app: the fixed line that tells you, on every deploy, whether things still stand straight.

FAQ

The ones everyone asks

Is this only for web3 apps?

No. The audit works for any web app — same method, same rigor, minus the wallet layer. Wallet-extension testing is simply the hard part most teams can't cover, so it's the part I prove in public.

Who owns the code?

You do. The suite lives in your repository from day one. No license, no lock-in, no dependency on me — maintenance is optional.

What do you need from us?

A staging URL or repo access, one hour of an engineer's time in week one, and a Slack or Discord webhook for alerts. That's the whole list.

Can you sign an NDA?

Happily, before seeing anything. I operate through a Portuguese limited company (DúvidaExclusiva, Unipessoal Lda), so invoicing and contracts are standard.

How do payments work?

Audits are invoiced upfront; builds are 50/50 with milestones on larger scopes; retainers run monthly. EUR by default, USD on request — and USDC is accepted through a compliant processor.

CONTACT

Tell me what breaks.

Three lines about your app is enough. I reply within a day — usually the same one.

Email directly

Your details are never shared.