VigilQA Docs

Integrations

VigilQA can push test results to external reporting and issue-tracking platforms. Integrations are configured per product so different teams can route results to different destinations.

ReportPortal

ReportPortal is a test analytics platform that aggregates results across multiple projects and runs. The VigilQA integration pushes each run as a ReportPortal launch after execution completes.

Setup

  1. In ReportPortal, generate an API token from User Profile → API Keys.
  2. Note your ReportPortal instance URL (e.g. https://reportportal.mycompany.com) and the target project name.
  3. In the VigilQA dashboard, go to Settings → Integrations → ReportPortal.
  4. Enter the URL, API token, and project name. Click Save and Test to verify the connection.

Per-product toggle

Once the global ReportPortal connection is saved, each product can independently enable or disable the push via Product Settings → Integrations → ReportPortal. This lets you push results for production-critical products while keeping experimental products out of your reporting dashboard.

What gets pushed

For each completed run, VigilQA creates a launch in ReportPortal with:

  • Launch name set to the product display name
  • Per-test items with pass/fail/skipped status and failure messages
  • Test attributes: domain (web, api, security…), run ID, environment
  • Failure logs attached as log entries so you can read tracebacks directly in ReportPortal

ReportPortal launch attributes map VigilQA domains to RP test suites. If your ReportPortal project uses custom attributes for filtering, add them to the Custom Attributes field in the integration settings.

Troubleshooting

  • Connection test fails — check that the VigilQA server can reach your ReportPortal host on port 443. If ReportPortal is on a private network, ensure network peering or VPN connectivity.
  • 401 Unauthorized — the API token may have expired; regenerate it in ReportPortal and update the integration settings.
  • Launch not appearing — verify the project name matches exactly (case-sensitive) and that the API token has write access to that project.

Bug trackers

The Bug Tracker module auto-creates entries when ResultAnalyzer classifies a failure as a Product Bug. See the Bug Tracker module documentation for Jira, Linear, and GitHub Issues setup.

CI/CD integrations

For triggering runs from GitHub Actions, GitLab CI, and Jenkins, see the CI/CD Integration section.