Gojko Adzic

I’m doing a talk on effective test driven database development this Thursday in London (near Farringdon station, stating at 18:30). I’ll talk about unit testing stored procedures, test data management and best practices for java/.net integration testing that involves a database. In the talk I’ll also give a technical demo of my DbFit database unit testing library that provides DB management/unit testing capabilities to FIT/FitNesse.

The event will be organised by Skills Matter, and it is free but registration is required. For more info, see:

http://skillsmatter.com/podcast/open-source-dot-net/effective-test-driven-database-development

See you on Thursday!

I am pleased to finally announce version 1.0 of DbFit. DbFit is an extension to FIT/FitNesse that makes test-driven database development easy. Version 1.0 (2008-03-10) is a major cleanup release, finally bringing proper documentation for the library as well. Grab it from SourceForge.
Continue Reading »

I’m preparing for release 1.0 of DbFit — one of the new things will be support for In/Out parameters. A pre-release with this functionality is now available for testing.
- To use In/Out parameters, just define two columns for the same parameter. The one for OUT direction should have a question mark
- Order of parameters in the table is no longer important (it was in Java), so you should be able to put parameters in FitNesse pages in a different order then those in the database.

Here is an example:

|Execute procedure|MultiplyIO|
|factor|val|val?|
|10|5|50|
|2|8|16|

Introducing IN/OUT parameters required a huge change in the underlying parameter processing, please help by testing a pre-release and verifying that your old tests work with the new system as well.

SQL Server turned out to be especially tricky because there is no explicit IN/OUT flag on stored procedure parameters, and .NET driver does not expect all outputs to be simply declared as InputOutput, so there is an ugly workaround in the code to check whether an output parameter is also used for input. I do not expect any problems with this, but it’s best to double-check.

Get the binary builds for .NET and Java from SourceForge.

Great news – SQLServer 2000 is now supported in DbFit. The only limitation, compared to Sql Server 2005, is that tables and procedures must be fully qualified (defined as schema.name), if there is an object of the same name in the current user’s schema and in dbo. The next official release will include sql server support — until then, you can download the binaries from Sourceforge: dbfit-dotnet-20080107.zip

the complete package, with acceptance tests, can also be downloaded from here: dbfit-complete-20080107.zip

For sqlserver 2000, use dbfit.SqlServer2000Test instead of dbfit.SqlServerTest.

Many thanks to Oscar Centeno for his help on implementing and testing support for Sql Server

DbFit 0.93 has just been released. Pick it up from SourceForge.

New and noteworthy

• Storing query results into fixture symbols
• Comparing queries stored into symbols
• SQL Server support for GUID and SQL_Variant types (variant is treated like a string)
• .NET version updated to use FitNesse.Net 1.3
• Loading connection settings from a text file on server

Continue Reading »