MongoDB implementation tests should clean up after themselves

[laserval]

The tests in hydra-mongodb leave empty or small databases in mongodb after they have run.

It appears to be a problem with how the cleanup methods are run by the maven surefire plugin, or by jUnit - running each test individually usually cleans up properly. Perhaps @AfterClass is problematic for the runner?

[laserval]

This might be one cause of #179

[rgraneru]

Could be one of the reasons, but I have had this problem after cleaning the
db too.
Den 19. apr. 2013 16:16 skrev "Olof Nilsson" notifications@github.com
følgende:

This might be one cause of #179#179

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/193#issuecomment-16655279
.

[remen]

I've seen (and fixed) some bugs in the tests themselves, where the test
assumed that the database would be empty. Mongodb isn't cleared between
each test method, only between classes in most test suites. Test method
order is not guaranteed. I think it would be worth it to clear the database
between each test method (i.e. in a @rule or @before). If this makes
running the unit test suite too slow, then perhaps we should use more
database mocks for the unit tests and move some other tests to integration.
I dunno, testing is tricky business...

/Petter

On Fri, Apr 19, 2013 at 5:14 PM, Roar Granevang notifications@github.comwrote:

Could be one of the reasons, but I have had this problem after cleaning
the
db too.
Den 19. apr. 2013 16:16 skrev "Olof Nilsson" notifications@github.com
følgende:

This might be one cause of #179<
https://github.com/Findwise/Hydra/issues/179>

—
Reply to this email directly or view it on GitHub<
https://github.com/Findwise/Hydra/issues/193#issuecomment-16655279>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/193#issuecomment-16659078
.

[laserval]

Currently it seems only on test leaves behind a database; MongoDocumentIOIT.