/
/
Smoke test every finished deploy with Ghost Inspector
For developers who want the smoke suite run only after a GitHub build truly passes, by asking their AI assistant.
On this page
Connector
Connect GitHub, pick your AI tool and paste the prompt.
The problem
Smoke tests run against half finished deploys
After a GitHub Actions deploy, someone should run the Ghost Inspector smoke suite, but first they need to know the build passed. Testing a half finished or failed deploy wastes runs and sends people chasing the wrong problem.
Without PopdockAI
- Watch the deploy workflow until it ends
- Check it passed
- Start the smoke suite by hand
- Chase failures from a broken deploy
With PopdockAI
- It stops if the latest run is still running or failed
- You see which run and suite will be tested
- A mismatched start URL gets a warning before you confirm
- The suite runs once, with failing tests named and a verdict
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** After the latest run of the GitHub workflow `{workflow-name}` (on branch `{branch}`, or any branch if blank), run the Ghost Inspector suite `{suite-id}` and report whether the deployed change passes.
**Step 1: Check the build (GitHub)**
Call `github-get-workflow-run` with `name` set to `{workflow-name}`, plus `branch` set to `{branch}` if given, and take the most recent run by `created-date`.
* If no run is found, report that and stop.
* If its `status` is not completed, report that it is still running and stop. Do not smoke test an unfinished deploy.
* If its `conclusion` is not success, report the run's conclusion and url and stop without running the suite.
**Step 2: Confirm the suite (Ghost Inspector)**
Call `ghost-inspector-get-suite` with `id` set to `{suite-id}`. If it is not found, stop. Tell the user which workflow run (run number, sha, branch) and which suite (name, test count, start url) you are about to run, and wait for confirmation.
**Step 3: Run it (Ghost Inspector)**
Call `ghost-inspector-execute-suite` with `suite-id` set to `{suite-id}`. Do not set `immediate`, so the call returns the result.
If the suite fails, call `ghost-inspector-get-test-result` with `suite-id` set to `{suite-id}`, `passing` false and `date-created.from` set to when you started the run, to name the failing tests.
**Step 4: Report**
* The workflow run: name, run number, branch, short sha, commit message and url.
* The suite: name, pass or fail, execution time, and the failing tests by name if any.
* One line verdict: the change at that sha passes or fails the smoke suite.
**Rules & Guidelines:**
* `github-get-workflow-run` is on the github server; the ghost-inspector tools are on the ghost-inspector server.
* `ghost-inspector-execute-suite` is the only write, called once, after confirmation.
* Do NOT call `github-rerun-workflow-run`, `github-cancel-workflow-run`, `github-add-issue` or `ghost-inspector-cancel-suite-run`. If the user wants an issue filed for a failure, say so and let them ask.
**Validation:**
* If the suite's start url does not look like the environment the workflow deploys to, warn the user before running and let them decide.
* If the execute call returns without a pass state, report the result id and tell the user the run is still in progress.Who it's for
One answer, three teams that use it
Developers
Test your deploy, not a broken one
The smoke suite runs only after the workflow has passed, so failures are real.
Run the Smoke suite in Ghost Inspector against the latest Deploy preview run on my branch in fabrikam/app.
QA engineers
Get a clear pass or fail per commit
A one line verdict says whether the deployed commit passes the smoke suite.
Has the latest Deploy staging run on main passed? If so, run the Staging smoke suite.
Release managers
Check production after release
Warnings on a mismatched start URL stop you testing the wrong environment.
Smoke test the latest Deploy production run in contoso/web with the Production smoke suite.
How it works
What PopdockAI does when you ask
You name the workflow, optionally a branch, and the suite, and your AI assistant checks the deploy finished first. The suite runs only after you confirm.
01
Ask
You name the workflow, optionally a branch, and the suite.
02
Check
It stops if the latest GitHub run is still running or failed.
03
Confirm
It shows the run and suite, warns on a mismatched start URL, and waits for your yes.
04
Run
It runs the suite once and reports which tests failed.
What PopdockAI provides
The tools behind the answer
Ready made tools for GitHub and one secure connection to your AI tool. No code, no exports.
github-get-workflow-run
ghost-inspector-get-suite
ghost-inspector-execute-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
A smoke test for every finished deploy
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)
