/
/
Rank Ghost Inspector failures by what to fix first
For QA teams after a run of red results who want failures ranked by evidence, not raw counts, by asking their AI assistant.
On this page
Connector
Connect Ghost Inspector, pick your AI tool and paste the prompt.
The problem
Raw failure counts reward tests that run hourly
After a run of red results the team needs to decide what to fix first, but a raw failure count favours tests that run often. Sorting real breakages from blips and new regressions takes a spreadsheet nobody has time for.
Without PopdockAI
- Count failures per test from the results
- Fix whichever test failed most
- Miss the new regression at the end of the week
- Chase old blips that already pass
With PopdockAI
- Failing and passing results give each test a failure rate
- Tests are ranked from always failing to new failures to old blips
- Affected browsers and regions are noted
- At most five next steps are given, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Produce a ranked triage list of the Ghost Inspector tests that failed in the last `{lookback-days}` days (default 7), optionally limited to the suite named `{suite-name}`, and recommend an order of work.
**Step 1: Narrow to a suite if one was given**
If `{suite-name}` is set, call `ghost-inspector-get-suite` with `name.contains` set to it. If more than one suite matches, list the matches and stop. Keep the suite `id`. If `{suite-name}` is empty, skip this step and triage everything.
**Step 2: Collect the failures**
Call `ghost-inspector-get-test-result` with `passing` false, `date-created.from` set to the start of the lookback window, `suite-id` from step 1 if you have one, and `max-records` set high enough to cover the window. If nothing comes back, report that no tests failed in the window and stop.
**Step 3: Collect the successes for the same window**
Call `ghost-inspector-get-test-result` again with the same filters but `passing` true. You need both sets to work out a failure rate rather than a raw count, because a test that runs hourly will always top a raw count.
**Step 4: Rank**
Group both sets by `test-name`. For each test compute runs, failures and failure rate. Rank by this order:
* tests failing on every run in the window, these are broken rather than flaky
* tests with a high failure rate and many runs
* tests that failed once at the end of the window, these may be a new regression
* tests that failed once in the middle and have passed since, lowest priority
Note which browsers and regions each failure occurred in. A test that only fails in one browser or one region is a different problem from one failing everywhere.
**Step 5: Report**
A table of: test name, suite, runs, failures, failure rate, browsers affected, most recent failure. Then a short ranked recommendation of what to investigate first and why, at most five items.
**Rules and guidelines:**
* Read only. Do NOT call `ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-cancel-suite-run` or any create, duplicate or comment tool.
* Do not diagnose individual failures here. Point at them and say which to investigate.
**Validation:**
* If `{suite-name}` matches nothing, say so and offer to run across all suites instead.
* If the result count hits `max-records`, say the window was truncated and the ranking may be incomplete.
Who it's for
One answer, three teams that use it
QA leads
Set the team's priorities
A ranked list and up to five recommendations tell the team what to investigate first.
Triage Ghost Inspector failures from the last 14 days across all suites.
Developers
Spot new regressions
New failures at the end of the window are separated from old blips that already pass.
Which Ghost Inspector tests started failing in the last 3 days in the Search suite?
Test automation engineers
Find browser or region specific failures
Affected browsers and regions are noted, so you can tell environment issues from real bugs.
Rank failing tests in the Mobile web suite this week and note which browsers are affected.
How it works
What PopdockAI does when you ask
You give a period and optionally a suite, and your AI assistant ranks failing tests by evidence. Truncated windows are flagged.
01
Ask
You give a lookback period and optionally a suite.
02
Collect
It gathers failing and passing results so each test gets a failure rate.
03
Rank
It orders tests from always failing to new failures to old blips, noting browsers and regions.
04
Report
You get the ranked list and at most five recommendations, changing nothing.
What PopdockAI provides
The tools behind the answer
Ready made tools for Ghost Inspector and one secure connection to your AI tool. No code, no exports.
ghost-inspector-get-suite
ghost-inspector-get-test-result
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Start on the failures that matter most
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
