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

When I do code review I always review the tests first. If they look through and reasonable then I can be a lot less careful reviewing the rest.


Tests never cover everything so exactly what are you looking for?


For example, just check the list of units, see that there is one for a happy flow, but none for error flow. Check that a number of tests correlates well with apparent cyclomatic complexity of the code. Check that tests are actually defining and testing relevant behavior and not just "I called method A, dus the method B was called".




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: