No Stupid Questions (Developer Edition)

1047 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 3 months ago* (last edited 3 months ago) by 3rr4tt1c@programming.dev to c/no_stupid_questions@programming.dev

17 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

[–] wesker@lemmy.sdf.org 5 points 3 months ago* (last edited 3 months ago)

It's my opinion that typically all published apps should employ automated testing, in the form of unit tests, integration tests, and so forth.

As far as logs and print statements go, it probably depends on the context. Like, useful feedback and debug logs are usually good. But step by step test logs not so much, especially if the end user will be inundated by them.