Getting into Agile Development with .NET
Posted August 2, 2007on:
Following on from my previous post Getting into Agile Development with .NET.
Atlassian’s professional WIKI solution, it works great with JIRA and provides a really nice WIKI solution. For those who want to travel light with documentation, WIKI’s provide a nice fit for technical documentation, build documentation, internal designs, etc. as they easily accommodate rapid changes, are completely web based and allow for automatic version tracking.
Data Dictionary Creator
One of the principles of Agile is make your code self-documenting. What about making your database self-documenting? You can do this in SQL 2005 in T-SQL by adding meta-data and descriptions to each field in your database. The Data Dictionary Creator tool does the same thing through a nice GUI and allows for export and import of the documentation. You can then document your database and store the meta-data in source safe for version control and safe keeping. In addition, you can export the descriptions to an excel file for instant documentation!
Wisdom Screen Hunter
Not really a development tool, but how many times have you been creating documents and wanted a quick screen capture? Forget using the PrntScrn and fiddling in paint – use this tool. Its free and allows you to capture any arbitrary rectangular area as well as any active window. Simply hit F6 and off you go.
Some tools suggested by my readers.
A plug in for Visual Studio which really helps by reducing the amount of time and hassle of opening another environment or tool to run tests in, Launches the right out of your VS Dev Environment.
MbUnit over NUnit
Syntax is identical, but MbUnit includes some additional test capabilities. For example the RowTest attribute can be used to run the same test with a variety of test conditions. Repeat can be used for stress testing, and ProcessTestFixture/TestSequence can be used for ordered testing.
NMock is a dynamic mock object library for .NET. Mock objects make it easier to test single components—often single classes—without relying on real implementations of all of the other components. This means we can test just one class, rather than a whole tree of objects, and can pinpoint bugs much more clearly. Mock objects are often used during Test Driven Development.
Thanks mdenomy always good to get some feedback, Please leave your comments and suggestions.