title: is it practically possible to do good TDD (or BDD) without using any DI framework in java?
body: <p>IMO one of the main characteristics of a good TDD is: testing your class (or actually unit) in isolation.</p>
  
  <p>When you do so, you are able to actually test single behavior in each test -- only one test will fall for a single problem you have.</p>
  
  <p>For this you first must verify that there are no static references from your class (including constructors AKA <code>new</code> keyword).</p>
  
  <p>in theory it is easy not to use any dependency injection framework and test your classes in complete isolation, for this you need to inject all dependencies in the constructor and create Factories classes that will call the <code>new</code> keyword.</p>
  
  <p>I found this theoretical MO to be too hard to actually do in practice. </p>
  
  <p>Am I missing something important in the process?</p>
  
  <p><strong>EDIT</strong>:
  I do think that we should all aim to one failure for one code change. it will never be perfect but it will get your code closer to there, people forget that test code is also maintainable code, <strong>specification of tested code changes</strong>.</p>
  
  <p>If you don't aim there you will end up deleting tests which is a poor solution</p>