WhyTestGetAndSetMethods

Get and Set methods are too easy to test. Or are they? Ever had a NullPointerException? from a getThing()?

Think VisitorPattern? instead? See UseVisitorPatternInsteadOfGetAndSetMethods.

Ok, so er WhyTestGetAndSetMethods ? -- Richard

So one answer seems to be, avoid the need for Get and Set methods at all. Question every time you write a get or set method. Would a VisitorPattern? prevent domain leakage? -- PaulS ³host³³date³May 22, 2000³agent³Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)³WhyTestGetAndSetMethods