No Stupid Questions (Developer Edition)

1009 readers

1 users here now

This is a place where you can ask any programming / topic related to the instance questions you want!

For a more general version of this concept check out !nostupidquestions@lemmy.world

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

LinearArray@programming.dev

Is it okay to leave tests in your code? (programming.dev)

submitted 5 days ago* (last edited 3 days ago) by 3rr4tt1c@programming.dev to c/no_stupid_questions@programming.dev

18 comments fedilink hide all child comments

Like if I'm using print statements to test my code. Is it okay to leave stuff like that in there when "publishing" the app/program?

Edit: So I meant logging. Not "tests". Using console.log to see if the code is flowing properly. I'll study up on debugging. Also, based on what I managed to grasp from your very helpful comments, it is not okay to do, but the severity of how much of an issue it is depends on the context? Either that or it's completely avoidable in the first place if I just use "automated testing" or "loggers".

you are viewing a single comment's thread
view the rest of the comments

[–] jaxxed@lemmy.ml 2 points 5 days ago

This is pretty good ^

The idea that println has a a good way to test a s incorrect. It requires a testing interaction which should be avoided. Test behaviour at the exposed interface primarily, use logging/telemetry to discover dynamics.

The exceptions are reserved for scripty things (bash has poor logging,) ones offs (1x migration) or personal tooling.