Gojko Adzic

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.

Mike Stockdale just released FitNesse.NET 1.4. Here are the news:

• To reduce the occurrence of technical jargon in storytests, configuration information can be specified in a Suite Configuration File
• FitServer socket connection to FitNesse now works on Vista.
• fit.dll is not loaded, even if it appears in an assembly list, to avoid multiple versions and invalid cast exceptions.
• Folder Runner opens files in shared read mode so other processes may have the files open.
• Import Fixture removes whitespace from namespaces.
• Row Fixture reports an error if a row is too short.
• The assemblies have been reorganized. Fit Library and Fit have been combined in fit.dll and all test classes have been moved out of fit.dll.

See www.syterra.com for more details. Grab the new release from SourceForge.