Use cases
Where bugs hide when more than one person is involved.
Each case below shows the problem, the ghosts that take part and what the test proves. They are the kinds of checks the product runs today in its synthetic labs.
Example tests
- 01
Authentication and sign-in
Crowd, 2 ghostsThe problem
Two people sign in at nearly the same time and one of them lands in the other person's account or dashboard.
Ghosts
- Member A
- Member B
The test verifies
- Each person reaches their own dashboard
- The name and data on screen belong to the signed-in person
- 02
Roles and permissions
Crowd, 2 to 5 ghostsThe problem
The menu hides the admin page from editors, but typing the address or calling the API still works.
Ghosts
- Administrator
- Editor
- Anonymous
The test verifies
- The administrator can open the page
- The editor is refused in the interface and by the server
- An anonymous visitor is sent to sign in
- 03
Forms and validation
Single GhostThe problem
A support request is sent without a required email. The validation message appears and every other answer is cleared.
Ghosts
- Visitor
The test verifies
- A clear message names the missing field
- Other answers are kept
- The completed form submits once
- 04
Search and filtering
Single GhostThe problem
Someone searches tasks for "report" and filters to open tasks only. A completed task is still in the results.
Ghosts
- Member
The test verifies
- Results match the search term
- The filter removes completed tasks
- Clearing the filter restores the list
- 06
Multi-user workflows and revocation
Company or crowdThe problem
An owner shares a record, then revokes access. The viewer, still signed in, opens the record and it loads.
Ghosts
- Owner
- Viewer
The test verifies
- The viewer can read while shared
- Access ends when revoked, in an open session too
- The owner's dashboard reflects the change
- 07
Regression after code changes
Saved checkThe problem
Your coding assistant refactors the data layer. A status bug you fixed last month quietly comes back.
Ghosts
- Editor
- Administrator
The test verifies
- Every check that passed in the approved baseline still passes
- A returning failure is reported as a new regression
- The CLI exits 1 so CI can stop the release
Kinds of software
Any web app where people have different jobs.
Ghost Company is not tied to one industry. If your app has users, roles or shared data, there is a question the ghosts can ask.
| If you build | The ghosts might ask |
|---|---|
| SaaS products and developer tools | Does a new team member see only their own workspace? |
| Websites and portals | Does a signed-out visitor stay out of account pages? |
| Internal business applications | Can a request be approved by someone who also submitted it? |
| Dashboards and admin systems | Do filters and totals agree with the records behind them? |
| Collaborative and community apps | Does an edit by one member reach everyone else? |
| Booking and management software | Can two people book the last slot at the same time? |
| Education and publishing | Do students see grades only after a teacher publishes them? |
| Other interactive web experiences | Does the journey survive back buttons and double clicks? |
Development situations
When to call the ghosts.
- After an AI assistant changes code
- Large generated diffs touch more than you read. A saved check covers the journeys you care about.
- Before a release
- Run the checks against the build you are about to ship and require the lab to report its revision.
- After touching auth or roles
- Permission bugs are rarely visible to the person who wrote the change. Ghosts with other roles see them.
- On pull requests, in CI
- Use the reusable GitHub Actions workflow on an isolated runner and fail the job on a regression.
Have a case we did not list?
Tell us about your app in the early access form. The kind of app and workflow you describe shapes who we invite first.