I think you're right. There's no alternative to an integration/e2e style test.

I was noodling around writing tests for some of the sql functions today but didn’t come up with any great ideas that didn’t require spinning up the DB and executing against it. That would make the test suite heavier to execute than preferred, IMO.

Maybe it’s not the worst thing, though. Seed some users. Write test cases that create items, zap, and verify expected wallet states. 

WeAreAllSatoshi

Thanks! I definitely need a process.

I think once we get some tests on the wallet stuff, no release should require much time to be confident in.

k00b

Daily discussion thread

saloon

Let me know if there’s something I can do as a contributor to help this process. 

One idea could be to group all the small PRs together and release those relatively quickly, then go in and do the meatier ones over longer time periods to give you more confidence 