Reviews and quality
When a quality run fails — what went wrong and what to do
Every failed quality run says what failed, the likely cause and the evidence for it, the safe next step and who can take it; plus what changed in your application, pipeline template versions, pausing, and usage against your plan.
Quality › Quality Intelligence › your application.
What went wrong
Open a run on the Runs tab. A run that failed, or whose tests failed, shows What went wrong:
| Part | What it says |
|---|---|
| What failed | the step: reading the application, generating, running the tests, creating the repository, the pipeline run |
| Likely cause | for example "The credential lacks a permission", "A secret the pipeline needs is not set", "The test environment could not be reached", "A test could not find what it looks for" — with how sure Yavaren is |
| Evidence | the lines that led to it, with tokens and passwords removed |
| Next step | the safe thing to do; Yavaren never suggests widening a token, skipping tests or using production |
| Who can fix it | you, an admin of your organisation, your CI or repository host's administrator, or Yavaren support |
When Yavaren cannot tell, it says the cause is unknown. Give support the reference shown under the diagnosis.
What changed
The Changes tab compares the latest analysis with the one before:
- pages, forms and buttons
- API endpoints
- tables
- sign-in
- dependencies
- the pipeline template
It lists the tests each change affects, and tests of something that no longer exists (for you to retire; Yavaren never deletes them). Propose the update as a draft pull request generates the update once per change, after the updated strategy is approved by a person. It goes to where your automation lives; Yavaren never merges.
Pipeline template
Each generated pipeline file starts with a line naming its template and version. A newer version is proposed as a draft pull request. A pipeline file you changed is kept, and the new version is offered next to it.
Pause
On Environment, an admin can pause new quality work for an application (with a reason). Nothing is deleted; Resume restarts it.
Usage this month
At the bottom of the page you see the month so far:
- runs, applications and separate repositories against your plan, with when the count resets
- browser minutes
- pipeline runs: their minutes are measured and billed by your CI provider, not by Yavaren
Quality Intelligence calls no AI model.