In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
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,
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 framework for
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
Go
CLI tools are deceptively hard to test. They interact through stdin and stdout, depend on environment variables and working directories, return exit codes instead of values, and often spawn subprocesses. Most teams settle for a few manual smoke tests and call it done. When the CLI breaks in a way
iOS Testing
UI bugs are the ones users actually notice. A misaligned button, a truncated label, a broken dark mode layout — none of these are caught by a unit test that only verifies a view model property. Snapshot testing exists to close this gap. It captures the visual output of your UI
Haskell
Testing in a purely functional language like Haskell has a reputation for being either trivially easy (pure functions are referentially transparent, so you just call them) or surprisingly complex (dealing with IO, monads, and laziness). The truth is somewhere in the middle. HSpec, inspired by Ruby's RSpec, gives
Tools & Frameworks
Most PHP projects end up with three separate testing tools: PHPUnit for unit tests, something else for HTTP integration, and a browser automation library bolted on for end-to-end scenarios. Each tool has its own configuration format, its own runner, and its own reporting conventions. Codeception was built to fix exactly