In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
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
Shell Testing
Shell scripts are the connective tissue of most infrastructure: they bootstrap servers, run deployments, process log files, and glue together a dozen other tools. Yet most teams test bash scripts the same way they have for decades — by running them manually and hoping nothing breaks. BATS (Bash Automated Testing System)
F#
F# testing has two solid options: you can use the C# testing frameworks (NUnit, xUnit) via FsUnit, or you can use Expecto — a framework built specifically for F# that embraces functional design with first-class functions, composable test lists, and native async support. Both approaches work; Expecto tends to feel
Clojure
Clojure's testing ecosystem is unusually rich for a language its size. At the foundation sits clojure.test, included in the standard library and requiring no dependencies. On top of that, Midje adds a readable BDD-style syntax with powerful stubbing. And test.check brings property-based testing — Clojure&
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
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
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
Test Automation
Playwright supports browser extension testing in Chromium (full support) and Firefox (experimental). Use chromium.launchPersistentContext() with --load-extension and --disable-extensions-except flags. For Firefox, launch with firefox.launchPersistentContext() and set firefox_profile preferences. Access the extension popup by navigating directly to its chrome-extension:// URL. Key Takeaways Use launchPersistentContext,