OK, I think I just answered myself...
[junit] Running
org.waveprotocol.box.server.persistence.mongodb.AccountStoreTest
[junit] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.12 sec
[junit] TEST
org.waveprotocol.box.server.persistence.mongodb.AccountStoreTest FAILED
[junit] Running
org.waveprotocol.box.server.persistence.mongodb.AttachmentStoreTest
[junit] Tests run: 9, Failures: 9, Errors: 0, Time elapsed: 0.016 sec
[junit] TEST
org.waveprotocol.box.server.persistence.mongodb.AttachmentStoreTest FAILED
[junit] Running
org.waveprotocol.box.server.persistence.mongodb.CertPathStoreTest
[junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 0.044 sec
[junit] TEST
org.waveprotocol.box.server.persistence.mongodb.CertPathStoreTest FAILED
[junit] Tests FAILED
Is anyone against having an instance of Mongo DB instantiated and
destroyed when tests are run? I'm already assuming the developer doesn't
need to have Mongo DB already installed, as well.
PP
On 14/06/12 13:07, Paulo Pires wrote:
> Hi list,
>
> Has anyone here tried the Mongo DB persistence unit-tests?
>
> org.waveprotocol.box.server.persistence.mongodb.AccountStoreTest
> org.waveprotocol.box.server.persistence.mongodb.AttachmentStoreTest
> org.waveprotocol.box.server.persistence.mongodb.CertPathStoreTest
>
> Am I wrong to assume that you have to have a Mongo DB instance already
> running in order for these tests to pass? Or is it started and stopped
> by the test process as well?
>
> I'm asking this because if we need the Mongo DB instance running for
> tests, then it makes sense to instantiate a Mongo DB before the related
> tests are executed and to terminate it after that. And if this is true,
> I'll implement it at least in the current Maven effort
> (https://github.com/pires/wave/issues/8).
>
> Cheers,
>
--
Paulo Pires
