Posts tagged “qa”

An accessibility finding a developer cannot locate never gets fixed. Here are the mistakes that make a11y feedback hard to act on, and how to correct each one.

Dictation is faster for long reproduction steps but wrong for exact values. Here is when to talk through a bug, when to type it, and how to handle Firefox.

How to place numbered pins on a single screenshot so a developer reads your bug report as an ordered checklist, not a scavenger hunt.

Teams switching from Jam.dev to a link-based review make the same handful of errors. Here is what stalls triage and how to correct each one.

Six steps your client can run on the staging site in about ten minutes, capturing stills and dictating notes into one link your developers can act on.

The client cannot reach your staging URL because of basic auth, VPN, or an IP allowlist. Capture the screens instead and send a link they can open.

An agent will happily edit the wrong element if your markdown bug report is vague. Here are the specific mistakes that cause it and the concrete fix for each.

A worked example: the same bug report shown as a published review link for people and as clean markdown for Cline to read and fix.

Markup anchored to a live page drifts or vanishes after a deploy. A cropped still frame records exactly what you saw, so your feedback still makes sense next week.

A step-by-step accessibility pass that ends in a shareable doc: capture the problem screen, name the WCAG issue, point at the spot, and publish.

A code diff tells you what changed, not how it looks. Here are five specific practices for adding screenshots to a pull request review so the author can act on every comment.

A step-by-step procedure for reviewing a staging build and sending issues someone (or an agent) can fix without a follow-up call.

A field-by-field QA bug report template you can copy into any review. Covers what to include, when to trim it, and how to attach the screenshot.

BugHerd's pinned-on-page bug tracker shines on long projects. A no-login review link wins when you just need feedback someone can act on today.

Vague comments, missing screenshots, mixed priorities. The specific feedback mistakes that cost a round trip, with the concrete correction for each.

Diffs hide the things that actually matter in UI work: spacing, hover states, focus rings, mobile layout. Here is how to review a PR on screen and attach the result.

A concrete pre-launch staging review walkthrough: what to check, how to capture it, and how to hand it off so the fixes actually ship before go-live.

IT-blocked extensions stall reviews for weeks. Here's why approval is slow, and a browser-only way to capture and share screen feedback in the meantime.

The precise vocabulary for bug reports a coding agent can fix without follow-up questions. Each term defined, with practical notes on when it matters.