Project descriptions

[learnstream]

You'll need to do a migration. Suggested resource: http://ruby.railstutorial.org/chapters/modeling-and-viewing-users-two#sec:password_migration See also http://ruby.railstutorial.org/chapters/rails-3-1#sec:reversible_migrations

• Add description field to projects spec
• Add description-visible scenario to projects cucumber
• Do database migration

[krivard]

Writing the cucumber test has been totally kicking my ass. No idea what's proper here.

[ryanmuller]

I think I have a book on Cucumber -- I'll put reading that on my list, and I can pass it on if it's good.

Here are some things you may want to read in the meantime. Also if you commit stuff I can review it, though I still consider myself a beginner also.

• http://elabs.se/blog/15-you-re-cuking-it-wrong
• http://mislav.uniqpath.com/2010/09/cuking-it-right/
• A big set of examples, though better to avoid the hard-coded ids (as explained in the blog posts): https://github.com/diaspora/diaspora/tree/master/features

Probably the easiest way to think to about it is that a completely non-programming interaction designer should be able to write the feature files and you fill in the step definitions. So think of each thing as real actions a user would take in the browser.

And remember we can always refactor. So making very specific step definitions is fine -- if we notice patterns later, we can then cut down the repetition.