Production-grade test automation frameworks and npm packages — crafted by a practising SDET with 10+ years of experience. Fork a boilerplate, install a package, and start shipping quality faster today.
MIT Licensed Production Ready Actively Maintained Built for the Community
3
Boilerplates
3
npm Packages
236
Tests Passing
MIT
License
Free
Always
Why QA Pulse by SK Builds Open Source
Every QA engineer has started a new job and spent the first two weeks setting up a test framework from scratch — installing dependencies, wiring up reporters, configuring CI, writing the first page object. That time is wasted. The real work is writing tests that catch bugs, not configuring infrastructure that already exists.
The products on this page eliminate that setup cost entirely. Fork a boilerplate and you have a production-grade framework in minutes. Install a package and you get assertions, reports, or test generation that would take days to build yourself. Everything is open source, MIT licensed, and free to use commercially — because quality tooling should be accessible to every QA engineer, not just teams with large budgets.
Clone & Start Testing
Test Automation Boilerplates
Fork, configure your base URL, and start writing tests. Everything else — folder structure, reporters, CI pipelines, auth setup, data factories — is already wired up and working.
TS + JS
Playwright Boilerplate
TypeScript & JavaScript · v1.0.0
A production-grade Playwright framework you can fork and start writing tests in minutes. Comes with Page Object Model, API testing layer, visual regression, WCAG 2.1 accessibility, Faker.js data factory, Allure + HTML + JUnit reporters, and full CI/CD for GitHub Actions, Jenkins and Azure DevOps. TypeScript on master, JavaScript on the javascript branch — both feature-identical. The with-packages branch integrates all QAPulseSK npm packages with 101 passing tests against real-world targets including SuiteCRM.
What you get
Page Object Model — BasePage + BaseComponent + Fixtures
A production-grade Cypress 13 framework with 12 custom commands, full Page Object Model, API testing with cy.request helpers, visual regression, WCAG 2.1 accessibility checks, cy.session() for fast login reuse, and cypress-grep for tagging tests by @smoke, @regression, @critical. Mochawesome + Allure reporting out of the box. TypeScript on master, JavaScript on the javascript branch.
A production-grade Selenium 4 boilerplate with Python on master, Java (Maven + TestNG) on the java branch, and WebdriverIO on the javascript branch — all feature-identical. Full POM with BasePage, BaseComponent, PageFixtures and ApiFixtures. Includes WaitHelper, ScreenshotHelper, A11yHelper, DataFactory, parallel execution via pytest-xdist, and Docker + Selenium Grid support.
Framework-agnostic utility packages that plug into your existing test suite. Each one solves a specific problem that every QA engineer eventually hits — and solves it better than building it yourself.
Cross-Framework
qapulsesk-assert
npm · v1.0.5
One assertion library that works identically in Playwright, Cypress, Jest, Vitest and WebdriverIO — no more relearning assertions every time you switch frameworks. Ships with fuzzy text matching that handles typos and copy changes, API schema validation in a single call, response-time SLA assertions with clear pass/fail messages, zero-config WCAG 2.1 accessibility checks, and optional AI-powered semantic assertions via Claude that can test what an element means, not just what it contains.
What you get
assertFuzzyMatch — Levenshtein similarity, handles text variations & typos
assertSchema — validates full API response schema in one call
assertResponseTime — SLA-based performance assertions with clear messages
toBeAccessible — zero-config WCAG 2.1 check, no axe-core setup needed
assertObjectContains — partial object match, works in any framework
assertApproximately — number tolerance for prices, percentages & rates
toMean / satisfiesRule — AI semantic assertions via Claude (optional)
Works in Playwright · Cypress · Jest · Vitest · WebdriverIO
Most teams install four or five separate reporter packages — one per framework, one for Slack, one for AI analysis, one for trends. qapulsesk-report ships everything in one package. After every test run it generates a dark-theme branded HTML dashboard with a pass-rate ring chart, trend history across runs, and expandable failed-test rows with full error messages. Slack and Microsoft Teams webhooks, optional AI failure analysis that explains why tests failed in plain English, and a persistent history file that builds the trend chart automatically.
What you get
Dark-theme HTML report — professional, shareable, zero config
Pass rate ring chart — visual percentage at a glance
Trend chart — pass rate history across multiple runs
Failed tests section — expandable rows with full error details
Slack / Teams webhooks — pass/fail alerts after every run
AI failure analysis — plain-English explanation of failures (optional)
Works with Playwright · Cypress · Jest · Vitest
History tracking — .qapulse-history.json persists across runs
Record your browser interactions in Chrome DevTools, export as a HAR file, and turn them into clean Playwright or Cypress tests in 2 milliseconds — no AI key needed. The same HAR generates TypeScript and JavaScript for both frameworks simultaneously. Run it as a CLI tool with npx qapulsesk-gen from-har or import the generate() function directly into your own scripts and CI pipelines. Also supports Playwright recording files and plain-English test descriptions via the Claude API.
What you get
from-har — HAR file → Playwright or Cypress TS/JS in 2ms
Every pattern came from real production projects — e-commerce platforms, ERP systems, telecoms stacks, and travel platforms. You get architecture decisions already tested under real conditions, not patterns invented for a tutorial.
Maintained by a practising SDET
Not abandoned side projects. Actively updated when frameworks release breaking changes, extended based on real community feedback. When Playwright or Cypress ships a major version, the boilerplate gets updated.
Documented honestly
Every README includes a comparison table showing what standard libraries offer vs where QAPulseSK packages add genuine value. If the standard assertion does the same job, the docs say so. That honesty is the reason these tools are worth trusting.
Need something custom?
These open-source tools cover the most common needs. If you need a bespoke automation framework, a custom reporter, or a test generation pipeline built specifically for your stack — that is exactly what the consulting service is for.
QA