Pocket QA
3 ratings
)Overview
Record & replay web tests with asserts, branching, variables and CSV data; API & SQL tests, DB rollback, Selenium/Playwright export
Pocket QA is a no-code test recorder for Chrome. Record your clicks and typing on any website, replay them as automated web tests, and get a clear verdict for every run: Passed, Failed, Test broken or Stopped. When something goes wrong, one click turns the run into a ready-to-paste bug report with steps and a screenshot. Built for manual testers, QA engineers, developers and product teams who want regression testing without setting up a framework. There is nothing to install beyond the extension, no scripts to maintain and no coding required. When you do need code, export any scenario as a ready-to-run test script. A built-in API tester checks the requests behind the page, and SQL and database tools cover the data underneath. ▸ MAIN FEATURES • Record and replay UI tests on any website, without writing code • Assertions with a clear Passed / Failed verdict and one-click bug reports • Conditions, Switch branching and variables for real-world flows • Data-driven runs from a CSV file, with results in Excel, HTML or ZIP • API testing with checks, environments and cURL paste • Export scenarios as test code in five formats • Full-page, scrolling and element screenshots with a built-in image editor • SQL test case designer and database rollback ▸ RECORD AND REPLAY IN SECONDS • Press Start Recording, use the page as usual, press Stop: your clicks and inputs become a saved test scenario • Replay one scenario, run several in sequence, loop N times, or schedule a run for later (once or every day) • While a test plays, a small panel on the page shows the scenario, the current step and the progress, with a Stop button • Playback works inside iframes and continues where it left off after the page reloads • Organise scenarios in folders; rename, duplicate and reorder steps by drag and drop, with undo / redo • Add a step anywhere: hover between two steps and press +; a dashed line shows exactly where it will go • Copy a Switch or a Condition together with the steps inside it, and paste it into any scenario, even an empty one ▸ 17 ACTION TYPES • Click, type, hover, drag and drop, and native dropdowns, including choosing an item by position or at random, even in long virtualised lists • Navigate to a URL, wait, or run your own JavaScript • Upload files into file inputs and drag-and-drop zones • Read text, values or attributes from the page into variables • Take screenshots of the viewport, the full page or a single element during a run • Conditions, assertions and Switch branching (see below) • Find elements by CSS, XPath, ID, name or text. Pick an element straight from the page, and preview which element a selector finds: you see at once if it is missing, hidden or matches more than one • Optional strict mode: a click fails when its element is disabled, hidden or covered, just as a real user would get stuck ▸ BRANCHING, CONDITIONS AND VARIABLES • 12 built-in checks: element exists / does not exist / visible / hidden, text or value equals / contains, URL contains / equals, has class, has attribute • Condition: skip the next steps when a check is false • Switch: based on a variable's value, run another scenario, jump to another step, or run only the matching block of steps • Variables with ${name} syntax in selectors, values, URLs and scripts: Static, Random (letters, digits, mixed, date-time), Pick from a list, or Fallback • Global variables shared by all scenarios • Rename a variable once and every scenario that uses it follows ▸ ASSERTIONS, CLEAR VERDICTS AND BUG REPORTS • Assert (Expect) checks that the page shows what it should, retried for up to 5 seconds so slow pages don't cause false failures • A failed check is recorded and the run carries on, so a single run tells you everything that is wrong • Every run ends with a verdict: ✓ Passed, ✗ Failed (the app is wrong), ⚠ Test broken (a step could not run), ⏹ Stopped • See the result in a notification, on the toolbar badge and on the Last run card, with one line per failure, such as: Expected text "Saved", got "Error" • One click creates a Markdown bug report with the page URL, browser and OS, steps to reproduce and a screenshot. Typed values and passwords stay hidden unless you choose to include them ▸ DATA-DRIVEN TESTING WITH CSV • Run a scenario once for every row of a CSV file; the header row names the variables • Each row gets its own result and a list of the steps that failed • Export results to Excel (XLSX) or HTML with images, or to a ZIP with a folder of screenshots for every row ▸ API TESTING • Keep API requests in folders on a full-page tool; paste a cURL command copied from DevTools to create one, or copy any request back as cURL • Check the status, a JSON path, a header, the body or the response time; click a key in the JSON response to turn it into a check • The same verdicts as your UI tests: ✓ Passed, ✗ Failed, ⚠ Broken. A request with no status check must answer 2xx, so a server error never slips through • Environments (Dev, Staging…) with ${variables}, values saved from a response for the next request (such as a login token), and Bearer, Basic or API key auth set once on a folder • Run a folder or the selected requests one after another; requests that change data (POST, PUT, PATCH, DELETE) ask before they go • Import Postman collections and environments, export to Collection v2.1 format (ready to run in CI), and save the results as CSV • Requests are sent from your browser, so cross-origin (CORS) limits don't block them, and the site's cookies go along unless you turn them off for a request ▸ EXPORT TO CODE Turn any scenario into: • Selenium Python (plain script or pytest) • Selenium Java (TestNG) • Playwright Test • Robot Framework • JavaScript bookmarklet Plus JSON export / import of scenarios and folders, and full backup / restore of your data. ▸ SCREENSHOTS AND IMAGE TOOLS • Capture the visible area, the full page, scrolling captures (vertical / horizontal), segments, a single element or a whole window • Crop and edit every capture; a standalone image editor opens images from the clipboard or a file • Pixel-level image diff to compare two images • Optional watermark and file name prefix ▸ HIGHLIGHTS AND REVIEW NOTES • Select text on a page to highlight it in 5 colours and attach a note, handy for exploratory testing and content review • Highlights come back automatically when you revisit the page, even on content that loads late • URL patterns with wildcards group several pages under one set of highlights • Search, filter by colour or page, and export everything as JSON ▸ SQL TEST CASE DESIGNER • Paste a SELECT, INSERT, UPDATE or DELETE statement and get a numbered list of test cases • Techniques: equivalence partitioning and boundary value analysis, decision tables and MC/DC, NULL and three-valued logic, JOIN cardinality, grouping and paging • Edit the sample values in one panel and export the test cases to CSV or JSON • Understands MySQL, PostgreSQL and SQL Server syntax, in English or Vietnamese; everything runs locally in the page ▸ DATABASE TEST SESSION FOR ADMINER • Records every row you change through Adminer: edit forms, grid edits, bulk delete, INSERT and hand-written SQL • Roll back a whole test run in one go, with a preview of the exact SQL • A drift check warns you when someone else changed a row after your test touched it ▸ COMFORTABLE TO USE • Dark and light themes • Five tabs you can reorder by drag and drop, and collapsible cards • The SQL, API and database tools open in full-page tabs with a collapsible side panel • Configurable keyboard shortcuts • Notifications when a run finishes ▸ WHO IT'S FOR • Manual testers taking their first steps into automation • QA engineers running regression, smoke, API and data-driven tests • Developers checking forms and user flows before a release • Business analysts and product owners who need reproducible bug reports ▸ PRIVACY Pocket QA needs no account and contains no analytics or tracking. Recording, playback and element picking work only on the tabs you turn the extension on for, unless you choose Allow on all tabs in Settings. Your scenarios, variables, highlights, API requests and environments, test results and database change logs are stored locally in your browser; some preferences, such as keyboard shortcuts and capture settings, can sync through your own Chrome profile. The SQL designer and the database rollback run entirely in the page. API requests are sent only when you press Send or Run, straight from your browser to the addresses you entered; scripts inside imported collections are never run, and tokens and passwords are left out of exports unless you choose to include them. The only request the extension makes on its own is a small daily check for important update notices. ▸ WHY THESE PERMISSIONS • Access to all websites: to record and replay tests on the sites you choose to test, and to send the API requests you write to the addresses you enter • Debugger: for trusted clicks on native dropdowns, full-page and element screenshots, file uploads and running your scripts. While it is in use, Chrome shows a bar saying the extension is debugging the browser; this is expected • Tabs, scripting and windows: to run each step in the right tab and frame and to open the editor windows • Storage: to save your scenarios and settings on your device • Downloads: to save images, exports and reports • Alarms: for scheduled runs and the daily update check • Notifications: to tell you how a run ended • Screen capture (optional, requested only when you use it): to capture a whole window ▸ GET STARTED 1. Open the page you want to test and click the Pocket QA icon 2. Press Start Recording; the first time on a tab, choose Turn on 3. Click and type as usual, then press Stop and name the scenario 4. Add checks with Add Action → Assert 5. Press Play and read the verdict Testing an API? Open the Tools tab → Manage API tests, paste a cURL command and press Send. Pocket QA is an independent tool and is not affiliated with or endorsed by the makers of the tools it works with.
3.7 out of 53 ratings
Details
- Version1.0.33
- UpdatedNovember 17, 2026
- Offered byHakij
- Size1.06MiB
- LanguagesEnglish
- Developer
Email
kthoangst1@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes