/
/
Find the buggy pages your tests do not cover
For QA and development teams who want to know which BugHerd hot spots have no Ghost Inspector test, just by asking their AI assistant.
On this page
Connector
Connect BugHerd, pick your AI tool and paste the prompt.
The problem
Test coverage follows memory, not where bugs land
Deciding which pages to automate next usually comes down to memory. Doing it properly means grouping months of BugHerd bugs by page and matching them against every Ghost Inspector test URL, cleaned up so they actually match.
Without PopdockAI
- Export months of BugHerd bugs and group them by page
- Collect every Ghost Inspector test start URL
- Clean up www, slashes and query strings to match
- Pick pages to automate from memory instead
With PopdockAI
- Bug reports are counted per page across tasks, archive and feedback
- Pages are matched to test start URLs by host and path
- Untested pages are ranked by report count
- Read-only, with a note on how coverage is counted
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** List the pages of the website tracked by the BugHerd project `{project-name}` that drew bug reports in the last `{lookback-days}` days (default 90) but have no Ghost Inspector test, ranked by how much they break.
**Step 1: Count bugs per page**
Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks`, `bugherd-get-archived-tasks` and `bugherd-get-feedback` with `project-id`, `created.from` set to the start of the period and `max-records` 500. Group by page (normalised as below) and count reports and critical or important ones.
**Step 2: Collect tested pages**
Call `ghost-inspector-get-test` with `max-records` 500. Keep each test's start-url. Match pages by URL: compare host and path, ignoring the scheme, a leading "www.", a trailing slash, the query string and the fragment. A BugHerd project matches a Ghost Inspector suite when the suite start-url is on the project development-url host or one of its sites.
**Step 3: Report**
A table of untested pages ordered by critical-or-important count, then total count: page, reports, critical or important, most recent report, example task numbers. Then a short list of tested pages that still drew several reports, since their tests may not check the right thing.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named ghost-inspector-... are on the ghost-inspector MCP server. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any Ghost Inspector tool that runs, changes or comments (`ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-add-test-result-comment`, `ghost-inspector-add-suite-result-comment`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-duplicate-test`, `ghost-inspector-duplicate-suite`, `ghost-inspector-accept-screenshot`, `ghost-inspector-cancel-test-run`, `ghost-inspector-cancel-suite-run`, `ghost-inspector-create-suite`, `ghost-inspector-create-folder`, `ghost-inspector-update-folder`, `ghost-inspector-create-data-source`, `ghost-inspector-update-data-source`).
* Tests can move through several pages; a test counts only for its start-url here, so say that coverage may be understated.
**Validation:**
* If no task has a page, say so and stop.Who it's for
One answer, three teams that use it
QA automation engineers
Write the tests that matter most
Start new tests on the pages that draw the most bugs and have no coverage yet.
Which Contoso Portal pages get the most BugHerd bugs but have no Ghost Inspector test?
QA leads
Justify where testing time goes
Back your automation plan with real bug counts per page.
Rank the untested pages on Northwind Traders by BugHerd reports over the last 180 days.
Web developers
Find tested pages that still break
See pages that have a test but keep drawing bugs, so you can strengthen the test.
Which pages on Fabrikam Shop have Ghost Inspector tests but still get several BugHerd bugs?
How it works
What PopdockAI does when you ask
You name the BugHerd project and your AI assistant compares where bugs land with what your Ghost Inspector tests cover. It only reads both tools.
01
Ask
You name the BugHerd project and, optionally, how many days to look back.
02
Count
It groups BugHerd tasks, archived tasks and feedback by page and counts the serious ones.
03
Match
It compares those pages with the start URL of every Ghost Inspector test.
04
Report
It ranks untested pages and lists tested pages that still draw bugs.
What PopdockAI provides
The tools behind the answer
Ready made tools for BugHerd and one secure connection to your AI tool. No code, no exports.
bugherd-get-projects
bugherd-get-tasks
bugherd-get-archived-tasks
bugherd-get-feedback
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
A ranked list of pages to automate next
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)
