-
the thing about testing is... often i am writing the kind of code where i am more interested in iterating on the behaviour of the code than i am in iterating on the implementation of the code @v21/1491357614554619904Look on archive.org
♻️ 1 Retweets ❤️ 19 Favorites Mood +4 🙂
-
things that have worked for me: - use a language with a type system :) - use asserts in your code - if there's any easy way to do it... monkey test with random inputs & see if you hit any errors - bonus points: play back recordings of monkey tests that hit errors in the pastPermalink Look on archive.org
-
i mean, also the reason that "iterating on the behaviour" is possible is usually because the code is heavily entangled with a framework/engine that's doing the heavy lifting. the logic separated from that framework is not complicated - the entanglement is the thing.Permalink Look on archive.org