In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
Testing
The Vue 3 Composition API changed how we write Vue components — and it changed how we test them. Composables can be tested in isolation, reactive state is explicit and predictable, and <script setup> components are simpler to reason about. But the patterns for testing them effectively aren'
Testing
Single-SPA is a framework for orchestrating multiple micro-frontend applications on a single page. Each micro-frontend registers as an application with its own lifecycle hooks — bootstrap, mount, and unmount — and Single-SPA activates them based on URL patterns. Testing Single-SPA applications requires testing at three levels: individual micro-frontend lifecycle hooks, the root-config
Testing
Playwright has first-class support for Electron application testing since v1.9. Unlike Spectron (deprecated) or older Electron testing approaches, Playwright connects to Electron directly — giving you access to both the renderer process (web content) and the main process (Node.js environment) in a single test. This guide covers Electron E2E
Testing
Desktop apps must work on Linux, macOS, and Windows — and each platform has different rendering engines, file system behaviors, system APIs, and distribution formats. A CI/CD pipeline that only tests on one platform misses platform-specific bugs. This guide covers building cross-platform CI/CD testing pipelines for desktop applications built
Testing
Module Federation in Webpack 5 enables true micro-frontend architecture — separate teams building, deploying, and updating independent JavaScript bundles that compose into a single application at runtime. The testing challenges this introduces are real: federated modules can fail to load, version contracts can break silently, and the shell app's
Testing
@testing-library/vue applies Testing Library's core philosophy to Vue 3 component tests: query elements the way users find them, interact with the interface like a user would, and assert on visible outcomes rather than implementation details. This guide shows how to write Vue 3 component tests with Testing
Testing
Nuxt 3's auto-imports, composables, and server routes require a different testing approach than standard Vue 3. Vitest combined with @nuxt/test-utils provides first-class support for testing in the Nuxt runtime environment — giving you access to auto-imported functions, useNuxtApp(), and SSR utilities without elaborate mocking. This guide covers unit
Testing
Nuxt 3's server directory provides a full Node.js server powered by H3, Nitro, and unjs utilities. Server routes in /server/api/, middleware in /server/middleware/, and utilities in /server/utils/ are testable as regular HTTP handlers — you don't need to spin up a browser to
Testing
Nuxt 3's server-side rendering, file-based routing, and auto-imports make it a powerful framework — and each of those features introduces testing considerations that plain Vue apps don't have. Playwright is the right tool for Nuxt 3 end-to-end testing: it handles SSR-rendered HTML, navigates routes, intercepts network requests,
Test Automation
Vitest's browser mode runs your tests inside a real browser instead of a simulated DOM environment like jsdom or happy-dom. This matters because jsdom does not execute real JavaScript rendering, does not run CSS layout, and does not implement browser APIs like ResizeObserver, IntersectionObserver, or Web Components. When
Test Automation
Vite plugins extend the build pipeline with custom transforms, virtual modules, and build hooks. Testing them is harder than testing application code because a plugin's behavior is entangled with Vite's internals — module graphs, HMR events, rollup hooks. This guide covers a practical, reproducible approach to testing
Test Automation
H3 is the HTTP framework that powers Nitro, which in turn powers Nuxt 3's server engine. If you write server/api/*.ts or server/routes/*.ts files in a Nuxt project, you are writing H3 event handlers. Testing these handlers in isolation — without starting a full Nuxt or