Interesting point, but i prefer measuring the performance on a system
level rather than down in my unit tests, and to write very quick unit
tests when I can.
In this case it was more interested in getting rid of the need to do
anyting in my tearDown and/or setUp methods. I usually prefer to get
ri
We setup an fs based graph on the jvm java.io.tmp folder and destroy
on every setup() teardown() if necessary.
This is how all of our unit tests run and it works fine.
An in memory store may give you a false view on how things work if one
of the things you are testing is performance, specially in t
2010/2/26 Hans Brattberg :
> Hi!
>
> For test automation it could be useful to create an instance of
> EmbeddedGraphDatabase that don't use the file system, but only keep
> the data in memory, in the same way hsqldb can be configured.
>
> Is there another version of EmbeddedGraphDatabase for that p
Hi!
For test automation it could be useful to create an instance of
EmbeddedGraphDatabase that don't use the file system, but only keep
the data in memory, in the same way hsqldb can be configured.
Is there another version of EmbeddedGraphDatabase for that purpose, or
has any one a solution fort
4 matches
Mail list logo
