In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
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 more
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's
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
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, not browser.newPage. Extensions
Test Automation
Test Chrome extensions at three levels: unit-test business logic with Jest + chrome-mock (no browser required), integration-test UI with Puppeteer by loading the unpacked extension, and end-to-end test user flows with HelpMeTest. Use sinon-chrome or jest-chrome to mock the chrome.* APIs in unit tests. Key Takeaways Unit test business logic in
Testing
Electron E2E testing with Playwright tests the full application, but unit tests with Jest run in milliseconds and catch business logic bugs during development. The challenge is that Electron's main process and renderer both have APIs that don't exist in Node.js or jsdom test environments.
Tools & Frameworks
PHPUnit is the standard PHP testing framework. Pest is a modern alternative that wraps PHPUnit with a cleaner functional syntax. Both produce identical test results — the difference is entirely how you write tests. Pest is Laravel's default since v11. PHPUnit is the safe choice everywhere else. Key Takeaways
Integration Testing
Integration tests verify that PHP components work together: your service classes with a real database, your HTTP controllers with real routing, your external API clients against real or stubbed endpoints. This guide covers database integration testing with transactions, HTTP layer testing, testing with real queues and caches, and integrating with