/
/
Find closed bugs that have no regression test
For project managers who want recently closed Azure DevOps bugs checked against Ghost Inspector tests, by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
Closed bugs come back without a regression test
Nobody checks whether the bugs that were closed ever got a regression test, so the same bugs come back. Doing it means reading recent closed work items and then searching Ghost Inspector for something that covers each one.
Without PopdockAI
- List recently closed bugs in Azure DevOps
- Search Ghost Inspector for a test for each
- Decide by name whether it covers the bug
- See the same bug return a month later
With PopdockAI
- Bugs closed in the window are read
- Ghost Inspector is searched for tests that appear to cover each
- A name match is treated as a hint, not proof
- No coverage is kept apart from could not match, and nothing is created
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** For work items of type `{work-item-type}` (default Bug) in state Closed in project `{project}`, check whether Ghost Inspector has a test that appears to cover each one, and list the ones that have none.
**Step 1: Read the work items (azure-devops)**
Call `azure-devops-get-work-item` with `project` set to `{project}`, `work-item-type` set to `{work-item-type}`, `state` set to Closed and `max-records` 25. Keep `id`, `title`, `area-path` and `changed-date`; use the 25 most recently changed.
**Step 2: Look for a test (ghost-inspector)**
For each work item pick the one or two most distinctive words in its `title` (not generic words such as error, page, fix) and call `ghost-inspector-get-test` with `name.contains` set to each. Also try the last segment of `area-path`. Record any matching test name and its latest `passing` value.
**Step 3: Report**
A table: work item id and title, matching test or "none found", and whether that test is passing. Then a short list of work items with no match, ordered by `changed-date`, as candidates for new regression tests. Say that a name match is a hint, not proof of coverage.
**Rules & Guidelines:**
* Azure DevOps tools (prefix azure-devops-) come from the azure-devops server; Ghost Inspector tools (prefix ghost-inspector-) come from the ghost-inspector server. Both servers must be connected.
* The only link is words in titles. Do not claim coverage that you did not see.
* Do not call any write tool: `ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-add-test-result-comment`, `ghost-inspector-add-suite-result-comment`, `ghost-inspector-accept-screenshot`, or any create, duplicate, cancel or update tool. This prompt only reads.
* Do not create tests or suites.
**Validation:**
* If no work items are returned, say so and stop.
* If a title has no usable keyword, list it as "could not match" and not as "no coverage".Who it's for
One answer, three teams that use it
QA managers
Find gaps in regression coverage
See which closed bugs have no test, so coverage is added before they return.
Which bugs closed in Fabrikam Mobile this month have no Ghost Inspector test?
Project managers
Check fixes are protected
Know that the bugs closed this sprint have tests guarding them.
List bugs closed in the last 14 days in Contoso Platform without regression tests.
Test automation engineers
Plan the next tests to write
Uncovered bugs give you a ready list of tests to add.
Which closed Northwind Commerce bugs from last quarter have no matching Ghost Inspector test?
How it works
What PopdockAI does when you ask
You give a project and a window, and your AI assistant checks each closed bug for a regression test. It only reports and creates nothing.
01
Ask
You give the project and the time window.
02
Read
It reads the bugs closed in that window.
03
Search
It looks in Ghost Inspector for tests that appear to cover each one.
04
Report
You get covered bugs, uncovered bugs and those it could not match.
What PopdockAI provides
The tools behind the answer
Ready made tools for Azure DevOps and one secure connection to your AI tool. No code, no exports.
azure-devops-get-work-item
ghost-inspector-get-test
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
Closed bugs without coverage, listed
Related use cases
More ways to put this data to work
Compare Azure DevOps pipeline runs with Ghost Inspector suites
Ask your AI to compare Azure DevOps pipeline runs with Ghost Inspector suite results and it lists where one is green and the other red.
Learn More
Audit Azure DevOps branch hygiene
Ask your AI to audit a repository and it lists stale, locked and diverged Azure DevOps branches with a suggested action for each. Nothing is deleted or locked.
Learn More
Audit stale Azure DevOps work items
Ask your AI to audit a project and it flags unassigned, untouched and neglected priority 1 work items grouped by area. Nothing is reassigned or closed.
Learn More
Check Azure DevOps pull request readiness
Ask your AI if an Azure DevOps pull request is ready and it checks reviewer votes, comment threads and merge status, then gives a verdict. It never merges or approves.
Learn More
Diagnose failing Azure DevOps builds
Ask your AI to diagnose a failing Azure DevOps pipeline and it finds the first failing run and the commits since the last success, with likely causes ranked.
Learn More
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.