This document discusses documentation vs tests for the Cucumber tool and provides examples of how to write Cucumber features and scenarios using tags like @i1 and @m1. It also includes information about synchronization of remote branches for stories and integrating Cucumber with other tools. Contact and resource details are provided at the end.

1. Documentation
vs
Tests
About tool Cucumber,
but not only for vegetarians
Michał Czyż

2. <me>

4. 1910
scenarios

5. @<estimation_number>
• @1 @2
● @3 @5
@8 @13

6. @<initials>
@bk @mw @rj

7. @m<number> @i<number>

8. @_<status
>

9. @new, @removed,
@skipped

10. @__<place_id>::<compon
ent_id>
@__checkout__address_d
etails
@__checkout__address_d
etails::
address_look_up

11. @m1 @mc
@__place_one::c_one
Feature: Sample feature
@i1 @2
Scenario: sample scenario
one
@i2 @1 @new
Scenario: sample scenario

12. #:::wireframe:
http://some_url
#:::page: place_one
#:::component: c_one
@m1 @mc
Feature: Sample feature
#:::estimation: 2
@i1
Scenario: sample scenario
one

17. @m1 @_spec
@m1 @_todo,@_backlog @mc
@m1
~@_done,@_qa,@_accepted
@m1, @m2, @m3 @new

20. Synchronization (remote
branches)
1)
stories_<latest>
2)
stories_<timestam
p>

21. Part of bigger
ecosystem

25. ./personas/product_own
er.yml
include:
- signed in user
- registered user
about: represents the stakeholders and
the business
goals:
- have control and overview of product
building ...
motiviations:
- build great product
points_of_pain:
- delays in delivery

26. @__login::sign_up
Feature: Sign up
In order to get access to protected
sections of the site
As a registered user
I want to sign up
Scenario: Visitor signs up with invalid
data
...
Scenario: Visitor signs up with valid data
...

28. feature "Homepage", %q{
To update requirement for project
product owner
should be able to change feature content} do
scenario "should show past event if no upcoming" do
title, description = "Beer chess", "Happy drinking"
at_time 1.month.ago do
@website.has(:event, :title => title,
:description => description)
end
@user.visit(homepage)
within "article.event" do
@user.should_see(title, description)
@user.should_see_translated("events.last_event")
end
end

29. # To update requirement for project
# product owner
# should be able to change feature content
## page: homepage
## developer: ps
feature "Homepage", :milestone => '0.1' do
# Given one month ago event was entered
# When user open homepage
# Then she should see this event on top
## wireframe: http://justproto.com/....
scenario "should show past event if no upcoming",
:iteration => 'one', :status => 'done' do

31. ?

32. Contact info:
Mail michalczyz@gmail.com
Twitter cs3b
Tools and usefull resources:
https://github.com/aslakhellesoy/cucumber/wiki
https://github.com/cs3b/cucumber_fm
http://demo.cucumber.fm/documentation/features
https://github.com/cavalle/steak
https://github.com/cs3b/steak_fm
Source of steak example
[28] https://github.com/drugpl/drug-site/blob/master/spec/acceptance/homepage_spec.rb
Font:
http://www.fontsquirrel.com/fonts/TitilliumText
Pictures
[3,6] http://www.selleo.com
[9,10] selleo – Rafał Bromirski
[14,15,17,18] http://demo.cucumber.fm
[20] selleo – Rafał Bromirski
[23] from redmine
[24] http://www.dreamstime.com/royalty-free-stock-photos-happy-with-laptop-image6621668
[26] http://www.dreamstime.com/royalty-free-stock-image-steaks-on-the-grill-image5835086