Steve Archbold's List: bdd

• Find your slowest-running cucumber features
• scenario_times = {}

   

  Around() do |scenario, block|

    start = Time.now

    block.call

    scenario_times["#{scenario.feature.file}::#{scenario.name}"] = Time.now - start

  end

   

  at_exit do

    max_scenarios = scenario_times.size > 20 ? 20 : scenario_times.size

    puts "------------- Top #{max_scenarios} slowest scenarios -------------"

    sorted_times = scenario_times.sort { |a, b| b[1] <=> a[1] }

    sorted_times[0..max_scenarios - 1].each do |key, value|

      puts "#{value.round(2)}  #{key}"

    end

  end

• (My) Cucumber best practices and tips
• 1. Organize your garden
• 3. Background: setup the DRY way
• 4. Scenario outlines: scenario with variables!
• 5. Multi-line step arguments: give your step a table for lunch!

3 more annotations...

• What makes a good feature file
• • About the business domain – not software design
  • In domain language
  • Specification – not a script
  • Easy to understand
  • Focused on a single thing
  • Precise and testable
  • Self-explanatory
  • Consistent
  • Easy to access

• Categories of bad smell in a feature file:

  • Long sentences
  • Repetitious sentences
  • Repetitive scenarios
  • A Never ending story
  • Commentary
  • And another thing
• Long sentences

• Treatments:

  • Plain English
  • Active Voice
  • Break lists into tables or bullets
• Repetitious sentences

• Treatments:

  • Extract the parts that vary into a table
• Repetitive scenarios

• Treatments:

  • Specify a background for repeated setup
  • Use examples to describe varying data
• A Never ending story

• Treatment:

  • Consider using a background
  • Break up the scenario
  • Break the scenario up with tables
• Commentary

• Treatment:

  • Start again
• And Another Thing 

• Treatments:

  • Try describing the initial state in a single line.
  • Split into multiple scenarios

• Positive Example

  How does a good feature file look then? Here’s an example from Gojko & David’s slides:

   Feature: Free Delivery  In order to increase customer loyalty VIP customers buying a lot of books should get free delivery   Scenario outline: Free delivery  Given the threshold for free delivery is 10 books  And the customer is <type> with <books> in the cart  When checking out  Then free delivery is <free delivery>   Examples  | type   | books | free delivery |  | VIP    |   9   | not offered   |  | VIP    |  10   | offered       |  | VIP    |  11   | offered       |  | Normal |  10   | not offered   | 
• Collaboration

• Start by having conversations, engaging both testers and business stakeholders

    

  If you can’t have those conversations, stop. You can’t do BDD

16 more annotations...

• Writing better steps
• A step description should never contain regexen, CSS or XPath selectors, any kind of code or data structure. It should be easily understood just by reading the description.

• Writing better Cucumber features
• Features can contain extra details if it is relevant to the feature
• Scenarios should not automate the UI
• Features should only contain information that the user sees
• Scenarios should not be dependant on other scenarios
• Use Background for setup when there's more than one scenario
• Feature names are features not processes
• Don't use multiple 'thens'
• Your features are your documentation
• Relish  is a very useful new site that takes all your feature files and displays them in a very readable format.

8 more annotations...