title: Shoulda testing workflow from the trenches
body: <p>Everyone is talking about TDD (BDD) in Rails (and not just Rails) development world today. It's easy to find plenty of good general information about it, there are quite a few tools you can use for this purpose and there are many (good) examples of how to use them. </p>
  
  <p>Now, I'm already on the train. I like the idea (never did TDD before) and I decided to go for Shoulda (because it seems to me quite easy to understand). I read plenty of examples and have done some first tests. My problem is this: I'm just not sure if I'm doing it right. As I said, there are many tiny examples all over the net, but I haven't found any comprehensive guide covering overall workflow of TDD with Shoulda.</p>
  
  <p>Here are my questions:</p>
  
  <ul>
  <li>What is your way of practising TDD with Shoulda? (What is your usual workflow throughout one iteration?)</li>
  <li>What other tools do you use (except of Shoulda itself)? </li>
  <li>Any other tips?</li>
  </ul>