Skip to main content

​
What types of issues does QA.tech detect?

QA.tech automatically detects issues during test runs. You can export any detected issue to Linear, Jira, or Trello.
  • Failed tests - When a test cannot be completed, QA.tech creates a failed test issue. This often indicates a UX problem or functional issue in your application that needs investigation.
  • Console errors - QA.tech captures JavaScript console errors that occur during test execution. These are typically filed as low-severity issues but can indicate bugs or misconfigurations.
  • Accessibility issues - QA.tech automatically checks for WCAG 2.0, 2.1, and 2.2 violations using axe-core on every page your tests visit.

​
How it works

  • Issues are created automatically when tests fail during execution
  • Same issue across multiple test runs is grouped together using fingerprint-based deduplication
  • Each issue page shows when and where the issue occurred

​
WCAG coverage

  • WCAG 2.0 (Level A, AA, AAA)
  • WCAG 2.1 (Level A, AA)
  • WCAG 2.2 (Level AA)

​
Limitations

Accessibility scanning:
  • Maximum 10 issues captured per test session (see limits)
  • Color contrast not checked (use browser DevTools for this)
  • Content in iframes not scanned
  • Certain rules disabled: region, landmark-one-main
What we don’t detect: Because we interact with your product as a user through a browser:
  • Server-side errors: Use a monitoring tool like Sentry or BugSnag for backend exceptions
  • Network request failures: We log these for debugging but don’t create issues for them
Automatic scanning: Accessibility checks run automatically whenever you execute a test - no setup needed.Schedule regular checks: To get ongoing accessibility monitoring, create a test plan with your test cases and add a schedule (daily, weekly, etc.), or run tests from your CI/CD pipeline.

​
How Issues Are Collected

Issues are automatically detected and created during test runs. You don’t need to manually create or report issues.

​
Automatic Detection

When a test execution completes with a FAILED result, QA.tech automatically:
  1. Creates an issue record for the failed test
  2. Links the issue to the specific test case and run
  3. Groups similar issues together using fingerprint-based deduplication

​
Deduplication

QA.tech uses a fingerprint system to group similar issues together:
  • Each issue has a unique fingerprint based on the test case and project
  • If the same test fails across multiple runs, it creates one issue with multiple occurrences
  • This prevents duplicate issues and helps you track how often a problem occurs

​
When Issues Are Created

  • After test execution: Issues are created automatically when a test finishes with a FAILED result
  • Requires test run: Issues are only created for actual test runs (not during initial test generation)
  • One issue per test case: Each unique test case failure creates one issue, with multiple occurrences tracked over time

​
Finding an Issue

There is no Issues item in the sidebar and no project-wide issues list. Open an issue from a test result. On a test result, the Issues section links to each detected issue. A saved link to one issue still opens that issue: /p/<project>/issues/<issue-id>. The old list address, /p/<project>/issues, redirects to the project home.

​
Issue Page

An issue page shows:
  • Severity and status - How critical the issue is and whether it is active or ignored
  • First seen and last seen - When the issue was first and most recently detected
  • Occurrences - Every time this issue was encountered during test runs, including which test run and URL
  • Help - Guidance on how to fix the issue (accessibility issues include WCAG documentation links)
From the issue page you can mark an active issue as ignored. Ignored issues are not raised again. Revert sets the issue back to active.

​
Export to Issue Trackers

QA.tech integrates with popular issue tracking tools so you can manage bugs in your existing workflow. Issues are not automatically synced - you choose which issues to export.

​
Supported Integrations

​
How to Export an Issue

1

Open the Issue

From a test result, open the issue in the Issues section. A direct link to that issue works the same way.
2

Export to Your Tracker

In the issue detail view, find the Link section at the top. Click the export button for your configured integration:
  • “Create ticket” (Jira) — creates a Jira issue with the qatech label
  • “Create issue” (Linear) — creates a Linear issue in your team
  • “Create Card in Trello” — creates a Trello card in your list
From a test run, you can also export via Send to Jira, Send to Linear, or Send to Trello in the tracer.
If you see “Add Integration” instead of export buttons, you need to configure an integration first. Go to Settings → Integrations in your project to set up Jira, Linear, or Trello.

​
What Gets Exported

When you export an issue, QA.tech sends:
  • Title: Prefixed with the QA.tech issue short ID (e.g. [iss_abc] Login button stays disabled)
  • Description: Summary, test intent, test steps, what went wrong, evaluator notes, evidence (screenshots and console details), and a link back to QA.tech
  • Labels (Jira): qatech for filtering exported tickets
  • Console Details: For console errors, includes the error level, file location, line numbers, and messages
See Jira or Linear for tracker-specific details.
After exporting, the issue detail page shows a direct link to the created ticket, so you can quickly jump to it in Jira, Linear, or Trello.