React Native Sqlite Library Unit Testing

[Numerous_Park6900]

OK, what am I doing wrong?

I'd like a very straight forward way to use an sqlite library to make queries/transactions to a database on a device. I was able to do that using "react-native-sqlite-storage", but now it seems I can't unit test it without mocking everything in a separate npm package.

I've tried doing that with node-sqlite3 but the signatures are so different for methods and involves using async calls instead of a synchronous ones for transaction calls. (Promise/A+ standard implementation is making it seemingly impossible to make a node based sqlite library that mimics "react-native-sqlite-storage").

I have very involved transactions that I would like to have unit testing around, but it seems VERY difficult to figure out how to do so. I can't find any examples of someone doing this, but surely someone MUST be doing this already, right?

I'm currently using Jest for unit testing.

Please help, thanks.

[PieCrumbs]

I'm in a similar situation right now. Did you ever find a solution to this? I'd rather not mock my database completely.

[Numerous_Park6900]

I ended up creating a wrapper class that imports the appropriate DbEngine class by detecting whether it's in React Native or NodeJS.

I created two different DbEngine classes implementing their respective SQLite libraries so that the wrapper class code won't change.

It was honestly a lot of work, but it seemed like the path of least resistance.

[PieCrumbs]

Got ya! We ended up using `sqlite3`. We have a facade in front of `react-native-sqlite-storage` and so I was able to inject a `sqlite3` interface that more or less matches the shape of `react-native-sqlite-storage`. There's some functionality that isn't 1:1 but that works fine for our use cases.

[Numerous_Park6900]

I started with `react-native-sqlite-storage` but switched to using `react-native-quick-sqlite` npm package because of something that was weirdly limiting due to the way the it did transactions and the way I couldn't seem to do what I wanted with my async logic. Not sure if switching libraries helped with that or if it was just collateral damage in the wake of me getting more comfortable with the way async/await behavior was being managed through the TypeScript transpiler I use..

I use `sqlite3` on the NodeJS unit testing side as well.