I'm building a no bs esign product, with api access by default. At a previous company, automating this stuff cost us an arm and a leg and we got locked into a bad contract. I've always been on the engineering side of things and never had the opportunity to learn how to find customers and sell. It's been a fun and rewarding experience for me. https://www.sign-n-post.com/
Depends on how fast you need them to be. I've had success using docker postgres , set up the same as production, where each test creates a connection to it's own test specific database, or is written to run inside a transaction that can clean up after itself using a shared database. In my experience, slower tests that use a real db almost always save net positive dev time.
reply