http://nutrun.com/weblog/guice-module-testing-made-harder-than-it-should-have-been/ nutrun Thu, 04 Dec 2008 07:28:54 +0000 http://wordpress.org/?v=2.6.5 http://nutrun.com/weblog/guice-module-testing-made-harder-than-it-should-have-been/#comment-271 Kevin Bourrillion Tue, 13 Mar 2007 15:00:21 +0000 http://new-site.nutrun.com/?p=85#comment-271 man, lately I am really determined that my blog be a ".org" ... very strange. man, lately I am really determined that my blog be a “.org” … very strange.

]]> http://nutrun.com/weblog/guice-module-testing-made-harder-than-it-should-have-been/#comment-270 Kevin Bourrillion Tue, 13 Mar 2007 14:59:21 +0000 http://new-site.nutrun.com/?p=85#comment-270 I'm very curious about this. Do you see a lot of value in testing your Module class itself? In our app we unit-test our implementation classes (no Injector involved), we have some small "layer tests" (for lack of a better term) which construct custom simple Injectors so as to test a handful of classes working in concert, and then we have functional tests of our whole application using the production Injector. It would have never occurred to us to try to write a test for the Module itself; we'd see that as time that could have been spent testing something more likely to break. I’m very curious about this. Do you see a lot of value in testing your Module class itself? In our app we unit-test our implementation classes (no Injector involved), we have some small “layer tests” (for lack of a better term) which construct custom simple Injectors so as to test a handful of classes working in concert, and then we have functional tests of our whole application using the production Injector. It would have never occurred to us to try to write a test for the Module itself; we’d see that as time that could have been spent testing something more likely to break.

]]>