Talk
BDD Requirements Management
Slides covering BDD requirements management and how living documentation supports delivery teams.
Category
Presentations
Slides and materials from presentations about Serenity BDD and BDD practices, covering requirements management, case studies, and implementation guides.
Talk materials and decks
A small collection of slide decks shared during community talks and conference sessions. Use them to explore how Serenity BDD fits into a real-world testing workflow.
Case Study
Adoption Patterns
Implementation notes and patterns drawn from teams introducing Serenity into their acceptance test suites.
Guide
Implementation Overview
A walkthrough of the core building blocks, useful as a starting point for your own internal sessions.
Continue exploring
Pair these slides with hands-on guides and release notes to see how the ideas map onto a working project.
Conference talks and slide decks offer a practical window into how teams apply Serenity BDD beyond the documentation. Presenters often walk through the structure of a real project, showing how features, stories, and acceptance criteria are organized in living documentation and how that documentation evolves alongside the code. The materials are typically designed to be self-contained, so attendees can revisit the slides later and trace ideas back to working examples. This makes presentations a useful complement to written guides, especially for newcomers who want to see the bigger picture before diving into configuration details, reporting setups, or integration choices within their own automated acceptance testing workflows and broader quality strategies.
Requirements management is a recurring theme in BDD-focused talks because it shapes how scenarios get written and how reports are interpreted. Speakers frequently highlight how epics, features, and stories relate to one another, and how cucumber or jbehave style scenarios can be tied back to higher level requirements for traceability. Slides often contrast manual and automated coverage side by side, showing how a single source of criteria can drive both review conversations and regression suites. The emphasis is usually on clarity rather than volume, encouraging teams to write focused scenarios that describe intent instead of exhaustively scripting every interaction, which keeps living documentation readable and relevant throughout the development lifecycle.
Case study sessions tend to focus on adoption patterns rather than abstract methodology. Presenters share what worked, what had to be changed, and how the team iterated on its approach to step libraries, page objects, and webdriver configuration. Common topics include organizing step definitions, structuring page object classes, and deciding where helper methods belong, as well as handling waits, implicit versus explicit timeouts, and findby strategies. Talks also touch on reporting concerns, from screenshot capture to coverage summaries and how default reporting behavior can be customized through properties, plugins, and maven configuration. The goal is to give listeners a realistic sense of the trade offs involved in scaling BDD practices.
Implementation guides presented at conferences often double as reference material that teams can apply directly to their own projects. Slides typically walk through directory structures, configuration files, and the relationship between junit test runners, reporting outputs, and the issue tracking workflow. Speakers may demonstrate how jira integration links scenarios to tickets, how release notes and version metadata are generated, and how capabilities and browser settings are externalized for different environments. Audience questions frequently surface practical concerns about fixing failing tests, maintaining older versions, and keeping documentation in sync as the project grows. These sessions tend to leave participants with a clearer mental model of the moving parts.