Skip to main content

​
Getting in touch

Email

info@fulgic.com

Report a bug from the app

The bug icon in the dashboard navigation opens a form that captures the context for us.
The in-app report is the better option when something went wrong in a run. It attaches the page you were on, the latest run id, the build versions, your viewport and the timestamp automatically, so you only have to describe what you expected.

​
What to include

For a run that behaved wrongly, the run id is worth more than a paragraph of description. From it we can see every step, every screenshot, the state read off each element, and the console and network activity. Then, in one or two sentences:
  • what you expected
  • what happened instead
  • whether the screenshot agrees with the report
If a report blamed your site and the screenshot disagrees, that is a defect in Testorim and we treat it as one. Send the run id.

​
Before you write

Most issues have a named cause on the failed step. Worth two minutes first:

Debugging a failed run

Read the cause, then the evidence.

Common issues

Refusals, logins, addresses, seats.

Browser failures

Error statuses, dialogs, downloads, timeouts.

Reliability

Why a test is flaky and what to change.

​
Sharing a run with someone outside your workspace

Use a share link from the run page. It is revocable, can be given an expiry, and the page it serves has credentials, environment headers, browser storage state and console/network detail stripped.

​
Security

If you believe you have found a security issue, email info@fulgic.com with the details and please do not open it anywhere public first. Terms · Privacy