QALens.AI
Create account

Stop guessing what to test.

Paste a diff or a screenshot — QALens turns any change into a prioritised QA checklist with risks flagged.

Try instantly

Not a ChatGPT prompt — understands repo context and prioritises by real-world bug patterns.

Analyze a change

What changed?

3 free analyses left

Describe what changed, what broke, or what needs testing.
Upload a screenshot or add any details — we’ll turn it into a clear summary.

Not sure what to write? Try:

Describe the issue:

  • “Promo code is not applied at checkout”
  • “Checkout button does nothing after update”

Or upload:

  • A screenshot of a UI bug or new feature
0 / 3,000 characters

Example checklist

Example output

Sample of what QALens generates

Input type

Generated from pull request changes

PR diff
src/checkout/address.ts
+if (!guestSession) redirectToLogin()
+await cart.preserveOnAddressChange()
−cart.clear(); redirectToCheckout()
+paymentToken.revalidate(address)
Shipping address
123 Main St
✦ Validation fires on submit, not on blur
QA-418 In Review Payments
Guest users can update shipping address before payment confirmation
QA checklist High risk
Confidence
Medium confidence
Auth flow and payment idempotency touched in the same change
Recommended tests
  • ✓Idempotency key blocks duplicate charge on retry of a timed-out payment request
  • ✓Cart state survives guest-session refresh during the address mutation
  • ✓Payment token re-validation runs before the next /charge call
What you might miss
  • ⚠Race between concurrent address PUT and session refresh leaves stale token
  • ⚠409 idempotency response not surfaced to the client retry path
Why this matters
Address mutation invalidates the cached payment token. Without re-validation, a retried request can charge an old address — a backend regression unit tests won't catch.
QA checklist Medium risk
Confidence
High confidence
Inline error state visible in the captured viewport
Recommended tests
  • ✓Inline field error renders at 320px viewport without overflow or clipping
  • ✓Error text meets WCAG 1.4.3 contrast (≥4.5:1) against the form background
  • ✓Validation status announced via aria-live="polite" on screen readers
What you might miss
  • ⚠Keyboard tab order skips the warning icon — error isn't reachable via Tab
  • ⚠Submit button touch target below 44×44px on iOS Safari portrait
Why this matters
Form errors without an aria-live region are invisible to assistive tech — a WCAG 1.3.1 audit-flag risk that quietly drops accessibility-bound users from checkout.
QA checklist High risk
Confidence
Medium confidence
Acceptance criteria leave session-expiry edge case open
Recommended tests
  • ✓All four acceptance criteria verified end-to-end on staging before merge
  • ✓Analytics event "address_updated" fires exactly once per confirmed edit
  • ✓Existing promo-code discount persists across the address-change flow
What you might miss
  • ⚠Mid-edit session expiry — no recovery workflow defined in the ticket
  • ⚠Concurrent edits from two browser tabs not covered by the business rules
Why this matters
Acceptance criteria cover the happy path but skip session-expiry handling — leaves a real workflow risk for guest-checkout abandonment that won't surface in feature tests.
↑ 6 checks · backend logic + idempotency Paste a diff to analyse your own change

Find hidden QA risks

Turn vague product changes into concrete regression and edge-case checks.

Save checklists

Registered users can save analyses and build a reusable QA knowledge base.

Connect delivery tools

Connect Bitbucket and Jira to analyze real pull requests automatically.

How it works

From change to checklist in seconds.

No setup. Just paste your change and get a checklist.

01

Know what to test instantly

From any change — PR, screenshot, or description.

02

Catch risks and missing scenarios

Get a focused QA checklist with what actually matters.

03

Run it on real PRs automatically

Connect your tools and analyze changes continuously.

Trust & Privacy

Built to be safe on real code.

Your code is processed in real-time and routed through verified Western providers — never stored, never used for training.

Code processed in real-time

Never stored on our servers after the analysis completes.

Western providers only

Anthropic, Gemini, and OpenAI — all with API-tier no-training guarantees.

Multi-model verification

50+ verified Western models in active rotation, with automatic fallback if a response is invalid or low-confidence.

EU-based, GDPR-compliant

Hosted in Cyprus. EU privacy rules apply by default.

See our data policy
FAQ

Quick answers

Everything you need to know before generating your first QA checklist.

Do users need to sign up first?

No. Anonymous users get 3 free analyses before seeing the registration prompt.

What happens after the free limit?

Further analysis is blocked and the user is prompted to create a free account.

Can QALens connect to Bitbucket and Jira?

Yes. Integrations are positioned as account benefits for registered users.

What happens if I cancel my Team subscription?

Your team workspace remains accessible for 30 days as a grace period. After 30 days the workspace is archived. Resubscribe within the grace window to reactivate.

Can I leave a team I own?

Not directly. Team owners delete the team from Settings to exit. Ownership transfer is on our roadmap — vote for it on /app/feature-requests/roadmap if you'd like it prioritised.

Free to start

Start with 3 free QA analyses.

Get instant value, then create a free account when you're ready to save and connect your workflow.

Try QALens now

No credit card. Sign up in 30 seconds.