Unit Testing, Agile Development, Leadership & .NET - By Roy Osherove
Hi Roy,
Lowercase 'f' in Autofac. For whatever reason :)
Nick
You forgot Ninject.
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.
Might want to include Ninject (http://ninject.org/) for dependency injection frameworks.
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...
I would add "inmemory database" in the database testing section. I'm often using NHibernate + SqlLite for my database tests and it works great. (recreates the db before every test)
You might want to add WebAii to the Web test automation frameworks (http://www.artoftest.com/)
http://testautomationfx.com/ for UI testing.
Pingback from Dew Drop - October 4, 2008 | Alvin Ashcraft's Morning Dew
Wow, great list!
You should also DbFit to your list:
gojko.net/.../dbfit
DbFit is a set of FIT fixtures which enables FIT/FitNesse tests to execute directly against a database.
For unit tests against your database, I would add NDbUnit (code.google.com/.../ndbunit), a .NET port of the Java DbUnit library.
QUnit.
Pingback from My favorite links from the 1:1st week of October 2008
For (specifically Oracle) Database Unit Testing, we use utPL/SQL: utplsql.sourceforge.net
Has the (dis)advantage of letting you write your database tests in PL/SQL
Infinitest
Pingback from Pages tagged "agile"
Pingback from 2008 October 06 - Links for today « My (almost) Daily Links
You forgot LinFu IoC container.
plaureano.blogspot.com/.../linfu-ioc-20-reaches-important.html
Dude, from the URL to "your book", I really look forward to "Arto Fun It Testing". I think I'll write about it at Expert Sexchange...
For Database Unit Testing, I would suggest Quest Code Tester for Oracle. This is obviously specific to Oracle and more specifically pl/sql environments but it is allows for automated testing of pl/sql. It was actually created by the individial that developed utPL/SQL and has signficant advantages over that freeware solution.
MbUnitForms
sourceforge.net/.../mbunitforms
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
#.think.in Info-Dose #2 (5th Oct - 10th Oct 2008)
Under "Database testing"
There's a free tool - "MassDataHandler", which you blogged about here: weblogs.asp.net/.../MassDataHandler_3A00_-generate-test-data-to-help-with-data-layer-testing.aspx
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.
My favorite links from the 1:1st week of October 2008
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... :-)