Sideboard provides a patch_session function which plugins can use in their unit tests to swap out their database for SQLite. We use the connection string sqlite:////tmp/test.db (this should possibly be configurable but I'll leave that for another ticket), but apparently that connection string means that systems which have sqlite2 instealled will use that over sqlite3. If we want to force sqlite3, we need to say sqlite+pysqlite:////tmp/test.db instead. I tried this and it worked fine, letting me use some sqlite3 features I needed in my MAGFest tests.
Now that I'm back from vacation I'll try to roll out the new release of rpctools this week, make sure the unit tests pass for the pull request on #63 and then merge that pull request so I can start making other pull requests for these lesser features/fixes.
Sideboard provides a
patch_session
function which plugins can use in their unit tests to swap out their database for SQLite. We use the connection stringsqlite:////tmp/test.db
(this should possibly be configurable but I'll leave that for another ticket), but apparently that connection string means that systems which have sqlite2 instealled will use that over sqlite3. If we want to force sqlite3, we need to saysqlite+pysqlite:////tmp/test.db
instead. I tried this and it worked fine, letting me use some sqlite3 features I needed in my MAGFest tests.Now that I'm back from vacation I'll try to roll out the new release of
rpctools
this week, make sure the unit tests pass for the pull request on #63 and then merge that pull request so I can start making other pull requests for these lesser features/fixes.