Test automation tutorials, frameworks, and tools — from first scripts to full CI/CD pipelines.
Background Jobs
Scheduled jobs and cron tasks are notoriously difficult to test. They run at specific times, interact with the real world (databases, APIs, files), and often involve time-sensitive logic. A monthly billing job that ran at 2:01 instead of 2:00 for a daylight saving transition can cause real production
Node.js
BullMQ is the modern successor to Bull for Node.js background job processing. It uses Redis for persistence and supports advanced patterns: priorities, rate limiting, flows (parent/child jobs), and job groups. Testing BullMQ requires understanding when to use real Redis versus mocks, and how to make workers testable. Testing
Test Reporting
JUnit XML is the lingua franca of test reporting. Originally a JUnit (Java) format, it's been adopted by every major test framework across every language. GitHub Actions, GitLab CI, Jenkins, CircleCI, and most other CI platforms can parse and display JUnit XML natively. Understanding how to generate and
Test Automation
Solid.js is fast by design — fine-grained reactivity, no virtual DOM, components that run once. That architecture is a strength at runtime, but it means your component tests can't rely on patterns from React or Vue. Signals update synchronously. Components don't re-render — they update in place.
Test Automation
Qwik's resumability model is fundamentally different from hydration. Components serialize their state into HTML, and execution resumes exactly where the server left off — no JavaScript re-execution, no reconciliation. That makes Qwik fast, but it also means your test setup needs to account for how Qwik actually runs code:
Test Automation
HTMX flips the standard SPA model: instead of JSON APIs and client-side rendering, the server returns HTML fragments that swap into the page. The JavaScript footprint is tiny, but the testing surface is real — swap targets, trigger events, out-of-band swaps, request headers, and server response formats all need verification. Standard
Test Automation
Stencil generates standard Web Components — Custom Elements with Shadow DOM — that run in any framework or vanilla HTML. That portability is the point, but it creates a testing challenge: your components need to work correctly both in isolation and when embedded in React, Angular, Vue, or plain HTML. Stencil comes
Test Automation
Lit builds on the Web Components standard — LitElement extends HTMLElement directly, uses the browser's native Custom Elements and Shadow DOM APIs, and adds a reactive property system and tagged template literal rendering. The result is small, fast web components that work anywhere. Testing Lit components requires real browser
Test Automation
WebExtensions work across Chrome, Firefox, and Edge via a common API standard, but there are meaningful compatibility differences in Manifest V3 support, background script models, and API availability. Use Playwright's multi-browser runner to test your extension in Chromium and Firefox. For Edge, test in Chromium (Edge uses the
Test Automation
Test Workbox service workers at three levels: unit test routing strategies with workbox-strategies in a mocked environment, integration test fetch behavior using sw-test-env which runs your service worker in Node.js, and end-to-end test cache behavior with Playwright. The makeServiceWorkerEnv() function from jest-service-worker (now service-worker-mock) gives you a DOM-less environment
Test Automation
Test PWA service workers by intercepting network requests with Playwright's page.route() to simulate offline mode. Verify caching strategies by blocking fetch requests and asserting cached responses are served. Test the install prompt by listening for the beforeinstallprompt event. Use Lighthouse CI to validate PWA criteria automatically in
Test Automation
Manifest V3 replaces background pages with service workers and removes chrome.webRequest blocking in favor of declarativeNetRequest. Test service workers by communicating via chrome.runtime.sendMessage from pages or content scripts. Service workers are ephemeral — they can be suspended between events, so your tests must account for startup latency. Use