This project is read-only.

New Steps in the 2004 version

These descriptions are taken from the NDoc file

ContextPopulateStep The ContextPopulateStep takes each key and value and adds it to the context. This is a standalone step and should not be nested (like the other ContextLoader steps)

DotNetObjectInvokerExStep The DotNetObjectInvokerStep is a sort of extension mechansim. It is used to call out to any .NET component that can accept requests and return responses. This allows developers to invoke their components from BizUnit and do stuff that is not possible in BizUnit itself. The EXTENSION now provides the facility to use the context while setting the parameter values

FileDeleteExStep The FileDeleteStep deletes a FILE specified at a given location. The EXTENSION now includes the use of context in this step

OracleDBQueryStep The OracleDBQueryStep is used to query an Oracle database and validate the values for the row returned. It requires the installation of the ODP.NET provider

OrchestrationConductorExStep The OrchestrationConductorExStep may be used to stop/start an orchestration. This replaces the out of the box step with code that uses the OM.

ReceivePortConductorExStep The ReceivePortConductorExStep enables or disables a receive location. This step replaces the out of the box step with code that uses the OM

StringFormatterMultipleStep The StringFormatter multiple step is used to format a base with multiple parameters and then to load the result into a specified key in the context

StringFormatterStep The StringformatterStep is used to format a string with a number of parameters and then to load the formatted string into the value of a specified context key. This is useful when you have to build say, a connection string, with dynamic values for server, database etc and then need to store in the context for use in future steps that connect to the specified database

WaitOnFileExStep The WaitOnFileExStep is used to wait for a FILE to be written to a given location. It uses the file system watcher. It replaces the old step which used to simply delay for the given interval.Now when the file is detected the system returns immediately. It also loads the file name(both the full name and the simple name) into the context (with the keynames WaitedFileFullName and WaitedFileName) and allows you to specify whether you want to consider previously existing files which is useful in scenarios where the testing is intensive and the system races ahead of the test and places the file in the location and the step executes after the file is already available.

XmlPokeStep This step is modelled on the lines of the NAnt XmlPoke task The XmlPokeStep is used to update data in an XML file with values from the context This will enable the user to write tests which can use the output of one step to modify the input of another step

Last edited Feb 21, 2007 at 4:15 PM by santoshbenjamin, version 2


No comments yet.