Write tests. Not too many. Mostly integration (2017)

Re:Write tests. Not too many. Mostly integration (2017) by atom_arranger on Thursday January 31, 2019 @08:16PM (#19050779)

If you have a user facing component that uses utility functions, let's say a component that shows a table with a sum (that uses a utility function). Then refactoring your sum function should not break your tests of the table component.

I'm not saying you shouldn't test your sum function using unit tests, but ultimately users don't care so much about the sum function, they care that they have a table, and it should show a sum, and so that functionality should be tested.

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration (2017) by kurtisc on Thursday January 31, 2019 @11:50PM (#19051665)

Users care if the table is broken because it's taking too long to find the bug from endpoint-only tests

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration (2017) by Aeolun on Friday February 01, 2019 @06:58AM (#19053407)

Your endpoint test would presumably make sure the table is working.

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration (2017) by kurtisc on Saturday February 02, 2019 @03:15AM (#19061843)

That's what I'm saying. But it only tells you that it is broken, not why. Users don't use tests, tests are for the developers.

[ Parent | on HN ]