A Alain Boss Apr 16, 2008 #21 Arne said: Believe it or not, but I have actually seen getters and setters being wrong after too much copy paste (it was not C# but that does not really matter). As a consequence I am paranoid enough to even make unit tests for that type of class. Arne Click to expand... Well, i have seen setters in legacy code that are longer than my arm too. In this case Unit tests are definitely called for. alain
Arne said: Believe it or not, but I have actually seen getters and setters being wrong after too much copy paste (it was not C# but that does not really matter). As a consequence I am paranoid enough to even make unit tests for that type of class. Arne Click to expand... Well, i have seen setters in legacy code that are longer than my arm too. In this case Unit tests are definitely called for. alain
B Ben Voigt [C++ MVP] Apr 17, 2008 #22 Arne said: Believe it or not, but I have actually seen getters and setters being wrong after too much copy paste (it was not C# but that does not really matter). Click to expand... These bugs should be found by the unit tests for the consumer classes.
Arne said: Believe it or not, but I have actually seen getters and setters being wrong after too much copy paste (it was not C# but that does not really matter). Click to expand... These bugs should be found by the unit tests for the consumer classes.
A Arne Vajhøj Apr 20, 2008 #23 Ben said: These bugs should be found by the unit tests for the consumer classes. Click to expand... Usually will. And if the consumer class is done by the same team at the same time, then no big deal. But another team taking a drop finding the bug 3 months later will not be pleased. Arne
Ben said: These bugs should be found by the unit tests for the consumer classes. Click to expand... Usually will. And if the consumer class is done by the same team at the same time, then no big deal. But another team taking a drop finding the bug 3 months later will not be pleased. Arne
