683 Tests in a 15-Package Monorepo: Docker Testing Strategy for AI Wallets

Description and use

In the 15‑package WAIaaS monorepo, 684+ tests validate every stage of the 7‑step transaction pipeline before the Docker image is built, ensuring reliability and security for self‑hosted AI wallets.

Problem

Self‑hosted AI wallet services must be trustworthy, but third‑party providers expose private keys and can fail or change APIs. Without rigorous testing, bugs in transaction pipelines can cost real money.

Outcome

The 15‑package monorepo with 684+ tests ensures that every stage of the transaction pipeline is validated before the Docker image is built, giving self‑hosters confidence that their AI wallet infrastructure is secure and reliable.

Workflow

• Clone the WAIaaS repo
• Run "docker compose up -d" for development
• Use "docker run" with WAIAAS_AUTO_PROVISION=true for production
• Retrieve auto‑generated master password from /data/recovery.key
• Configure secrets via Docker Secrets for production
• Start the daemon and use the CLI to initialize wallets and MCP sessions
• Generate a session token for the AI agent
• Use the session token with the SDK to perform wallet operations

Evidence

WAIaaS is an open‑source, self‑hosted Wallet‑as‑a‑Service built for exactly this. And the 684+ test files spread across its 15‑package monorepo are what make the self‑hosting story believable rather than aspirational.

Source

The Compose file includes a secrets overlay specifically for production: ... docker compose -f docker-compose.yml -f docker-compose.secrets.yml up -d

Source

Once the daemon is running, the CLI handles the rest: npm install -g @waiaas/cli waiaas init waiaas start waiaas quickset --mode mainnet

Source