Every week, without fail, I'd find myself searching for the same things.
"Playwright intercept POST request." "Cypress wait for API response." "How to skip login UI in Playwright."
I've been a senior QA automation engineer for years. I know these patterns. But I'd still end up on the same Stack Overflow threads, the same outdated blog posts, the same GitHub Gists that may or may not still work with the current version.
And when I couldn't find what I needed fast enough, I'd ask AI to generate it for me. That worked — but it felt like there should be a better way.
So I built one.
What is SnipQA?
SnipQA is a free, searchable snippet library built specifically for QA automation engineers working with Playwright and Cypress.
It has two main features:
- A curated snippet library 137+ real-world code snippets covering everything from authentication and network interception to file uploads, visual testing, fixtures, selectors, and more. Every snippet is commented to explain why, not just what.
- An AI generator You describe what you need in plain English — "intercept a failed API response and show an error message" — and get a working, commented snippet instantly. No prompt engineering needed, just describe your scenario.
What it covers
Both Playwright (TypeScript) and Cypress (JavaScript) — across these categories:
Auth (login via UI, via API, storageState, cy.session)
Network (intercept, mock, abort, modify headers)
Assertions (visible, text, URL, title, count, soft assertions)
Selectors (getByRole, getByLabel, getByTestId, getByText, XPath)
Forms (dropdowns, checkboxes, radio buttons, file upload, date inputs)
Fixtures (beforeEach, afterEach, test.describe, data-driven)
Visual (screenshot, element screenshot, baseline comparison)
Wait (network idle, element disappear, URL change)
Navigation (multi-tab, back/forward, redirect)
And more
Why I built it the way I did
I deliberately kept it simple. No login required. No account. No paywall. You land on the page, you search, you copy, you go back to work.
The AI generation is powered by Claude with a QA-specific system prompt — so the output follows actual best practices for each framework version, not just generic code.
The like/dislike system on each snippet is there so the most useful patterns surface over time as more engineers use it.
What's next
I'm planning to add:
Page Object Model snippets
CI/CD config snippets (GitHub Actions)
Accessibility testing patterns
A "show equivalent in Cypress/Playwright" toggle
But honestly the most valuable input right now would come from you. What patterns do you search for most? What's missing? What would make this actually save you time?
It's free, no account needed. Try the AI generator and tell me what you think.
Top comments (0)