Closed dragan closed 11 years ago
This could be a nice change. On a similar vein, we could add integration tests for the authorization key functionality, which are currently lacking because setting up the auth key requires the rethinkdb admin
command to be invoked.
Ideally the startup & shutdown would be done in a [SetUpFixture] in the Integration test namespace, that way the other unit tests don't require RethinkDB, and the startup and shutdown don't have to be done individual for each test fixture.
That was my thought as well. I should be able to work on this soon.
Instead of starting and shutting down RethinkDB in the build script before and after running the tests. Add the logic to the tests themselves to start/stop and cleanup after themselves.