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
- Scans run automatically during test execution (on page load, after navigation, after clicks)
- Issues appear in the dashboard with the exact URL, HTML element, and WCAG documentation
- Same issue across multiple test runs is grouped together
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
- 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.
Issues Dashboard
Filtering Issues
Use filters to find specific issues:| Filter | Options |
|---|---|
| Severity | Minor, Major, Critical |
| Type | Accessibility, Console, Failed Test, Hosting |
| Status | Active, Ignored, Resolved (by default, only Active issues are shown) |
Viewing Issue Details
Click on any issue to see:- Severity and Status - How critical the issue is and its current state
- First/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 Information - Guidance on how to fix the issue (accessibility issues include WCAG documentation links)
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
Navigate to Issues
Click Issues in the sidebar to see all detected issues for your project.
2
Find Your Issue
Use filters to narrow down by severity, type, or status. Search for specific issues by title.
3
Open Issue Details
Click on an issue to view its full details, occurrences, and help information.
4
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 Issue in Jira” - Creates a Jira issue with
qatechlabel - “Create Issue in Linear” - Creates a Linear issue in your team
- “Create Card in Trello” - Creates a Trello card in your list
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: The issue title from QA.tech
- Description: Issue type, first seen date, full description, and help hints
- Link: Direct URL back to the issue in QA.tech for easy reference
- Console Details: For console errors, includes the error level, file location, and messages