I completely agree. We usually just build all the tables once and
then just try to make sure all the objects are deleted at the end of
the test, but you are correct that this is sometimes more cumbersome
than it could be. An easy drop-then-create option would simplify
this, although some databases can be notoriously slow with schema
interrogation and manipulation that doing it for each test might wind
up being prohibitively slow.
On Jan 2, 2007, at 3:44 PM, robert burrell donkin wrote:
On 1/2/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
Unfortunately, we don't have any automatic drop-table feature, but I
agree it would be handy (you might want to make a JIRA report with
The only other recourse, I think, would be to just manually delete
the database files before running your tests.
support for easy integration testing is one area where i think many
JDO implementations could really improve
it's vital to start with a known database state and clean up after
each integration test. this isn't as easy as it should be when you
have a complex object-relational mapper with extensive caching. a set
of side doors for integration testing would really help productivity.