Connectors

/

Ghost Inspector

/

Reconcile Ghost Inspector failures with GitHub issues
Report
Cross-Connector

Match open GitHub issues to what Ghost Inspector reports now

For development teams whose test-failure issues stay open after tests pass, who want the backlog reconciled by their AI assistant.

Try PopdockAI free
Get a live demo
Reconcile Ghost Inspector failures with GitHub issues
Reconcile our open GitHub issues tagged [Ghost Inspector] with current test results from the last 7 days.
Of 11 open issues, 4 now pass and could be closed, and 2 failing suites have no issue. - Now passing: #212 Checkout suite, passing since 3 October - Still failing: 6 issues, latest result 6 October - Not found: 1 issue names a suite that no longer exists - Unfiled: Search suite and Account settings suite Want the four tables with latest result times?
Ghost Inspector
Sample figures. Your results come from your own account.
github-get-issue
ghost-inspector-get-suite
ghost-inspector-get-suite-result
ghost-inspector-get-test

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Ghost Inspector

Ghost Inspector
Run it on your own Ghost Inspector data.

Connect Ghost Inspector, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Issues stay open after tests pass again

GitHub issues about Ghost Inspector failures stay open long after the tests pass, while new failures go unfiled. Sorting it out means checking every issue against current results and every failing suite against the backlog.

Without PopdockAI

  • Search GitHub for issues about test failures
  • Check each suite and test in Ghost Inspector
  • Look for failing suites with no issue
  • Leave stale issues open

With PopdockAI

  • Open issues with your title marker are read
  • Each is sorted into now passing, still failing or not found
  • Recently failing suites with no open issue are listed
  • Closing and filing are recommended, never done

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Reconcile open GitHub issues about Ghost Inspector failures (titles containing `{title-marker}`, default `[Ghost Inspector]`) against what Ghost Inspector reports now, looking back `{lookback-days}` days (default 7) for failures.

**Step 1: Collect the open issues (GitHub)**

Call `github-get-issue` with `title.contains` set to `{title-marker}` (or `[Ghost Inspector]` if blank) and `status` open. For each issue, pull out the suite name from the title and the test names and test ids from the body.

**Step 2: Check each against Ghost Inspector**

For each issue, call `ghost-inspector-get-suite` with `name.contains` set to the suite name, then `ghost-inspector-get-suite-result` with `suite-id` for its most recent result. Where the body names tests, call `ghost-inspector-get-test` with `id` (or `name.contains`) to read each test's current `passing`.

Sort each issue into one of:

* **Now passing**: the latest suite result and every named test pass. Candidate to close.
* **Still failing**: the latest result still fails.
* **Not found**: the suite or test no longer exists in Ghost Inspector.

**Step 3: Find unfiled failures (Ghost Inspector, then GitHub)**

Call `ghost-inspector-get-suite-result` with `passing` false and `date-created.from` set to `{lookback-days}` days ago. For each distinct suite name that is failing now and has no open issue from Step 1, record it as unfiled.

**Step 4: Report**

Four tables: Now passing (issue number, title, url, latest pass time), Still failing (issue, suite, failing count), Not found (issue, what is missing), Unfiled failures (suite name, suite id, latest failing result id and time).

**Rules & Guidelines:**

* `github-get-issue` is on the github server; the ghost-inspector tools are on the ghost-inspector server.
* This prompt is read-only. Do NOT call `github-update-issue`, `github-add-issue`, `github-add-issue-comment`, `ghost-inspector-execute-suite` or `ghost-inspector-execute-test`. Recommend closing or filing; do not do it.

**Validation:**

* Match suite names exactly once found; if `name.contains` returns several suites, prefer the exact name and list the others under Not found as ambiguous.
* If no issues carry the marker, say so, report only the unfiled failures, and mention that issues filed by hand may use a different title.

Who it's for

One answer, three teams that use it

Developers

Close issues that are already fixed

Issues whose tests now pass are listed with the latest result time, ready to close.

Which open GitHub issues titled [E2E] are for Ghost Inspector tests that pass now?

QA leads

File the failures nobody reported

Suites failing recently with no open issue are listed so you can file them.

Which Ghost Inspector suites failed in the last 14 days with no open GitHub issue?

Engineering managers

Trust the test issue backlog

Four tables show exactly where the backlog and test results disagree.

Reconcile GitHub issues marked [Ghost Inspector] with the last 30 days of results.

How it works

What PopdockAI does when you ask

You give a title marker and a period, and your AI assistant matches the issue backlog to current test results. Ambiguous suite names are listed, not guessed.

01

Ask

You give the issue title marker and a lookback period.

Your AI tool

02

Read

It reads open GitHub issues with that marker and checks each suite and test in Ghost Inspector.

github-get-issue
ghost-inspector-get-suite
ghost-inspector-get-test

03

Find

It lists suites failing recently with no open issue.

ghost-inspector-get-suite-result

04

Report

You get one table per group, with closing and filing recommended, never done.

Your AI tool

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.

get-data

github-get-issue

Returns GitHub issues from a repository. Filter by issue number, title text, state, labels, assignee, author, milestone, and created or updated date range.
get-data

ghost-inspector-get-suite

Returns the test suites defined in Ghost Inspector, with the folder and organization they sit in and the browser, region and start URL their tests run with. Filter by organization, folder, name, browser or region, or fetch a single suite by ID.
get-data

ghost-inspector-get-suite-result

Returns Ghost Inspector suite runs, with the number of passing and failing tests in each, the run timing and the suite they belong to. Filter by suite, date range, pass state, or a minimum count of failing tests.
get-data

ghost-inspector-get-test

Returns the browser tests defined in Ghost Inspector, with the suite they belong to, their schedule and run settings, and whether the last run passed. Filter by suite, name, browser, region, creation date or current pass state, or fetch a single test by its Ghost Inspector ID.
Read only.Nothing in Ghost Inspector Changes

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.

How Popdock AI secures your data

The outcome

An issue backlog that matches reality

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

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.

Try PopdockAI Free
See Documentation