Some times... ------------------------------------------------------------------------------- Test set: org.waveprotocol.box.server.persistence.mongodb.AccountStoreTest ------------------------------------------------------------------------------- Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.033 sec
------------------------------------------------------------------------------- Test set: org.waveprotocol.box.server.persistence.mongodb.AttachmentStoreTest ------------------------------------------------------------------------------- Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.019 sec ------------------------------------------------------------------------------- Test set: org.waveprotocol.box.server.persistence.mongodb.CertPathStoreTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.628 sec So you see, it's pretty fast to populate the database and run the tests. Cheers, PP On 14/06/12 14:54, Paulo Pires wrote: > On 14/06/12 13:18, Ali Lown wrote: >>> 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. >> How much of an overhead is that going to add to the running of the >> tests? Inutition suggests that instantiating a DB is going to be a >> pretty heavy job... > It will only take 30 seconds or a little less/more (depending on your > internet connection) to download the Mongo distribution for your > OS/arch. After that, database population, tests and shutdown take around > 15 seconds (Core 2 Duo 2.4 GHz, 4GB DDR2, SSD disk). > > On the other hand, GWT tests, for instance, take hours. Eventually, > tests should be profiled and executed only if the developer specifies so. > > Btw, just to clarify, I have only one Mongo DB instance for all tests > and not an instance per test. > >> Ali -- Paulo Pires
