esc

Verify

Run the test pipelines you already have, and see why they fail.

Run the test pipelines you already have, from one place, and see why a run failed without digging through a separate CI dashboard for each git host.

Verify: The test gates

Every run, on every host, and why it failed.

  1. Test runs on every host

    Trigger test pipelines in GitHub Actions, Bitbucket Pipelines and GitLab CI from one place.

  2. Live step status

    Step status updates as your pipeline moves. No refresh button. Every step's log is one click away, GitHub Actions included.

  3. Scutor explains failures

    Scutor reads a failed run's steps and logs and tells you which step broke and why. If it offers to re-run something, it waits for your click.

Test runs on every host

Pick a repo and branch and DeployNX triggers the test pipeline in your CI. Steps update as they run, failed steps come first, and each log is one click away.

  • Step status updates as your pipeline moves. No refresh button.
  • Every step's log is one click away, GitHub Actions included.

Scutor explains failures

Ask Scutor why a run is red. It reads the failed step's log and answers with the evidence linked. If it offers to re-run something, it waits for your click.

  • Scutor cannot approve anything. It acts only after you click, and every action is logged with your name.
Scutor· billing-workerIllustrative

Why is billing-worker blocked?

Run #1183 on main failed at step integration-tests after 4m 02s. The log ends with ConnectionError: postgres:5432 refused (line 412).

The last passing run was #1179. This looks like the test database not starting, not a code change.

Open step log

Want me to re-run the tests?

Run tests

billing-worker @ main

CancelRun tests

Scutor acts only after you click, and can't approve anything. Every action is logged with your name.

Pipelines found for you

DeployNX reads your CI file and suggests the test, stage and production pipelines for each repo. Confirm them once. Other pipelines, like migrations and smoke suites, can run on demand.

  • Run migrations, smoke suites and other non-deploy pipelines on demand. Stage and prod pipelines always go through approval.

Verify: Stage by stage

Everything in the Verify stage

In the order a test run meets them.

  1. Connect

    The pipelines you already have, on the host they live on.

    • Test runs on every host

      Trigger test pipelines in GitHub Actions, Bitbucket Pipelines and GitLab CI from one place.

    • Pipelines found for you

      DeployNX reads your CI file, finds the test, stage and production pipelines, and asks you to confirm them.

  2. Watch

    Every step as it runs, and its log.

    • Live step status

      Step status updates as your pipeline moves. No refresh button.

    • Step logs

      Every step's log is one click away, GitHub Actions included.

    • Pipeline runs

      Run migrations, smoke suites and other non-deploy pipelines on demand. Stage and prod pipelines always go through approval.

  3. Diagnose

    Why a run failed, and which steps keep failing.

    • Scutor explains failures

      Scutor reads a failed run's steps and logs and tells you which step broke and why.

    • Test health

      Steps marked flaky or broken from same-commit retries, ranked by the releases they block.

    • Per-test results and quarantine

      Every test with its flaky score and history, from the JUnit XML your pipelines upload and the failures in each run's logs. Quarantine a flaky test so a run that fails only on it counts as passed.

Product views on this page are illustrative demo data. Test runs, pipeline runs, live step status and logs work on GitHub Actions, Bitbucket Pipelines and GitLab CI.