Comments on: When Writing Developer Tests, Take on Account that the JRE Is Another Leaky Abstraction http://kaksles.org/2007/08/25/when-writing-developer-tests-take-on-account-that-the-jre-is-another-leaky-abstraction/ Reflections of programming as a real-world activity. Tue, 11 May 2010 16:19:37 +0000 hourly 1 http://wordpress.com/ By: Eugene http://kaksles.org/2007/08/25/when-writing-developer-tests-take-on-account-that-the-jre-is-another-leaky-abstraction/#comment-1779 Wed, 22 Oct 2008 23:34:34 +0000 http://kaksles.org/2007/08/25/when-writing-developer-tests-take-on-account-that-the-jre-is-another-leaky-abstraction/#comment-1779 Nice article. Thanks. :) Eugene

]]> By: Markus Hjort http://kaksles.org/2007/08/25/when-writing-developer-tests-take-on-account-that-the-jre-is-another-leaky-abstraction/#comment-1195 Sun, 26 Aug 2007 12:13:45 +0000 http://kaksles.org/2007/08/25/when-writing-developer-tests-take-on-account-that-the-jre-is-another-leaky-abstraction/#comment-1195 I guess Ville proposed this idea because we used to use different JRE for our unit tests in our last project. JRE 6.0 was used for tests, while production server was JRE 1.4.2. Although, we had different JRE for unit tests, we did run all higher level tests with same JRE as used in production. So we actually had three different modules: for production code, for unit tests and for integration tests. I know that it is a bit complex setup, but for us it worked pretty well.

And I totally agree with your point. Project’s continuous integration environment should be very similar with production environment. So you should use same JRE if it is possible.

]]>