Borrowchck: "we built a machine that can detect both race conditions & memory problems." Proptest: "we built a machine that can simulate thousands of unit tests a second, and if it finds a bug it provides all the information needed to reliably recreate it."
-
Show this thread
-
Replying to @yoshuawuyts
At work you’re probably writing app (not lib) code and I’m still not sure which parts of an app are good for being prop tested.
1 reply 0 retweets 1 like -
Replying to @laduke13
That's a really good question! On the one hand it's probably a good idea to write as much lib code as you can. Even in a company setting But for app code testing a combination of network splits, circuit breakers, random payloads, and IO throttles should get quite far
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @laduke13
Now there isn't too much software out there geared towards testing this quite yet. But there totally could be! Ask questions like: "What should happen if our Postgres backend goes down halfway at the start of a request, but comes back up once we need to write to it."
1 reply 0 retweets 1 like
"what's the behavior if our application is saturated? How do we shed load?" "What happens if the power cuts while we're writing to the database? At which point do we consider a request successful?" "What happens if we get a malformed payload?" Ask questions, simulate scenarios
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.