In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
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
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
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
Node.js
Building a CLI tool with oclif is pleasantly structured. Each subcommand is a class with a run() method. Flags and args are declared statically. The framework handles parsing, help generation, and error formatting. The problem is that most teams treat this structure as incidental and test nothing until something breaks
Python
mutmut is the most widely adopted Python mutation testing tool. It works by making small, targeted modifications to your source code — flipping + to -, changing True to False, removing return values — and running your test suite against each modification. If your tests don't fail when the code changes, those
PHP
Code coverage is one of those metrics that developers either obsess over or dismiss entirely. The truth sits between those extremes: coverage data is genuinely useful for finding untested code paths, but a 90% coverage number tells you nothing about whether those tests are actually meaningful. Understanding what coverage measures
Shell Testing
Most shell testing frameworks assume you are running bash. Real infrastructure does not. Log processors run under POSIX sh on Alpine Linux. Deployment scripts run under ksh on AIX. Init scripts run under dash on Debian. If your tests only work with bash, you will not catch the bugs that
OCaml
OCaml has a strong type system that catches many bugs at compile time, but types can't verify that your sorting algorithm actually sorts or that your parser handles malformed input gracefully. For that you need tests. Alcotest is OCaml's most popular lightweight test framework — it'
iOS Testing
A test suite that takes 45 minutes to run is not a safety net — it is a speed bump. Engineers skip it, merge without waiting, and the feedback loop that automated testing is supposed to provide collapses. Slow iOS CI is one of the most consistent complaints in mobile development,
Erlang
Erlang was designed for systems that must not fail — telecom infrastructure running nine nines of uptime. That heritage means Erlang's testing tools are mature, battle-tested, and deeply integrated with the OTP framework. EUnit handles unit tests in a lightweight, embeddable way. Common Test provides a full-featured
PHP
Infection is the leading mutation testing framework for PHP. It operates on the Abstract Syntax Tree (AST) level — generating mutants by altering your source code according to predefined mutation operators — then running your test suite against each change. A test suite that kills 80%+ of mutants provides much stronger behavioral