Anyone have any patterns or tricks for managing tearing up/tearing down DB state in automated tests? I'm having fun hacking away at my toy app, but I haven't used XTDB much and I'm a bit leery of having no test coverage.
yeah, I've got a couple tests in the biff repo: https://github.com/jacobobryant/biff/blob/master/test/com/biffweb/impl/xtdb_test.clj
see test-node and get-context
Awesome, thanks!
Heh I just added an issue asking for documentation of this