Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Acceptance Criteria and Example Mapping: Clarifying Rules with Examples
Acceptance criteria are a story's conditions of acceptance, and they work best when every rule has concrete examples under it. Using Bookstore's institutional discount and partial shipment cards, we cover rule-based and scenario-based criteria, how they differ from the Definition of Done and Definition of Ready, a four-colour Example Mapping session, and deciding at the end whether a story is ready, should be split or needs investigation.
Executable Specifications with Gherkin: Given-When-Then, Rule, Scenario Outline and Writing Declarative Scenarios
Gherkin turns the rules and examples found in Example Mapping into a specification that stakeholders can read and a test runner can execute; a good scenario describes the business rule, not the UI. Using Bookstore's institutional order rules, we cover Feature, Rule, Background, Scenario Outline, Examples and data tables, declarative versus imperative scenarios, the Turkish keyword decision and Gherkin anti-patterns.
BDD in .NET: Binding Gherkin Scenarios to the Bookstore API with Reqnroll 3
SpecFlow reached end of life on December 31, 2024; the current way to run Gherkin scenarios in .NET is Reqnroll 3, with the Reqnroll.xunit.v3 package for xUnit v3. We bind Bookstore's institutional order scenarios to the API on .NET 10: project setup, step definitions, context injection, WebApplicationFactory, a diagnostic hook for failures, living documentation with the HTML formatter and filtering by tag, plus a pitfall observed under Turkish culture.