title: Acceptance Tests vs Unit Test Examples
body: <p>OK, so I have been trying to look at information on testing, different testing libraries what not and so forth.</p>
  
  <p>It seems to me that people always clearly define the difference of these test as one being high level and one being low level.  And that a properly tested out application would contain both style tests as well as integration test, etc. etc.</p>
  
  <p>But it seems like every article about the test types ends with something like "in practice it could be hard to see what the difference actually is".  I find it weird that people seem so preachy that you must have both test to even reach any sort of full code coverage and at the same time not have any good info/examples on what each might look like.</p>
  
  <p>I am asking because I am starting a new project, that promises to be much bigger and more involved than anything i have done in the past.  I would like to keep a good workflow with my test and make sure I am not creating gaps in my testing as I go (in the past projects have been small, and any gaps I might have had don't seem to cause any major issues in production that weren't simple t0 correct)</p>
  
  <p>I know that it seems a good Acceptance Test, naturally leads you to your unit test and once you get it, it is this magical thing that happens and your development life because just that much more blissful.</p>
  
  <p>Anyway, does anyone know of any good discussions on getting started on a good testing workflow, one that talks about moving between your acceptance/integration tests to you unit test and what not.  </p>
  
  <p>example for .net would be great, but since most testing frameworks cucumber(gherkin)/rspec etc. are all meant to be fairly readable any example should be good.</p>