title: Unit testing with lots of use cases
body: <p>I am working on a java application which has a lot of use cases. Inputs to the application are different kinds of events occuring at different times. This kind of input gives rise to hundreds of test cases. Has anybody faced this kind of scenario? Do you make sure all the test cases are covered before making a release to the QA team?
  So my question is: what is the best approach for testing programs with lots of test cases? </p>