Capability
It runs the change in a real browser.
Where your team already has a preview or staging environment, Moonray AI starts the change up there and works through the affected parts of the product in a real browser. Anything that breaks comes back as a recording with the steps to reproduce it.
What it does
Reading code tells you a lot. Running it tells you more. After the review passes have identified which parts of the product a change touches, we start the change up in an environment you already have and use it, the way a person would: open the page, fill the form, submit it, watch what happens.
Every session is recorded. When something breaks you get the recording, the steps that produced it, and the specific state the product was in at the moment it went wrong. You are not reading an assertion that something might be a problem. You are watching it happen.
How it decides a failure belongs to this change
This is the hard part, and it is where we intend to be the best in the market. A failure in a staging environment is not automatically the fault of the change in front of you. Something may already have been broken.
So we run the same checks against the commit before the change and compare. A failure that reproduces on both is reported as pre-existing, not as a reason to hold this change. A failure that appears only on the new commit is attributed to it. Where the comparison is inconclusive, we say the failure cannot be attributed, rather than guessing.
What it does not touch
Everything runs in isolation against test data. Never against production, never against anything live. Actions that reach outside the system, such as sending emails or taking payments, are blocked at the boundary rather than trusted not to fire.
charge.duplicate
Retry created a second charge of $412.00 on order 40219.
- 1 Open refunds
- 2 Select order 40219
- 3 Retry payment
- ! Duplicate charge created
reproduced 3 of 3, not present on the commit before this change
Questions.
What kind of environment do you need?
Anything the change can be started up in and reached over HTTP: an existing preview environment per pull request, a shared staging environment, or an ephemeral one you already build in CI.
What happens if we do not have one?
You still get the review, the codebase map, the standards check, the ticket check, the blast radius and the test runs. The assessment states that runtime evidence was unavailable, and its confidence reflects that.
Can it reach our production data?
No. Testing runs against test data in an isolated environment, and outbound actions such as email and payments are blocked.
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.