Hi all,
During the past couple months, I've ended up creating a
"persistence" test framework in order to do 2 things:
1. be able to run tests on other db's (oracle, db2, postgresql)
2. test the backwards/forwards compatibility of the data jBPM/Drools
writes to the database
All of this code has now been moved to the drools-persistence-jpa
jar, in the org.drools.persistence.util and
org.drools.marshalling.util packages. It's been moved there so that
I can include the test-jar in places where adding the
jbpm-persistence-jpa dependency would cause a problem, and also
because I end up using it in drools tests as well (DRY.. ).
But I can very easily imagine that people setting up tests just want
to set the test up, and not also deal with some complicated "hobby"
util that someone else wrote, so to speak. On the other hand, in the
course of testing and solving database and marshalling bugs, I end
up converting lots of tests to use the framework so that I can do 1.
and 2. (above).
To that end:
- If you have any tips, wishes or ideas about how you would
like a persistence test util to work, please share them!
The more tests that use both, the easier it is for me (us?) to catch
bugs and fix them.
Thanks!
Marco
--
jBPM/Drools developer
Utrecht, the Netherlands