does anyone have tips for reducing randomness in your programs while debugging? thinking of timing issues, random numbers, chaotic inputs, etc.

so far I have

- seed your RNG
- capture all input and run it a million times, and save the input once you find a version that fails
- use a record/replay debugger if you can (like rr)

Follow

@b0rk there is stryker (mutation testing). And there was also another one, can't remember the name, that would remove a single line from source then run the test suite (for every line).

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!