> Imagine replicates being a thing you have to think about when debugging a program. Like in software, running your code again with no changes after it just failed is insanity.
This is a common requirement in software QA. "Can we reproduce the issue? Does it happen every time? Is it sensitive to timing of user actions, or anything else? What part of the initial state of the system could affect this outcome? What other external or environmental changes will alter the result?"
Sometimes, the initial failure seems to have an obvious answer, and sometimes an immediate code change is the best first move. But replicating a behaviour does is insanity.
This is a common requirement in software QA. "Can we reproduce the issue? Does it happen every time? Is it sensitive to timing of user actions, or anything else? What part of the initial state of the system could affect this outcome? What other external or environmental changes will alter the result?"
Sometimes, the initial failure seems to have an obvious answer, and sometimes an immediate code change is the best first move. But replicating a behaviour does is insanity.