title: Beginning TDD - Challenges? Solutions? Recommendations?
body: <p>OK, I know there have already been questions about <a href="https://stackoverflow.com/questions/4303/why-should-i-practice-test-driven-development-and-how-should-i-start">getting started with TDD</a>.. However, I guess I kind of know the general concensus is to <em>just do it</em> , However, I seem to have the following problems getting my head into the game:</p>
  
  <ul>
  <li>When working with collections, do will still test for obvious add/remove/inserts successful, even when based on Generics etc where we kind of "know" its going to work?</li>
  <li>Some tests seem to take forever to implement.. Such as when working with string output, is there a "better" way to go about this sort of thing? (e.g. test the object model before parsing, break parsing down into small ops and test there) In my mind you should always test the "end result" but that can vary wildly and be tedious to set up.</li>
  <li>I don't have a testing framework to use (work wont pay for one) so I can "practice" more. Are there any good ones that are free for commercial use? (at the moment I am using good 'ol <em>Debug.Assert</em> :)</li>
  <li>Probably the biggest.. Sometimes I don't know what to expect <em>NOT</em> to happen.. I mean, you get your green light but I am always concerned that I may be missing a test.. Do you dig deeper to try and break the code, or leave it be and wait for it all fall over later (which will cost more)..</li>
  </ul>
  
  <p>So basically what I am looking for here is not a " <em>just do it</em> " but more " <em>I did this, had problems with this, solved them by this</em> ".. The <strong>personal</strong> experience :)</p>