Parse, Don't Validate (2019)

Re:Parse, Don't Validate (2019) by syngrog66 on Saturday June 26, 2021 @04:10PM (#27645375)

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

[ Parent | on HN ]

Re:Parse, Don't Validate (2019) by chrisandchris on Saturday June 26, 2021 @04:21PM (#27645480)

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).

[ Parent | on HN ]

Re:Parse, Don't Validate (2019) by cortesoft on Saturday June 26, 2021 @04:43PM (#27645651)

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.

[ Parent | on HN ]

Re:Parse, Don't Validate (2019) by exdsq on Saturday June 26, 2021 @05:49PM (#27646224)

Sounds laborious to manually check edge cases each time you change that code or its dependencies. I'd rather just write a test.

[ Parent | on HN ]