Agile Testing tools List

Update: A full list, with links to the tools, an editable wiki page and more,  is now located on the book wiki site. Feel free to add your own tools in there.

 

Working on an appendix for my book, with a list of tools and frameworks you should care about. Tell me if I missed anything:

· Mock Frameworks

o Moq

o Rhino Mocks

o Typemock Isolator

o NMock

o NUnit.Mocks

· Test Frameworks

o MS Test

o NUnit

o MbUnit

o XUnit

o Gallio 

· Dependency Injection and Ioc Containers

o StructureMap

o Microsoft Unity

o Castle Windsor

o Common IServiceLocator Framework

o Managed Extensibility Framework

o Spring.NET

o AutoFac

· Database testing

o Use Integration testing

o MbUnit,NUnit,XUnit Rollback attributes

o TransactionScope

· Web Testing

o Ivonna and Typemock

o Team System Web Test

o NUnitASP

o Watin

o Watir

o Selenium

· UI Testing

o NUnitForms

o Project White

o Team System UI Tests

o Typemock Isolator

· Threading Related Testing

o Microsoft Chess

o Typemock Racer

o Osherove.ThreadTester

· General Testing

o Pex

· Acceptance Testing

o Fit & Fitnesse

o Watin and Watir and selenium

Published Friday, October 03, 2008 5:55 PM by RoyOsherove
Filed under: ,

Comments

Friday, October 03, 2008 7:08 PM by Nicholas Blumhardt

# re: Agile Testing tools List

Hi Roy,

Lowercase 'f' in Autofac. For whatever reason :)

Nick

Friday, October 03, 2008 7:22 PM by Avish

# re: Agile Testing tools List

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 :)

Friday, October 03, 2008 7:54 PM by Kyle Baley

# re: Agile Testing tools List

Maybe add Ninject (or NInject?) for IoC containers.

Friday, October 03, 2008 8:05 PM by Kyle

# re: Agile Testing tools List

Might want to include Ninject (http://ninject.org/) for dependency injection frameworks.

Friday, October 03, 2008 10:18 PM by Grant Palin

# re: Agile Testing tools List

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...

Saturday, October 04, 2008 12:15 AM by Aaron Jensen

# re: Agile Testing tools List

You don't have any of the BDD frameworks, NBehave, SpecUnit.NET, Machine.Specifications (mspec) plus any others I may be forgetting...

Saturday, October 04, 2008 1:23 AM by Andreas Öhlund

# re: Agile Testing tools List

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)

Saturday, October 04, 2008 3:16 AM by Johan

# re: Agile Testing tools List

You might want to add WebAii to the Web test automation frameworks (http://www.artoftest.com/)

Saturday, October 04, 2008 6:23 AM by Arild

# re: Agile Testing tools List

Saturday, October 04, 2008 10:40 AM by Dew Drop - October 4, 2008 | Alvin Ashcraft's Morning Dew

# Dew Drop - October 4, 2008 | Alvin Ashcraft's Morning Dew

Pingback from  Dew Drop - October 4, 2008 | Alvin Ashcraft's Morning Dew

Saturday, October 04, 2008 10:52 AM by koistya

# re: Agile Testing tools List

Wow, great list!

Saturday, October 04, 2008 2:10 PM by Sølve

# re: Agile Testing tools 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.

Saturday, October 04, 2008 3:16 PM by Steve Bohlen

# re: Agile Testing tools List

For unit tests against your database, I would add NDbUnit (code.google.com/.../ndbunit), a .NET port of the Java DbUnit library.

Saturday, October 04, 2008 4:41 PM by zac

# re: Agile Testing tools List

QUnit.

Sunday, October 05, 2008 10:48 AM by My favorite links from the 1:1st week of October 2008

# My favorite links from the 1:1st week of October 2008

Pingback from  My favorite links from the 1:1st week of October 2008

Sunday, October 05, 2008 12:15 PM by Casey

# re: Agile Testing tools List

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

Sunday, October 05, 2008 9:55 PM by Ben Rady

# re: Agile Testing tools List

Infinitest

Monday, October 06, 2008 4:01 AM by Pages tagged "agile"

# Pages tagged "agile"

Pingback from  Pages tagged "agile"

# 2008 October 06 - Links for today « My (almost) Daily Links

Pingback from  2008 October 06 - Links for today « My (almost) Daily Links

Monday, October 06, 2008 10:30 AM by Alex Simkin

# re: Agile Testing tools List

Monday, October 06, 2008 11:26 AM by Pete

# re: Agile Testing tools List

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...

Monday, October 06, 2008 12:01 PM by Joe Faherty

# re: Agile Testing tools List

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.

Monday, October 06, 2008 1:36 PM by Jeremy Jarrell

# re: Agile Testing tools List

Wednesday, October 08, 2008 7:35 AM by Andy Stopford

# re: Agile Testing tools 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

Sunday, October 12, 2008 6:17 PM by #.think.in

# #.think.in Info-Dose #2 (5th Oct - 10th Oct 2008)

#.think.in Info-Dose #2 (5th Oct - 10th Oct 2008)

Tuesday, October 14, 2008 5:44 PM by Tim

# re: Agile Testing tools List

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

Wednesday, October 15, 2008 7:25 AM by Elad Sofer

# re: Agile Testing tools List

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.

Wednesday, October 15, 2008 7:29 AM by RoyOsherove

# re: Agile Testing tools List

tim: you are welcome to add this to the wiki page (link noted in the beginning of the post)

Wednesday, October 15, 2008 7:32 AM by RoyOsherove

# re: Agile Testing tools List

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.

Wednesday, October 22, 2008 9:08 AM by || yeschandana ||

# My favorite links from the 1:1st week of October 2008

My favorite links from the 1:1st week of October 2008

Sunday, October 26, 2008 3:38 AM by Jeff Brown

# re: Agile Testing tools List

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...  :-)