http://watchitlater.com/blog/2009/09/junit-tests-and-the-file-system/ A reluctant foray into the world of blogging. Thu, 17 May 2012 02:38:18 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://watchitlater.com/blog/2009/09/junit-tests-and-the-file-system/comment-page-1/#comment-5664 Writings of french geek Tue, 19 Jan 2010 21:40:47 +0000 http://watchitlater.com/blog/?p=46#comment-5664 I made a article about JUnit: Unit test except container J2EE with Spring and JNDI (here : http://bit.ly/798uHp )- The first solution consists in using the attribute defaultObject JndiObjectFactoryBean class which allows to change data source when call JNDI fails - The second consists in creating a class which will create for us context JNDI before using our services in the files of Spring configuration I made a article about JUnit: Unit test except container J2EE with Spring and JNDI (here : http://bit.ly/798uHp )- The first solution consists in using the attribute defaultObject JndiObjectFactoryBean class which allows to change data source when call JNDI fails – The second consists in creating a class which will create for us context JNDI before using our services in the files of Spring configuration

]]> http://watchitlater.com/blog/2009/09/junit-tests-and-the-file-system/comment-page-1/#comment-4687 Tom Sat, 26 Sep 2009 10:58:39 +0000 http://watchitlater.com/blog/?p=46#comment-4687 I've used the container approach previously as well with a good deal of success. I wonder how the rest of the rules that now come with JUnit will be used in the future. I’ve used the container approach previously as well with a good deal of success. I wonder how the rest of the rules that now come with JUnit will be used in the future.

]]> http://watchitlater.com/blog/2009/09/junit-tests-and-the-file-system/comment-page-1/#comment-4676 Felix Fri, 25 Sep 2009 21:10:44 +0000 http://watchitlater.com/blog/?p=46#comment-4676 Interesting one. I was recently thinking something along these<a href="http://wuetender-junger-mann.de/wordpress/?p=638" rel="nofollow">lines</a>. I.e. your test framework acts as a container, instead of having a huge number of annotations. Interesting one. I was recently thinking something along theselines. I.e. your test framework acts as a container, instead of having a huge number of annotations.

]]>