Hacker News new | ask | show | jobs
by syngrog66 1820 days ago
you run it. look at the results or output. like the stdout, or a file it changed, or in a REPL or debugger. depends on situation
2 comments

Yeah I‘m not sure that‘s how software engineering should work.

Tests should prove a desired behaviour. Sometimes it‘s not possible to fully run code until late in some staging, just because there are a lot of dependencies and conplexity. That‘s what tests are for (on various lebels of abstraction).

I think it depends on the task. Some code we write is so simple and only used a few times that you don’t need tests.
Sounds laborious to manually check edge cases each time you change that code or its dependencies. I'd rather just write a test.