Do not infer the interface. Run it.
A green unit suite can still hide a broken journey. Nova runs the changed application in a real browser, then returns visible evidence for review.
One changed journey, checked end to end.
Nova uses the ticket, change and acceptance criteria to start the application in the project environment and run the relevant browser journey.
The result is not “looks good.” It is a list of named checks with pass, fail or blocked status, plus screenshots and the relevant observations.
That evidence joins the tests and Nova’s summary, where a reviewer can inspect it before the branch is published.
- Start the application environment
Use the project environment and the real services the journey needs.
- Open the journey browser
Navigate with the browser tool and observe the rendered interface rather than inferring from source.
- Check the contract verify
Run named checks against visible state, interaction and expected outcomes.
- Capture evidence evidence
Return structured results and screenshots with the code change.
- Stop cleanly done
Close the browser and application lifecycle without leaving an orphaned process.
Browser evidence is part of the engineering result.
Same environment
The browser sees the application produced by the checked-out change, not a disconnected hosted preview with unknown state.
Same body of work
Acceptance criteria, code changes, tests, browser checks and screenshots stay together rather than becoming separate chat transcripts.
Focused check
Nova runs the named journey and returns structured evidence without receiving broader access than the work requires.
Choose journeys with an observable answer.
Bring one journey your unit tests do not prove.
We will define the visible checks, run them against the changed application and show exactly what evidence Nova returns.