# Tests & Integration ## 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.coveragelabs.io/services/fuzzing-campaign/tests-and-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.