Comments on: My Defect Fixing Process http://www.basilv.com/psd/blog/2006/my-defect-fixing-process Wed, 16 May 2012 04:03:57 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Abhishek http://www.basilv.com/psd/blog/2006/my-defect-fixing-process/comment-page-1#comment-60442 Abhishek Mon, 25 Aug 2008 03:18:59 +0000 http://www.basilv.com/psd/blog/2006/my-defect-fixing-process#comment-60442 Regression testing should be included in the context Regression testing should be included in the context

]]> By: Chris Wash http://www.basilv.com/psd/blog/2006/my-defect-fixing-process/comment-page-1#comment-57927 Chris Wash Thu, 31 Jul 2008 21:09:32 +0000 http://www.basilv.com/psd/blog/2006/my-defect-fixing-process#comment-57927 I like this process. W/R/T Mike's comment, IntelliJ's structural search (& replace) makes this idea of finding recurrences quite compelling. See: http://www.jetbrains.com/idea/documentation/ssr.html Also, from what I remember Chapter 4.6 of "Test Driven" by Lasse Koskela is another good resource for activities involved in making maintenance changes (applied specifically to legacy code). Link: http://www.manning.com/koskela/ I like this process.

W/R/T Mike’s comment, IntelliJ’s structural search (& replace) makes this idea of finding recurrences quite compelling. See: http://www.jetbrains.com/idea/documentation/ssr.html

Also, from what I remember Chapter 4.6 of “Test Driven” by Lasse Koskela is another good resource for activities involved in making maintenance changes (applied specifically to legacy code). Link:
http://www.manning.com/koskela/

]]> By: Basil Vandegriend http://www.basilv.com/psd/blog/2006/my-defect-fixing-process/comment-page-1#comment-418 Basil Vandegriend Sun, 25 Jun 2006 23:22:39 +0000 http://www.basilv.com/psd/blog/2006/my-defect-fixing-process#comment-418 I agree - looking for other occurances is a very useful thing to do. I did mention this in point #5 "Learn from the defect", but perhaps it should have gone under point #6. I agree – looking for other occurances is a very useful thing to do. I did mention this in point #5 “Learn from the defect”, but perhaps it should have gone under point #6.

]]> By: Mike Totman http://www.basilv.com/psd/blog/2006/my-defect-fixing-process/comment-page-1#comment-413 Mike Totman Sun, 25 Jun 2006 21:24:57 +0000 http://www.basilv.com/psd/blog/2006/my-defect-fixing-process#comment-413 One other thing that you could put in point #6 "Act on my learning" : Look for other occurences of that error. If that error is an easily searchable pattern or commonly occurring idiom, search out other cases of similar code and see if they suffer from the same defect. This is the approach the OpenBSD team applies to eradicate whole families of defects which lead to vulnerabilities. e.g. buffer overflows. One other thing that you could put in point #6 “Act on my learning” : Look for other occurences of that error. If that error is an easily searchable pattern or commonly occurring idiom, search out other cases of similar code and see if they suffer from the same defect.

This is the approach the OpenBSD team applies to eradicate whole families of defects which lead to vulnerabilities. e.g. buffer overflows.

]]>