Skip to content

FastProof by FransHub

FastProof documentation

FastProof is an open-source (Apache-2.0), self-hosted test reporting server. Your CI uploads the reports it already writes (allure-results, JUnit XML, CTRF, Playwright JSON or the FastProof JSON format), and FastProof keeps every launch with its history per test, finds flaky tests, groups failures and helps the team triage them. One Rust binary serves the API, the ingest queue and the web UI; it needs PostgreSQL and either an S3-compatible bucket or a directory.

Why FastProof

  • Light

    One static binary in a distroless image, PostgreSQL and object storage. No Elasticsearch, no message broker, no JVM. Any number of replicas share the work through PostgreSQL; Valkey is optional.

  • Open

    Apache-2.0, self-hosted, no per-seat licence and no feature gates. Formats in and out are documented, including the FastProof JSON report schema.

  • Allure-compatible

    Test identity follows Allure 2.45+ and Allure 3 (testCaseId, fullName, parameter hashes), so your tests keep their history when you move from Allure Report, and Allure adapters work unchanged.

  • FastMock correlation

    When tests run against FastMock, the traceparent of each attempt links the result to the mock interactions it caused, so a failure shows what the system under test really sent.

Start here

  • Getting started

    Run FastProof with Docker or Docker Compose, create a project and upload the first report.

  • Concepts

    Projects, launches, shards, test identity, retries and flaky tests.

  • CI recipes

    GitLab CI, GitHub Actions and Jenkins with fastproof upload and fastproof watch.

  • Report formats

    allure-results, JUnit XML variants, CTRF, Playwright JSON and the FastProof JSON report.

  • Migrating from Allure Report

    Keep your tests and adapters; point the upload at FastProof.

Operate

  • Configuration

    Every environment variable of the server and the CLI.

  • Helm chart

    Values, PostgreSQL and S3 options, upgrades and running several replicas.

  • Security

    Authentication, roles and permissions, attachment sandboxing, reporting vulnerabilities.

  • Limits

    Size, depth and count limits applied to every upload.

  • Roadmap

    Test management, ReportPortal agent compatibility, own reporters, FastProof Analysis.

Conventions in these pages

  • FastProof listens on http://localhost:8080 (UI, API, sign-in) and http://localhost:9090 (metrics, health and readiness). In Kubernetes both are ports of the chart's Service (fastproof for a release named fastproof).
  • FASTPROOF_TOKEN holds an API token; FASTPROOF_URL the server URL; FASTPROOF_PROJECT the project key.
  • Example host names use example.com, example addresses 198.51.100.0/24 and 203.0.113.0/24.
  • FastProof is at an early stage (0.1.0-dev1); names on these pages are the ones the first release ships.