Speak or type
Describe the issue in plain language instead of formatting a ticket manually.
Speak or type the bug. QAL structures the report, captures technical evidence when available, lets you review it, and routes the final issue into the tools your team already uses.
QAL combines natural-language reporting, screenshots, selected element context, failed JavaScript/network evidence, review and issue routing in one QA workflow.
Describe the issue in plain language instead of formatting a ticket manually.
Build Summary, Expected, Actual, Steps, classification and investigation focus.
Check screenshot, selected element, failed JS events and failed network requests when present.
Send the reviewed issue to GitHub, Jira, Linear, GitLab or Azure DevOps.
QAL adds useful technical context without turning every issue into a wall of noise.
Capture the visible page and mark the selected area for a cleaner visual clue.
Include element text, selector, geometry and relevant layout context.
Capture uncaught errors, unhandled promises and resource load failures.
Surface failed fetch/XHR requests and HTTP 4xx/5xx events when available.
The visuals are now sequenced by the real QAL flow, with mobile-friendly crops and no oversized banner first.
QAL sits before the issue tracker: capture the problem, prepare the report, then send it cleanly.
Capture, review and route bugs while testing web products.
A dedicated place to review and manage QAL reports.
Bring QAL into mobile app testing and issue capture.
This public summary reflects the current QAL extension behavior. A dedicated privacy page is included separately so it can later live at /privacy on your domain.
When secure evidence is used, screenshots are compressed before routing and shared through temporary private links rather than a public bucket.
Local report history stores report text and metadata in the browser, not raw screenshot image bytes.
OAuth connection tokens are handled through QAL Cloud; browser access tokens are stored in browser session storage.
If Machine Learning improvements are enabled, QAL may use sanitized report signals and corrections. Raw screenshots, cookies, request/response bodies, authorization headers and OAuth tokens are excluded.
For individual QA professionals.
For small QA teams of up to 3 users.
Public feedback can help other QA professionals understand what using QAL is actually like. Only approved submissions are shown publicly.
Send a message directly from the site. You do not need to open your email app.
Install the extension and turn your next issue into a clean, structured and actionable report.