Docs

Bug Tracker Integration

Overview

RobusTest supports integration with popular bug tracking systems, enabling you to log bugs directly from test sessions without switching tools. When a bug is created, RobusTest automatically includes device details, screenshots, and test context.

Benefits:

  • In-Session Reporting: Create bugs without leaving your test session
  • Automatic Context: Device, OS, app version, and screenshots attached automatically
  • Streamlined Workflow: Link bugs directly to the project and test session

Supported Bug Tracking Systems

Bug Tracker Notes
JIRA Full integration — create and assign issues with custom fields
Redmine, Assembla, Asana, Bugzilla Selectable from the Admin Console dropdown; backend integration is in development

Setting Up JIRA Integration

Step 1: Create the JIRA Configuration in Admin Console

  1. Go to the Admin Console → Bug Tracker (or navigate to /admin/bugtracker).
  2. Click the + button to add a new configuration.
  3. Fill in the required fields:
    • Name — a label for this configuration
    • JIRA Server URL — the base URL of your JIRA instance
    • JIRA Username
    • JIRA API Token
  4. Click Save. RobusTest validates the credentials and fetches the list of JIRA projects for your instance.
  1. Go to the Project Dashboard for the project you want to connect.
  2. Open the Settings tab.
  3. In the Bug Tracker dropdown, select the JIRA configuration you created.
  4. Save the settings.

Project Created! Your project is now linked to JIRA. Team members can create JIRA issues directly during manual or automation test sessions.

Logging a Bug During Testing

Once a project is linked to a bug tracker, the Log Bug button is available in the vertical menu of any manual test session.

When logging a bug, you can specify:

  • Assignee and reporter
  • Issue type
  • Summary and description
  • Attachments: device log, ANR log, screenshots

Automatically included in every bug report:

  • Screenshot of the current app state
  • Device model and OS version
  • App version and build details
  • Test session ID and timestamp

Best Practices

  • Map your project early: Link the bug tracker to your project before testing starts so the team can log bugs immediately
  • Use descriptive summaries: Include a clear one-line description — RobusTest pre-fills some fields but a good summary saves triage time
  • Attach logs for crashes: Always include the ANR log or device log when reporting a crash