Robotesta

Support

Help with connecting your tools to Robotesta and with what you see in the app.

Contact us

Email sam@robotesta.ai. To help us answer quickly, tell us:

  • the name of your organization in Robotesta;
  • the tool involved, for example GitHub or Jira;
  • what you did and what you see, with the Request ID if the screen shows one.

Never send a password, token or API key by email. We will never ask you for one.

For questions about your data, see our Privacy policy.

Connect a tool

Owners and admins connect tools. Members and viewers see the tools that were shared with their projects.

  1. In Robotesta, open your organization and choose Integrations.
  2. Pick the tool and choose Connect. Robotesta sends you to the tool to approve its access; for some tools you paste a token or key instead.
  3. Back in Robotesta, choose what to read (repositories, projects, spaces or teams) and the Robotesta project each one feeds. Choosing a project also shares that tool’s data with the project’s members and viewers.
  4. The first import runs in the background. Open Sources to follow it; you can leave the page while it runs.

If the tool sends you back with an error, the page says why. If it keeps happening, contact us.

A connection says “Expired” or “Needs reconnection”

The tool no longer accepts Robotesta’s access. The access may have expired or been revoked in the tool, or the person who approved it may have lost access there. Robotesta stops reading that tool until access is renewed. Nothing already collected is lost.

To fix it, an owner or admin opens the tool from Sources and chooses Reauthorize or Reconnect, then approves access again in the tool. For a tool connected with a pasted token or key, choose Replace token (or Replace key) and paste a new one. If Robotesta says reauthorization is not available for that tool yet, contact us.

An import says “Partial” or “Imported with gaps”

Robotesta marks what it collected as partial when it could not read everything. It never counts a partial item as complete. Common reasons:

  • The run stopped before it finished: someone stopped it, it reached the limit of a single run, or the tool limited how many requests Robotesta could make.
  • The tool refused some items, for example because Robotesta’s access does not cover them.
  • Something was over an import limit. Code import reads up to 300 source files of up to 256 KB each per repository, and test reports, screenshots and videos have size limits too.
  • A file the tool pointed to could not be read, for example a GitHub Actions artifact that had expired.

The tool’s page in Sources says why, under Details. Running the import again picks up where it stopped, and nothing already saved is lost. A partial item becomes complete once a later read collects everything.

Disconnect a tool

Owners and admins can disconnect a tool: open it from Sources, then Settings and actions, then Disconnect. Disconnecting:

  • stops all reading from that tool at once;
  • destroys the access tokens Robotesta stored for it, and asks Slack and Sentry to remove the access you approved there;
  • erases the raw copies Robotesta kept from that tool;
  • keeps the records already collected, so your history stays readable.

A disconnected connection cannot be turned back on. To use the tool again, connect it from Integrations. To stop reading only one repository, project or space, stop it on the tool’s page instead. To have collected records deleted, contact us.

Remove Robotesta from a tool

Some tools keep Robotesta listed until you remove it on their side as well:

GitHub
Disconnecting does not uninstall the Robotesta GitHub App. To remove it, open the settings of the GitHub organization or account where it is installed, go to GitHub Apps (for a personal account: Applications, then Installed GitHub Apps), choose Configure next to Robotesta, then Uninstall. When the App is uninstalled, Robotesta marks the connection as disconnected.
Jira and Confluence
Atlassian gives Robotesta no way to revoke its own access, so disconnecting destroys only the tokens Robotesta stored. To remove the access itself, open your Atlassian account settings, go to Connected apps, and remove Robotesta.
Slack
Disconnecting asks Slack to revoke Robotesta’s access. To remove the app itself, open your workspace’s app management in Slack, choose Robotesta, then Remove app. When the app is removed, Robotesta marks the connection as disconnected.
Sentry
Disconnecting asks Sentry to uninstall Robotesta from your Sentry organization. If Sentry still lists it, open Settings, then Integrations, then Robotesta, and choose Uninstall. If you connected with an integration token, delete that token in Sentry as well: Sentry does not let Robotesta remove it.

Which tools you can connect

The Integrations page lists every tool Robotesta supports, in three groups:

  • Connected: the tools your organization has connected.
  • Available: tools you can connect now. Their connector is certified and Robotesta can reach the tool.
  • Coming soon (shown as “Not available yet” on some pages): tools whose connector is not certified yet, or that this version of Robotesta cannot reach yet. They cannot be connected until then, and the page says why.

Which tools are available changes as connectors are certified, so the Integrations page is always the current list.