Also, I wouldn't call the Common Service Locator a
DI/IoC tool; rather it's supposed to be an abstraction
of one, so that you could inject your own dependency
injection framework instead of having a dependency on
it. A meta-IoC container, if you will :)
Maybe add Ninject (or NInject?) for IoC containers.
That's a good list. I was aware of *some* of them, but
certainly not all. Got some more entries for my .NET
tool listing...
You don't have any of the BDD frameworks, NBehave,
SpecUnit.NET, Machine.Specifications (mspec) plus any
others I may be forgetting...
Wow, great list!
Roy,
Gallio is not really a test framework so you can't
really classify it there. It makes MbUnit and Gallio
sound like seperate things, while they are in some
sense, they are also inclusive of each other. If you
wanted, create a test automation framework category and
add gallio to that.
I'd add CsUnit to your list as well. Saw your later post
but prehaps a BDD category - BDD styles using xUnit
frameworks, MSpec, NBehave are a few examples.
Andy
This is just a list of tools, i really have a problem
with the definition "agile tools", especially giving the
first value of the agile manifesto: Individuals and
interactions Over processes and tools.
tim: you are welcome to add this to the wiki page (link
noted in the beginning of the post)
Elad: It is indeed just a list of tools. You are free to
use Notepad instead of Visual Studio, if you don't buy
into the fact that the *right* tooling can be used to be
more agile.
I don't think you missed anything but I do believe that
you should spend some extra time writing descriptions of
these tools.
I noticed that much of the content was taken more or
less directly from the project mission statements. This
is okay but I think readers would benefit from a more
in-depth perspective and perhaps some additional context
as to what these tools are good for and how you might go
about choosing one.
This is also in line with @Elad's point about Agile.
Most any tool, applied with care, can enable one to
become more Agile. With that in mind, I think it would
help if you provided some good examples of how these
kinds of tools fit in. (That's probably already covered
in the subject matter of the book itself though.)
In any case, the list should be left deliberately
open-ended. Almost as soon as you publish it, it will be
out of date... :-)