here's my choice of gems (my toolset):
# authentication
gem 'devise'
# http calls to external api's
gem 'restfulie' # or
gem 'http_party'
gem 'curb'
# performance management
gem 'newrelic_rpm'
"There is a pleasure in the pathless woods,
There is a rapture on the lonely shore,
There is society, where none intrudes,
By the deep sea, and music in its roar:
I love not man the less, but Nature more."
- Lord Byron, Childe Harold’s Pilgrimage
on a recent project we used cucumber extensively for functional testing of our rails app using selenium webdriver to run it in the browser. all of us are convinced that it's a great tool, but there are many a things worth keeping an eye on otherwise it can lead to pain.
here i list top gotchas that we targetted and brought sanity back; but before i start, i'd like to point-out that these problems arise from the misuse of the freedom that cucumber gives us. cucubmer scenarios are plain english, and hence there are as many styles of writing scenarios as there are members on the team and that trickles down to steps as well.
