Documentation
  • 👋Welcome to Coverage!
  • Methodology
    • 📑Request Form
    • 🔍Scope of Work
    • 📊Rates
    • 🗃️Statement of Work
    • 🗣️Communication
  • Services
    • 🕵️Security Review
      • Context & Cleanup
      • Manual Review
      • Quality Assurance
      • Fix Review
      • Final Report
    • 🥷Fuzzing Campaign
      • Invariant Development
      • Implementation
      • Tests & Integration
      • Fix Review
      • Final Report
  • Resources
    • 🖌️Media Kit
Powered by GitBook
On this page
  • Running the Test Suite
  • CI/CD Integration
  1. Services
  2. Fuzzing Campaign

Tests & Integration

We run a 48-hour fuzzing campaign to extensively test all protocol invariants. The test suite is then integrated into your CI/CD, triggering short fuzzing campaigns on every commit.

Running the Test Suite

Following the completion of invariant development, we initiate a 48-hour fuzzing campaign designed to uncover deeper edge cases that manual review might miss. The campaign is typically executed on cloud infrastructure (AWS/GCP) to ensure consistent performance and enable parallel execution.

CI/CD Integration

We integrate the test suite into your GitHub Actions CI/CD pipeline, triggering short fuzzing campaigns on every commit. This ensures that new code is continuously validated against protocol invariants, preventing buggy code from being pushed. We provide all necessary configuration files and a detailed integration guide, enabling your team to maintain and expand the tests post-engagement.

PreviousImplementationNextFix Review

Last updated 2 months ago

🥷