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.
I think you're right. There's no alternative to an integration/e2e style test.
reply