I'd say that is an architecture problem up to a point. A test does not need any ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

fsloth on Feb 14, 2018 | parent | context | favorite | on: What I wish I knew when I became CTO

I'd say that is an architecture problem up to a point. A test does not need any framework. Simply a defined output for a defined input, and then check whether the output matches expectations.

millstone on Feb 14, 2018 [–]

In this sort of scenario, the bugs lie in the expectations themselves. Tests that don’t account for that are dead weight.

icebraining on Feb 14, 2018 | [–]

Can you expand on that? Because I don't see how a test can account for the faulty expectations of the person writing it.

Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact