> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/developers/testing.md).

# Testing and CI

Unit, fuzz, invariant and fork tests, and the CI that runs them.

```bash
cd contracts
forge build                    # solc 0.8.28 for our contracts, 0.8.26 for v4-core and the hook/adapter
forge test                     # 106 tests: unit + fuzz (1,000 runs) + invariants + real v4 pool swaps
FOUNDRY_PROFILE=ci forge test  # 10,000 fuzz runs, deeper invariants

cd .. && pnpm typecheck && pnpm build    # website
node scripts/e2e-devnet.mjs              # all user actions on devnet + indexer check
node scripts/check-hook.mjs              # KyteHook fees landing in the FeeVault on devnet
```

Dependencies are installed through pnpm (OpenZeppelin 5.6.1, forge-std 1.11, Uniswap v4-core 1.0.2): no git submodules.

**CI** (`.github/workflows/ci.yml`, on every push and pull request):

* `contracts`: `forge fmt --check`, `forge build`, `FOUNDRY_PROFILE=ci forge test`
* `web`: `pnpm install --frozen-lockfile`, `pnpm typecheck`, `pnpm build`

**Intentional lint warnings:** `_mint` over `_safeMint`, strict balance equality (fee-on-transfer guard), `transferFrom` with `from` = sender or router, and `block.timestamp` comparisons (durations ≥ 1 h).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kyte.sh/developers/testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.