Today I came across this link on IT Conversations to the presentation by Kent Beck on Developer Testing. The presentation was recorded at the Developer Testing Forum held in Palo Alto, California, November 17th, 2004.
In his presentation Kent mainly talks about Developer Accountability and Software Health vs Software Quality. He also explains "How Developer testing is a simple way for developers to become accountable".
Some of his statements:
- "Developer Testing is something you can do today to improve the health of your system"
- "The only person that can be responsible for health is you, not anyone else"
- "Substantial improvements in the health of your software can happen when you begin to write developer tests"
- "To gain the full benefits of your developer tests, they must be run very frequently"
- "Developer testing leads to accountability which then helps you build trust with other people, including your team members, manager, your project sponsor, and most importantly, your customers"
Notes:
Check also Dominique Plante nice wrap-up on his talk.
Kent also has a particular view on the release process at Microsoft!
Kent Beck is widely recognized as the father of eXtreme Programming and JUnit. Kent's other contributions to software development include patterns for software, and the rediscovery of test-first programming. He is the author/co-author of Extreme Programming Explained: Embrace Change 2nd Edition, Contributing to Eclipse, Test-Driven Development: By Example, Planning Extreme Programming, The Smalltalk Best Practice Patterns, and the JUnit Pocket Guide. He received his B.S. and M.S. in Computer Science from the University of Oregon.
[Via Joel Ross] Clean Sources is a little tool that adds an explorer shell menu to folders. Clicking "Clean Sources" allows you to clean your source directory: it recursively deletes the contents of the bin, obj and setup folders.
This is useful if you want to remove all unnecessary files from your projects before sharing it with others, or when adding it to your sourcecontrol system.
On a recent project a co-worker, Roy Dictus, created a similar tool which - besides deleting the bin and obj folders - also deleted all SourceSafe related files (*.scc, *.vsscc, ...) from the .NET solution and projects we were working on. We used this tool to clean up the projects before adding them to the release branch of our sourcecontrol system. What about merging the functionality of both tools?
[Updated] Roy decided to make this utility tool, which I mentioned above, freely available for download. Get Cleanup 1.5 for Visual Studio.Net 2003 Solutions here. Thanks Roy!