Know what changes, test what matters, release with proof
Every vendor release and internal change takes the same path: Detect, Assess, Automate, Assure. Release Intelligence finds what changed, the Qventis Engine runs only the test delta in plain English on any screen, and a named person signs a decision backed by evidence.
- Release intelligence built in
- Traced to the step
- Evidence you can defend
How a release moves through Qventis One
Every change, read as it publishes
Release Intelligence reads each vendor's own release content as soon as it is published, preview releases included, and lists it in the Release Feed.
See Release Intelligence- What's New notes and feature summaries
- Opt-in and delivered enabled notices
- API specs and deprecations
- Each vendor's Release Train in one view
Impact traced to the step, not just the module
The App Model maps every changed feature to your modules, process steps and tests, then scores it by transparent rules. Not an AI guess.
See the App Model- Feature impact score: low, medium, high or critical
- Step traceability to the expected result
- Handoffs across business process chains
- Customization exposure for your extensions and roles
Only the tests the change needs
The Qventis Engine builds the test delta and runs it in plain English across eight engines, with zero AI tokens at run time.
See the Qventis Engine- Test delta: impacted, new, retire and unchanged
- Test Selector plans such as "SOX audit evidence"
- Functional, performance, security and more from one model
- Desktop, terminal, web and API steps in one chain
A signed decision per cohort
Quality View rolls results up to cohort readiness, with evidence for every check and a named person who signs.
See Quality View- Release acceptance: accept, accept with actions or hold
- Every number labeled observed, derived or estimated
- Retirements and desupports in the platform risk register
- Agents run tests, people approve releases
Five execution waves, in order of risk
The test delta runs in a fixed order, so the failures that matter most surface first.
- BlockersSign-in, roles and the paths that stop everything else
- End-to-end chainsBusiness process chains across every handoff
- Impacted regressionTests the change touches, ranked by impact score
- New capability and opt-inNew features and opt-in decisions before you switch them on
- Smoke the restA quick pass over everything unchanged
Questions
Can an agent approve a release?
No. Agents can find and run impacted tests, but a named person records go or no-go.
Does this cover our own changes too?
Yes. Configuration and code changes run through the same model and waves as vendor releases.
Does this work with our CI?
Yes. The CLI runs in any pipeline and publishes JUnit XML.
See one release reach a signed go or no-go
Bring your next vendor release. We take it from Detect to Assure with you.