Sharajdev

Chrome extensions for QA testing

Nine free, focused Chrome extensions that cover the everyday QA loop — designing test cases, recording UI flows, exploring an app, inspecting what you see and filing bugs engineers can actually reproduce.

QA Testing Extensions

Free

QAtalyst

AI Test Case Generator

Turn any feature, user story or requirement into structured test cases — positive, negative, edge and boundary scenarios — in seconds. Stop writing QA test cases by hand.

Add to Chrome Explore QAtalyst →
Free

FlowScribe

UI Test Script Generator

Record clicks, inputs and navigation in the browser and turn them into ready-to-run UI test scripts — no manual selector writing or test boilerplate.

Add to Chrome Explore FlowScribe →
Free

Gotcha

One-Click Bug Reports

File a complete, reproducible bug — screenshot, console, network, auto-recorded repro steps and DOM snapshot — into Linear or Jira. Every report ships with a runnable Playwright regression test.

Add to Chrome Explore Gotcha →
Free

Pathfinder

Autonomous UI Test Exploration

Autonomously explores your web app's UI — mapping screens and flows to surface untested paths and build exploratory UI test coverage without a written script.

Add to Chrome Explore Pathfinder →
Free

LingoAI

Localization (l10n/i18n) QA

Audit the localization quality of any page — untranslated strings, clipped UI, grammar and formatting — with severity, a suggested fix and on-page overlays. Local-first, export to Jira/GitHub.

Add to Chrome Explore LingoAI →
Free

StyleSpy

CSS & State Inspector

Inspect CSS of static, hidden and dynamic elements. Freeze hover/focus states, reveal ghost DOM, track mutations — and copy ready-to-use selectors and XPath for Selenium, Playwright and Cypress.

Add to Chrome Explore StyleSpy →
Free

Hotshot

Exact Screenshot & Element Capture

Capture elements, custom regions, or full scrolling pages with on-page markup, true pixel redaction, and direct export to Jira or Notion. 100% on-device.

Add to Chrome Explore Hotshot →
Free

skiller

Auto Skill Generator for Jira Tickets

Automatically turns your Jira tickets into reusable skills — converting ticket requirements into ready-to-run automation without manual setup.

Add to Chrome Explore skiller →

Built for the people who test in the browser

Most QA work happens in a browser tab: reading a ticket, clicking through a new feature, spotting something off and writing it up. These extensions sit in that tab so you don't have to switch tools for each step. They're aimed at manual testers, QA engineers and SDETs, and at developers who own their own test coverage. Each one does a single job, so you install only what you need, and all of them run in Chrome and other Chromium browsers.

Which one should I use?

How they fit together

A typical sprint looks like this. When a story lands, Jira Compass shows what the ticket is missing, and QAtalyst turns the acceptance criteria into a first draft of test cases. While you test, Pathfinder looks for flows the plan missed, LingoAI covers each locale, and StyleSpy helps you check what the page actually rendered. When something breaks, Gotcha or Hotshot captures the evidence. Once a flow is stable, FlowScribe records it as a UI test so it keeps running in CI.

For help with the test-design step itself, read our guide on writing negative and edge-case test cases. If your testing involves the network layer, see the API testing extensions and the guide to mocking API responses in Chrome. To catch slow pages as well as broken ones, work through the Core Web Vitals debugging checklist.

More collections: API testing extensions · AI developer tools · all extensions

Frequently asked questions

Are these QA extensions free?
Yes — every extension on this page is free to install from the Chrome Web Store.
Do I need to write code to use them?
No. QAtalyst, Gotcha, Pathfinder, LingoAI, StyleSpy and Hotshot need no code at all. FlowScribe and Gotcha produce test scripts you can run, but you don't have to write them yourself.
Do they replace my test management tool or test framework?
No. They produce input for your existing tools: test cases you copy into your test management tool, scripts you add to your suite and bug reports filed into Linear or Jira.
Which browsers do they work in?
Chrome and any Chromium-based browser, including Edge, Brave and Arc.