🧪 Testing Guide

The project includes both Solidity contract tests (using Foundry) and frontend tests (using Vitest).

Contract Tests

Foundry tests are written in Solidity and live alongside the contracts in the contracts/test/ directory.

make test-contracts

Test Files

File	Tests
MockERC20.t.sol	Minting, only-faucet restriction, setFaucet, events, ownership transfer
Faucet.t.sol	Claim mETH, claim mBTC, 24h cooldown, time-remaining, lifetime tracking, double-claim revert, onlyOwner setters
MockDEX.t.sol	Add liquidity, swap mETH→mUSDC, swap mUSDC→mETH, slippage protection, rate updates, insufficient liquidity, fuzz tests with bound()

Coverage

make coverage

Generates an LCOV coverage report showing line-by-line coverage of all contracts.

Frontend Tests

Frontend tests use Vitest and React Testing Library. Test files live in frontend/tests/.

make test-frontend

Test Areas

• Utility functions: calculateOutput, applySlippage, formatDexBalance, formatRate, calculatePriceImpact
• Contract logic: formatTokenBalance, formatCountdown, formatTimestamp

Running All Tests

make test

This runs both contract tests and frontend tests sequentially.

Best Practices

• Write tests before implementing new features (TDD where practical)
• Use fuzz testing for numerical edge cases in contracts
• Test all error paths and revert conditions
• Aim for 100% line coverage on all contracts
• Frontend utility functions should be pure and easily testable