DeFi QA Checklist: 25 Tests Every DeFi Protocol Needs Before Launch

A practical pre-mainnet QA checklist for DeFi protocols — covering swap flows, liquidity operations, staking, bridge interactions, and price oracle failures.

DeFi protocol QA checklist pre-mainnet illustration
DeFi protocol QA checklist pre-mainnet illustration
9 min read

DeFi protocols have more failure modes than standard dApps. Beyond wallet connection and basic UI flows, you need to validate swap math, liquidity edge cases, oracle price feed behaviour, and cross-chain bridge operations.

This checklist covers the 25 tests QaLock runs on every DeFi engagement before recommending a mainnet launch.

Swap and AMM flows

Token approval flow (first-time and existing allowance). Swap execution with slippage tolerance at 0.1%, 0.5%, and 1%. Price impact warning display for large trades. Transaction failure handling when slippage exceeds tolerance. Token pair reversal and balance update after swap. High-volume swap math accuracy compared to on-chain output.

Price oracle staleness: what happens when oracle price is more than 30 minutes old? Does your UI surface the warning, or silently execute at stale price?

Liquidity and staking operations

Add liquidity with balanced and imbalanced token amounts. Remove liquidity in full and partial amounts. LP token minting and burning accuracy. Staking deposit, withdrawal, and reward claim flows. Reward accrual display accuracy (real-time vs batched update).

Edge cases: what happens if a user tries to remove liquidity when pool is near empty? What if reward claim is called when rewards are zero?

Bridge and cross-chain

Bridge initiation on source chain and receipt on destination chain. Transaction status display during bridge delay (5 to 30 minutes). Failed bridge transaction recovery flow. Incorrect network state during bridge (user switches network mid-flow).

These flows are high-risk because failed bridge transactions can result in funds stuck in limbo. Testing them thoroughly before mainnet is non-negotiable.

Want help implementing this for your product?

Book a free 30-minute QA audit — coverage report in 48 hours.