No Stupid Questions (Developer Edition)

1014 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 [email protected]

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

founded 2 years ago

MODERATORS

LinearArray

Is it okay to leave tests in your code? (self.no_stupid_questions)

submitted 1 week ago* (last edited 1 week ago) by 3rr4tt1c to c/no_stupid_questions

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

[–] [email protected] 1 points 1 week ago

(Guessing JS / TS) I look after a moderately sized app, and still find console.log() useful sometimes. They are all protected by a Boolean, so we have authLog && console.log('something about auth') and the bools are all set in one global file. So turning debug logging on and off is very simple.

The best thing is that when it's off, the bundler strips all the console log lines from the source, so they're not even there-but-inactive in production.