Reading List: Requirements / Business Rules / BDD

Agile / BDD Requirements
Requirements Storytelling / Storymapping
Requirements and Business Rules
Cucumber / Gherkin
General
Lists

Agile / BDD Requirements

Requirements Storytelling / Storymapping

Requirements and Business Rules

Cucumber / Gherkin

  • theitriskmanager.com: The tragedy of Given-When-Then – “… there are at least three different types of things to specify about a system: 1. What the system looks like. 2. The calculations in a system, and the data needed. 3. The behaviour of the system based on its internal state, and the system interactions within and without the system.”; “Although Given-When-Then is a fantastic way to describe interactions, state and behaviour, it is a lousy way to describe data and calculations.”; “The reduction of the tester to an expert translator/typist is a tragedy. It means that the business analyst does not necessarily see the actual Given-When-Then statements and a disconnect occurs between the them and the testers and developers. Cucumber comes to be seen as a test automation tool rather than a repository of the system specification.”; “Business Analysts often do not see the feature files and do not fully understand the process. They see no value in cucumber, seeing it as a test automation tool.”; “Agile was created by studying those who “do it and help others do it”, except in the case of business analysis where developers make stuff up for business analysts to do… Where the observers, not the doers, define the process.”; “Ideally we will realise that Given-When-Then is a tool for describing the interactions, state and behaviour of systems. We will realise that describing data and calculations using the Given-When-Then format leads to tragedy, and will create and popularise tools and approaches using Excel to document examples.”
  • Cucumber: Gherkin Wiki
  • Groupon: Dima Kovalenko: Case Study: Poorly Written Cucumber Tests –
  • Automation-excellence: Declare or Impair (pro-Declarative)
  • WatirMelon: Cucumber: imperative or declarative? that is the question (pro-Imperative)
  • Ben Mabey: Imperative vs. Declarative Scenarios in User Stories (pro-declarative but balanced perspective – endorsed by Aslak Hellesoy who created Cucumber)
  • Friendly Tester: Using BDD Tools To Write Automated Checks != BDD – be sure gherkin is serving a purpose such as clarity or facilitating readability
  • Jeff Nyman: The BDD Lure and Trap – “Unit tests are just another form of acceptance test when you realize that acceptance testing is an approach to testing, not a type of testing”;  references The Cucumber Trap
  • Tea-Driven Development: Is Cucumber just a scam? (pro-Cucumber article, good pros and cons discussion in comments)

General

Lists

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: