Behavior-driven development guides — write tests in plain English with Cucumber, Gherkin, and Robot Framework.
Tools & Frameworks
SpecFlow is the leading BDD framework for .NET, letting teams write Gherkin feature files and execute them through C# step bindings. It integrates with NUnit, MSTest, and xUnit, supports full dependency injection via built-in or external DI containers, and ships with a Visual Studio / Rider extension for a smooth
BDD
FitNesse is older than most modern testing frameworks and carries that age visibly — a wiki-based test editor, table-driven specs, Java-centric tooling. But it solves a specific problem exceptionally well: getting non-technical business stakeholders to write and own acceptance tests, structured as business rules rather than test
Tools & Frameworks
FitNesse is a self-contained wiki server and acceptance testing framework. Teams write test tables directly in a browser-based wiki, and FitNesse executes them against Java (or other language) fixtures. It is the canonical tool for Acceptance Test-Driven Development (ATDD) and is especially well-suited to legacy Java
Testing
Example Mapping is a structured 25-minute workshop where a developer, tester, and product person use four colored cards — yellow (story), blue (rules), green (examples), red (questions) — to turn a vague user story into concrete, testable examples. The output maps directly to Gherkin scenarios. Stories that generate too many red
BDD
Living documentation solves a specific problem: the gap between what tests prove and what stakeholders can read. Test results are for engineers — pass/fail counts, stack traces, assertion errors. Living documentation is for everyone — narrative descriptions of system behavior, organized by feature, backed by evidence from actual test runs. Serenity
BDD
Serenity BDD integrates with REST Assured to give you the same rich HTML reports for API tests that you get for UI tests. Combine this with Cucumber and you can write acceptance tests that mix API calls and browser interactions in a single scenario — useful for tests that need to
BDD
Serenity BDD integrates with Cucumber to give you something neither framework provides alone: Cucumber's plain-English scenarios plus Serenity's rich HTML reports with screenshots, step-level narrative, and coverage statistics. This guide covers the full setup from scratch. What Serenity Adds to Cucumber Cucumber gives you
Python
Behave and the Python requests library are a natural pairing for API testing. You write scenarios in plain Gherkin that non-developers can read, while step definitions handle the HTTP calls. This post walks through project setup, reusable context objects, authentication flows, and error-case testing — all with working code.
Testing
Cucumber is often pitched as "better JUnit" — more readable, closer to requirements, collaborative. That framing is wrong. Cucumber and JUnit aren't alternatives to each other; they serve different purposes and most teams need both. The real question isn't "Cucumber or JUnit?" It&
Testing
A Cucumber test suite with 200 scenarios running sequentially might take 10-15 minutes. That's too long for a feedback loop during development and an obstacle in CI pipelines. Parallel execution can cut that to 2-4 minutes, but it requires making your tests thread-safe. This guide
Testing
Three frameworks dominate the Java BDD landscape: Cucumber-JVM, JBehave, and Serenity BDD. All three let you write acceptance tests in a business-readable format and map them to Java glue code. Beyond that surface similarity, they make very different trade-offs. Picking the wrong one costs you months of
Testing
Cucumber-JVM brings Behaviour-Driven Development to the JVM. Combined with Spring Boot, it gives you executable specifications that run against a real (or sliced) application context. This guide covers everything from zero to a working BDD suite: dependency setup, Spring integration, writing your first feature file, defining steps, and