Capability
It runs your tests, then writes the ones you are missing.
Moonray AI runs your own test suite against the change, focused on the areas the change actually affects rather than running everything and burying the result. It then identifies the parts of the change your suite never touches and writes tests for those gaps.
What it does
Running the whole suite on every change produces a number that nobody reads. We use the blast radius to select the tests that actually exercise the changed behaviour, run those, and report the result against the specific part of the change it relates to.
Then the more useful half: the parts of the change nothing tested. That is almost always where the risk is, because it is the part nobody thought about. We write tests for those gaps and attach them for you to accept or reject.
Ran
214 passed, 0 failed, 1,388 skipped as unaffected
Not covered by your suite
refunds.go: webhook replay branch
idempotency.go: expiry boundary
Two tests written for those branches and attached to the pull request. They are a proposal. Nothing enters your repository without a person accepting it.
Questions.
Do you commit the tests you write?
No. They are attached as a proposal. Nothing enters your repository without a person accepting it.
Where do the tests run?
In an isolated environment against test data, never against anything live.
See it on your own pull requests.
We install on one repository, let Moonray AI assess the next changes your team opens, and go through what it found with you. If the position is not better than what you have now, you will know within a week.
Nothing to host. Reviews begin on the next pull request opened.