NerveStax · Tested before merge
Every change, tested before merge.
Every dbt pull request is built and tested on your own Airflow, in a schema of its own, on real data. Production is read, never written.
1:30
How it works
Tested before merge, step by step.
Ask
Describe the change. The agent builds it and runs your tests first.
Approve
It asks before it opens the pull request.
Test
Airflow builds the changed models, and everything downstream, in an isolated schema.
Result
Pass or fail comes back to the pull request and to the PR Tests page.
Review
You see exactly what it touches downstream.
Merge
A person merges it. Your review rules and CI still apply.
Isolation
A schema of its own. Production untouched.
Test tables go into a dedicated test schema. A project can use a separate warehouse login that cannot write production, and production schemas are compared before and after every run.
- Test tables are removed within minutes of the pull request closing.
- A daily check reports anything left behind.
- A project still on its production login is told so plainly.
The pull request
Built and tested before it is opened.
The agent edits your dbt project on its own branch, builds and tests only what the change affects, and opens a pull request under the engineer’s own identity. Agent pull requests are labelled for testing automatically.
- Merge checks stop a change that would break a schedule or a certified definition.
- Merging always happens in your git server, by a person.
Risky changes
Refused, or held for a second reviewer.
Some changes are not tested automatically. They are refused, or held until someone who did not write the code reviews them.
Not tested automatically
- Files outside the project
- Symlinks
- Credentials typed into code
- Snapshots
- Pull requests from forks, which are off by default
Held until someone who did not write the code reviews it.
In detail
What is in it.
Runs on your Airflow
A component in your Airflow repository tests every labelled pull request. Nothing is installed on the Airflow images.
One build per push
Each push gets one build of the models it affects.
PR Tests page
Every pull request’s stage: not picked up, preparing, running, passed, failed or archived.
Why nothing is happening
A drill-in explains what is waiting, what failed and the coverage.
Commit status
An optional status is posted back to your git server.
Installed by pull request
The test component is installed and upgraded as one self-contained folder, through a pull request.
Good to know. Pull request tests work with GitHub and GitLab, cloud and self-hosted.
Who decides
A person decides. The agent prepares.
The agent has only the permissions of the person it works for, and the approver is recorded.
These wait for a person
- Opening the pull request
- Merging it, in your git server
- Reviewing a held change
- Installing or upgrading the test component
Transcript of the film
A model change looks fine in review. Then it reaches production, and a board report breaks.
With NerveStax, nothing reaches production untested. Every pull request is tested in Airflow before anyone merges it.
Ask for a change. The agent builds it and runs your tests first, and checks the numbers against production.
Then it asks before it opens the pull request.
The moment it opens, Airflow builds the changed models, and everything downstream, in a schema of its own, on real data. Production is read, never written.
Results come back to the pull request and to the PR Tests page: which commit, which models, pass or fail.
And you can see exactly what it touched downstream before you merge.
A person merges it. Your review rules and CI still apply.
Every change, tested before merge. NerveStax.
More of the platform
The other features, each with a film.
See it on your own repository.
Tell us what you run and what is waiting. We will set up a working session on your stack and reply within a working day.