New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update tests #61
Update tests #61
Conversation
…ions can require some time to be applied by backend, and this template method can be overriden by subclasses to do something. Do nothing by default. Remove VOMongoTestResource: it's risky to share isntance of repository since some tests set options that can affect other tests. A repository can be created for each test run, it's not slow. I moved the code into VOMongoTest.
1 second! is not that A LOT??? |
Ah... I thought I wrote something like 100 milliseconds. I'll change it. |
It's 50ms now |
now we are talking about :) |
waitForWriteOperation | ||
"Write operations can be performed in a fire-and-forget mode, and it's convenient to wait a bit to ensure mongodb performed it before asserting on the results." | ||
|
||
50 milliSeconds wait |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again you can use >>#command: with getLastError and force a sync? Then the last write/delete/op must have succeeded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 this can be the next step
Two changes in this PR:
--> Question: Does anybody use VOMongoTestResource>>mongoHost: to customize the mongodb address? I moved it to VOMongoTest (class side, obviously).