Skip to main content

Getting in touch

Report a bug from the app

Help in the app header → Report a bug 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, the timestamp and the tab’s recent errors automatically, so you only have to describe what you expected. You can add up to three screenshots. Help → Send feedback is for anything else you want to tell us, and each report in the app asks How was this run? Missing a feature? Help → Request a feature opens the shared feature-request board, where you can ask for it or vote for a request someone already made.

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