I find that if an input doesn't affect the outcome of my unit test, it's usually a red flag that it's there at all. I try to refactor or add a factory method so that my test isn't responsible for creating irrelevant objects. For e2e or integration tests, there's more junk
Aggressive testing strategy: if an object or piece of data shouldn't affect the outcome of your test, fill it with random bytes.
-
-
-
Great insight- unnecessary vals in test often smell of unclear separation of responsibilities among classes/modules/functions
End of conversation
New conversation -
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.