Implementing Executable Specifications with NBehave: Ensuring Quality through Examples

DESCRIPTION

This document explores the concept of executable specifications using NBehave, demonstrating how to bridge the gap between requirements and code. It emphasizes the importance of acceptance criteria and outlines how errors can be introduced in project development. By referencing valuable resources such as the Chaos Report and stories as requirements, it provides insight on best practices in behavior-driven development (BDD) with tools like JBehave and Cucumber. Learn how to create precise specifications that enhance collaboration and minimize risk in software projects.

Download

executable specifications with examples using nbehave

1 / 10

Apr 29, 2026

Download Presentation

Télécharger la présentation

Implementing Executable Specifications with NBehave: Ensuring Quality through Examples

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

Executable specifications with examples using NBehave • Morgan Persson • morgan.persson@enea.com • @lazydev

The solution
The Obvious
Where errors are introduced Source: Chaos report

story as requirements http://dannorth.net/whats-in-a-story
Acceptance criteria
Requirements to code
Nbehave • http://nbehave.org/ • Jbehave • http://jbehave.org • Cucmber • http://cukes.info/ • Morgan Perssonmorgan.persson@enea.com @lazydev