Skip to main content
To protect live capital and ensure robust order routing, Hoox mandates a rigorous testing pipeline. With money on the line, we verify every contract calculation, rate-limiting gate, and database query. Our test suite is powered natively by Bun’s high-speed test runner, comprising ~124 test files and ~4,500 individual test assertions split across five diagnostic layers.

🎚️ The 5 QA Testing Layers


⚡ Running Tests: CLI Commands

A. Core Platform Verification (Excluding Live)

B. Workspace-Specific Targeted Runs

To optimize developer feedback loops, you can target specific workspaces or workers:

C. Security & Fuzz Testing

D. Advanced Integration & Live Runs


🔒 Type-Safe Mocking Specifications (No as any)

To enforce strict TypeScript compiler safety, test files must never utilize as any to bypass types when mock-binding resources. Always cast stubs using as unknown as Env:

🚢 Continuous Integration Gates & Coverage Targets

Our GitHub Actions workflows enforce the following quality gates:
  1. TypeScript Type Safety: All workspaces must compile without errors using tsc --noEmit.
  2. Coverage Thresholds: The monorepo enforces a minimum 80% coverage threshold across all core execution paths (packages/cli, packages/shared, workers/hoox, workers/trade-worker).
  3. Dependency Audit: bun audit runs after tests to detect known vulnerabilities (informational, doesn’t block CI).
  4. Secret Scanning: gitleaks scans all commits for hardcoded secrets on every push/PR (informational).
  5. CodeQL: Weekly security-and-quality analysis for JavaScript/TypeScript.

🔗 Next Steps

Last modified on June 17, 2026