Testing your app on a budget

Re:Testing your app on a budget by leeoniya on Tuesday March 29, 2016 @10:32AM (#11381707)

i have found that dogfooding and acceptance tests (tracking regressions), combined with focused source commits are the most practical.

while unit tests laser in on specific problems, they are often unnecessary and with frequent commits and sensible commit messages, the causes of problems are always trackable and nearly always obvious.

git bisect helps in situations where the commit count is high (in large teams).

[ Parent | on HN ]

Re:Testing your app on a budget by fweespee_ch on Tuesday March 29, 2016 @10:45AM (#11381808)

I mostly agree with you. I've found unit tests shine in refactors simply because you are often refactoring for performance and/or bug extraction so the overall functionality of a given unit of code is largely identical to the previous version.

However, outside of refactoring, I've never found them to be cost effective time wise compared to other automated testing options.

[ Parent | on HN ]

Re:Testing your app on a budget by Aleman360 on Tuesday March 29, 2016 @11:40AM (#11382249)

Yea, unit tests for messy logic and algorithms.

Integration tests for complicated scenarios.

Extensive dogfooding for the UI.

[ Parent | on HN ]