title: some basic questions on testing or unit testing
body: <p>So usually my apps are very small and my test framework is just a console project. . I add classes in there with static methods and test my code. I find this approach to be pretty straightforward and nice (especially since you can see the output delivered)</p>
  
  <p>I have a nice little test project in visual studio now, so I was a little confused about how you would test things that don't seem <em>unit like</em>, for example :</p>
  
  <pre><code>Purchase.LoadAllAsync()//finished loading on the loadcomplete event
  </code></pre>
  
  <p>What kind of unit test would I write for this? Especially because this would change based on whats in the database? </p>
  
  <p>I did some scouting on SO and found this :
  <a href="https://stackoverflow.com/questions/1257560/when-is-a-test-not-a-unit-test/1257583#1257583">When is a Test not a Unit-test?</a></p>
  
  <p>Which confused me further, if a test is not a unit test, how would you test it? </p>
  
  <p>Sometimes I usually just write a small test function in the main form, or mainpage in silverlight and then just delete it off. But I guess unit testing is used because the tests need to stay there so you can re-use them right?</p>
  
  <p>Im sorry if im a little too ignorant! =P<br>
  Thanks</p>
  
  <p><strong>Update</strong></p>
  
  <hr>
  
  <p>Also wanted to add:  What about tests that run fine in the application itself, but when called from external code it fails. (This has happened to me a couple of times) Does it happen to you guys too and/or does it mean bad design?</p>