The downside of that is that it makes the tests significantly slower Also it isn't the case that every test needs an isolated DB, there are sets of tests that create a DB and then use it over multiple individual tests
I think the best suggestion I've seen so far is that of tweaking the TDB setup to use a smaller block size for the tests, the downside of that is then you aren't testing exactly what end users will be using in the wild Rob On 12/03/2015 11:38, "Claude Warren" <[email protected]> wrote: >First let me start with a disclaimer: I do not run windows, I have not >attempted to run the windows TDB tests, I have only followed the >conversation tangentially. > >My understanding of the testing issue is that Windows does not release the >disk space associated with memory mapped files until after the JVM exits. > >Q: Is it not possible to add a configuration option to Maven that causes >those tests to be run in a different JVM. When the test finishes the JVM >should clean up the files. Not sure if that makes sense but a discussion >of how to configure Maven to do the new JVM per test is found here: >http://stackoverflow.com/questions/6813373/how-to-tell-maven2-to-execute-j >unit-tests-one-by-one-each-in-new-jvm-instance > >Claude > >-- >I like: Like Like - The likeliest place on the web ><http://like-like.xenei.com> >LinkedIn: http://www.linkedin.com/in/claudewarren
