Running in CI
Exit codes make Fuzzloom a normal CI step: 1 fails the build on a finding, and 2 fails it on an infrastructure problem. Pin a seed for a deterministic check, or leave it random to explore further on every run. The seed is printed either way. --junit writes a report that test dashboards understand. Findings become <failure> and infrastructure problems become <error>, so a dashboard never shows out-of-gas as a broken property.
GitHub Actions, on Linux so the native backend is available:
yaml
- uses: actions/setup-node@v4
with: { node-version: "22" }
- name: Install Fe
run: |
curl -fsSL https://raw.githubusercontent.com/argotorg/fe/master/feup/feup.sh | bash -s -- --version v26.6.0
echo "$HOME/.fe/bin" >> "$GITHUB_PATH"
- run: npx -y fuzzloom doctor
- run: npx -y fuzzloom replay --junit reports/replay.xml # saved failures stay fixed
- run: npx -y fuzzloom fuzz --junit reports/fuzz.xml # new inputs every run
- run: npx -y fuzzloom diff --junit reports/diff.xml # sonatina against nativeFuzzloom's own pipeline, scripts/ci.sh, is a complete working example. It runs on CircleCI.