ruby-on-railsrspeccucumberbddatdd

Are cucumber scenarios stories in a sprint?


I am just starting off with Cucumber and BDD/ATDP(Acceptance Test Driven Planning) in a new project, I am not 100% sure of what makes up a story, are the scenarios what I will end up using as my sprint stories? I am guessing this should be the case but not 100% sure if I am right, or is it the case that the feature description as in the example below would be the story?

e.g

feature: Ability to duplicate an invoice record

In order to re-use a particular invoice details
As a user
I want to be able to duplicate an existing invoice record

Solution

  • An user Story is a {small} functionality which can be tested and 
    delivered within a timebox. Scenarios represent different ways of interacting 
    with that functionality.  So, an User Story may have multiple scenarios. 
    Scenarios are implemented in {re-usable} steps.
    

    In your case, the various scenarios could be

    Feature: Invoice duplication
      ...
      Scenario: Valid invoice
      ...    
      Scenario: Non-existing invoice
      ...    
      Scenario: Already duplicated invoice
      ...    
      Scenario: Expired invoice
      ...
    

    The scenarios above verify/test your User Story/Feature i.e. Invoice Duplication.

    Scrum Guide => https://www.scrum.org/Portals/0/Documents/Scrum%20Guides/2013/Scrum-Guide.pdf#zoom=100