DEV Community

Discussion on: What are your biggest problems with unit testing?

Collapse
alexbunardzic profile image
Comment marked as low quality/non-constructive by the community. View Code of Conduct
Alex Bunardzic

This doesn't make any sense. If you are unit testing code by supplying input (domain) values and then checking/verifying/asserting the output (range) values, and if when tests run repeatedly you get different output values with identical input values, you know that something is terribly wrong with your design. You should never see that scenario, ever!

Collapse
bengreenberg profile image
Ben Greenberg • Edited on

I think you are responding to a different comment, since you are not responding to what I wrote. My point is exactly when input changes, it shouldn't break the test.

Thread Thread
alexbunardzic profile image
Alex Bunardzic

Sorry, probably misread your comment. Still not sure I understand how is it possible that a change in the input value breaks the test? Please explain.

Thread Thread
bengreenberg profile image
Ben Greenberg

If a test's expectation is linked to the exact desired output, then changing the input, for example, the wording in the hypothetical markdown file, will break the test. In my experience, this is something not to do, because it adds unnecessary fragility to the unit test. That's what I was saying.

Have a great weekend!

Thread Thread
rossdrew profile image
Ross • Edited on

Agree. That's a problem in general with unit testing infinitely variable textual values. It's almost never a case for unit testing if you end up trying.