295 reputation
19
bio website
location France
age
visits member for 2 years, 9 months
seen Sep 9 at 14:13

May
30
awarded  Nice Question
Apr
19
awarded  Popular Question
Dec
15
awarded  Yearling
May
16
awarded  Teacher
May
10
awarded  Supporter
May
10
comment Should we always unit test bugs when correcting them?
well, indeed, in the end it's all about a balance between the time needed to maintain the test vs the time it would take for a noob to detect and correct the bug if it happened again.
May
10
accepted Should we always unit test bugs when correcting them?
May
10
comment Should we always unit test bugs when correcting them?
the refactor is about something else, and it is still possible in the new design to slightly modify the code and reintroduce the bug, which is what the test is watching. I guess an alternative to the test would be a comment in the code saying "don't fuck with this", but it sounds like the wrong thing to do :p
May
10
awarded  Nice Question
May
10
asked Should we always unit test bugs when correcting them?
Dec
22
awarded  Scholar
Dec
22
accepted Would you rather make private stuff internal/public for tests, or use some kind of hack like PrivateObject?
Dec
22
awarded  Editor
Dec
22
revised Would you rather make private stuff internal/public for tests, or use some kind of hack like PrivateObject?
example
Dec
22
awarded  Student
Dec
22
comment Would you rather make private stuff internal/public for tests, or use some kind of hack like PrivateObject?
See programmers.stackexchange.com/questions/77313/…
Dec
22
awarded  Analytical
Dec
22
asked Would you rather make private stuff internal/public for tests, or use some kind of hack like PrivateObject?