In-depth tutorials and comparisons for testing tools and frameworks — Playwright, Cypress, Selenium, Robot Framework, and more.
Security Testing
The NIST Cybersecurity Framework (CSF) provides a flexible structure for managing cybersecurity risk. Unlike FIPS 140 or SOX, the CSF is not prescriptive — it describes outcomes, not specific controls. This makes it adaptable but also harder to test against. This guide maps CSF functions and categories to concrete automated tests.
Security Testing
FIPS 140-2 (and its successor FIPS 140-3) defines security requirements for cryptographic modules used in federal systems. If your application handles sensitive government data or pursues FedRAMP authorization, you need to use FIPS-validated cryptographic modules. Testing verifies your code actually uses them. What FIPS 140-2/3
Security Testing
FedRAMP (Federal Risk and Authorization Management Program) is the U.S. federal government's standard for cloud service security. If your product serves federal agencies, FedRAMP authorization is required. The security testing requirements are among the most rigorous in any compliance framework — and a significant portion can be automated.
Visual Testing
Reg-Suit is a visual regression testing framework built around a plugin architecture. Unlike tools that are opinionated about screenshot capture, Reg-Suit focuses on the comparison and reporting layer — you bring your own screenshots, and Reg-Suit handles storage, comparison, and CI status reporting. Architecture Reg-Suit separates three
Visual Testing
Loki is a visual regression testing tool purpose-built for Storybook. It runs locally and in CI, captures screenshots of every story, compares them against stored references, and shows diffs when components change. Unlike cloud-hosted alternatives, Loki stores reference images in your repository and runs entirely offline. Why Loki
Visual Testing
Happo solves a specific problem: visual regression testing across multiple browsers simultaneously. While Chromium-only tools catch 80% of visual regressions, cross-browser differences — font rendering, flexbox quirks, Safari's date inputs — require testing against real browser engines. Happo runs your components in Chrome, Firefox, Safari, and Edge and
Visual Testing
Visual regression testing catches UI changes that unit tests miss. Lost Pixel is an open-source visual regression testing platform that compares screenshots of components or pages across commits, flags differences, and integrates with your existing CI pipeline. Unlike hosted-only tools, Lost Pixel can run entirely in your own
Clojure
re-frame's unidirectional data flow — events → effects → db → subscriptions → views — makes applications predictable. It also makes them testable. Every piece of behavior in a re-frame app is a pure function or a data-driven side effect description. re-frame-test provides the tooling to test them without
Clojure
Example-based tests check specific cases. Property-based tests check invariants across hundreds of randomly generated inputs. test.check is Clojure's property testing library — a port of Haskell's QuickCheck — and it finds bugs that no developer thought to test for. Why Property-Based Testing Consider a
Clojure
Kaocha is the most flexible test runner in the Clojure ecosystem. While lein test and clojure -M:test get you started, Kaocha gives you fine-grained control over test selection, execution order, output formatting, and extensibility through plugins. This guide covers advanced Kaocha configuration for teams that need more than
Test Automation
Testing effectful Haskell code is where the language's type system earns its reputation. By abstracting over effects — whether through MTL typeclasses or algebraic effect systems like Polysemy — you can run production code with a pure test interpreter. No mocking frameworks, no monkey-patching, just different interpreters for different
Test Automation
Tasty is a composable test framework for Haskell. It doesn't replace HUnit, QuickCheck, or Hedgehog — it organizes them. Tasty provides a TestTree abstraction that lets you mix testing libraries, run tests in parallel, filter by name, and generate multiple output formats from a single test suite. The Core