Message-ID: <1608019648.41103.1371638205486.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_41102_1145326587.1371638205486" ------=_Part_41102_1145326587.1371638205486 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When Ashcroft fails a test, you will see that the recommended solution o= ften involves a refactoring towards dependency injection. Fine, that (with = the aid of Mock Objects will allow y= ou to test your class in isolation. But what about integration tests? Or ev= en the whole application? How do you assemble the real cla= sses (including these low level ones) that actually do acc= ess files, sockets, threads and graphics environments?
There are several ways. You can do it manually in some bootstrap class, = or you can use PicoContainer/NanoContainer or some other DI framework such = as Spring or HiveMind. It's up to you. These frameworks will make that asse= mbly easy, as long as your classes honour DI.------=_Part_41102_1145326587.1371638205486--