In tests, I want to provide a SQLite connection that looks like SupportSQLiteDatabase but doesn’t require an Android Context. SQLDelight is the library I’m using actually, and I’m using the AndroidSqliteDriver. That library has a JDBC driver, but they’re quite different in practice (specifically related to caching, which I realize even in my proposed scenario the SupportSQLiteDatabase implementation would have to simulate/mimic behavior/implementation).
The other piece to this puzzle is that I want to use a SQLite compiled with json1, which is easy to do in Android (requery/sqlite-android), but in unit tests loading that .so is difficult/impossible but is doable using other jvm/JDBC based distributions. With a SupportSQLiteDatabase wrapper, I can have AndroidSqliteDatabase use the JDBC connection in tests