I will test the paths that usually break on a dApp: wallet connect, account switch, transaction confirm or reject, and the follow-through in your UI, first by hand, then with Playwright where your package includes automation.
I currently work as a Software Engineer in Test on a consumer crypto and rewards product, and I have a background in payments and fintech QA. This is product and UI testing on a public testnet. It is not a smart-contract audit.
You receive:
- An exploratory test of the agreed wallet and transaction paths, with a written report (bugs, severity, reproduction steps, and risks)
- Playwright (TypeScript) end-to-end coverage of those paths on the Standard and Premium tiers
- Notes on wallet states worth retesting (reject, disconnect, wrong network, pending, failed transaction)
- A short list of suggested follow-up tests
This package does not include a Solidity or smart-contract audit, mainnet testing with real funds, custody of keys, transaction signing with a real wallet, or production credentials. I only use public testnets, test wallets or extensions you provide, and sanitized staging data. The default wallet for automation is a widely used browser wallet on a public testnet; tell me if you use a different wallet or connect kit.
Never send seed phrases, private keys, or recovery phrases. If those appear in the order, I will pause and ask for a test-only setup.