[ed_blackburn]

I'm using sqlglot to parse hundreds of old mysql back up files to find diffs of schemas. The joys of legacy code. I've found hypothesis to be super helpful for tightening up my parser. I've identified properties (invariants) and built some strategies. I can now generate many more permutations of DDL than I'd thought of before. And I have absolutely confidence in what I'm running.

I started off TDD covered the basics. Learned what I needed to learn about the files I'm dealing with, edge cases, sqlglot and then I moved onto Hypothesis for extra confidence.

I'm curious to see if it'll help with commands for APIs. I nothing else it'll help me appreciate how liberal my API is when perhaps I don't want it to be?

[groundhogstate]

You might find schemathesis useful for API testing (which IIRC is built on Hypothesis). Certainly helped me find a stack of unhandled edge cases.

YMMV, but once I first set up Schemathesis on one of my MVPs, it took several hours to iron out the kinks. But thereafter, if built into CI, I've found it guards against regression quite effectively.

[IanCal]

https://schemathesis.readthedocs.io/en/stable/

This looks really good. I like using hypothesis for APIs so this is a really nice layer on top, thanks for pointing this one out.

[agumonkey]

pretty nice tool, helped us poke into our app in ways we didn't foresee

also pretty happy to see the reports of thousands or api calls that matched the expected responses, that increases the confidence you have in your system