ssisUnit Wiki & Documentation Rss Feed

Updated Wiki: Using Expressions in Asserts

johnwelch — Thu, 16 Apr 2009 21:14:09 GMT

Expressions in Asserts is a feature planned for the ssisUnit 1.1 release. It's implemented in the source, so you can play with it now by downloading and building the source.

Assert Expressions

The expression feature allows you to embed simple C# expressions into the ExpectedResults of an Assert. This adds a lot of flexibility to the Asserts. Previously, they were limited to evaluating whether result returned by the command object in the Assert was equal to the ExpectedResult. While this worked in a number of scenarios, it wasn't very flexible for checking non-equality, or making the expected result the current date. Now, there is capability in the Assert to handle those scenarios.

The expression in ExpectedResult must evaluate to a boolean (True/False) value, and it has to be valid C# syntax (similar to the expression language in SSIS). You can reference the actual result in the expression using the result object, which will contain the output from the command object contained in the Assert. Since C# is type safe, the expression need cast the result objects to the correct type for the comparison.

To use the expression in an Assert, you'd set the Expression property to true, and put the expression in the ExpectedResult property:

Or if you prefer the raw XML:
<Assert name="ExpressionTest" expectedResult="(int)result==1" testBefore="false" expression="true">
<SqlCommand connectionRef="AdventureWorks" returnsValue="true">
SELECT 1FROM Production.Product
</SqlCommand>
</Assert>

Examples

Check a result to see if it is less than 1

(int)result<=1

Compare a string

result.ToString()=="test"

Checking the result against the current date

((DateTime)result).Date==DateTime.Now.Date

Updated Wiki: Using Expressions in Asserts

johnwelch — Thu, 16 Apr 2009 21:12:20 GMT

Expressions in Asserts is a feature planned for the ssisUnit 1.1 release. It's implemented in the source, so you can play with it now by downloading and building the source.

Assert Expressions

The expression feature allows you to embed simple C# expressions into the ExpectedResults of an Assert. This adds a lot of flexibility to the Asserts. Previously, they were limited to evaluating whether result returned by the command object in the Assert was equal to the ExpectedResult. While this worked in a number of scenarios, it wasn't very flexible for checking non-equality, or making the expected result the current date. Now, there is capability in the Assert to handle those scenarios.

The expression in ExpectedResult must evaluate to a boolean (True/False) value, and it has to be valid C# syntax (similar to the expression language in SSIS). You can reference the actual result in the expression using the result object, which will contain the output from the command object contained in the Assert. Since C# is type safe, the expression need cast the result objects to the correct type for the comparison.

To use the expression in an Assert, you'd set the Expression property to true, and put the expression in the ExpectedResult property:

Cannot resolve image macro, invalid image name or id.

Or if you prefer the raw XML:
<Assert name="ExpressionTest" expectedResult="(int)result==1" testBefore="false" expression="true">
<SqlCommand connectionRef="AdventureWorks" returnsValue="true">
SELECT 1FROM Production.Product
</SqlCommand>
</Assert>

Examples

Check a result to see if it is less than 1

(int)result<=1

Compare a string

result.ToString()=="test"

Checking the result against the current date

((DateTime)result).Date==DateTime.Now.Date

Updated Wiki: Home

johnwelch — Thu, 16 Apr 2009 20:27:17 GMT

Project Description
ssisUnit is a unit testing framework for SQL Server Integration Services.

ssisUnit is a unit testing framework for SQL Server Integration Services. It is loosely based on the xUnit family of unit testing frameworks, but is tailored to better support the SSIS environment. One of the bigger differences is that you do not have to write code to create the unit tests. Instead, we have taken a declarative approach to specifying the unit tests. The test information is all stored in XML files. Since many SSIS developers do not have a background in coding traditional applications, we felt it was important to deliver something that did not require an understanding of .NET development to use.

ssisUnit supports task level testing in SSIS. Any control flow task can have a set of tests created around it. This level of granularity in testing can make testing complex packages much easier.

Unit Test Structure

Getting Started

Product Sample Package and Test

Using Expressions in Asserts

New Comment on "Unit Test Structure"

johnwelch — Wed, 18 Mar 2009 22:25:49 GMT

The XSD is included with the source code, and compiled into the binaries. I didn't want to introduce any outside dependencies. However, it probably would be helpful to add it as a separate download on the release page.

New Comment on "Unit Test Structure"

ahammon — Tue, 17 Mar 2009 22:05:11 GMT

I note that http://tempuri.org/SsisUnit.xsd no longer works. Is there a canonical source for the dtd?

Updated Wiki: Getting Started

johnwelch — Thu, 25 Sep 2008 15:42:43 GMT

_***Note: This example works with the 1.0 version, which is available on the Releases page.

The attached files contain a very simple package and unit test to illustrate the concept of ssisUnit. For a more complete sample, see Product Sample Package and Test.

Getting Started.zip

Updated Wiki: Product Sample Package and Test

johnwelch — Thu, 25 Sep 2008 15:39:52 GMT

This is a sample SSIS 2005 package and unit test. It will also work under 2008, once the package has been upgraded.

The attached sample works with v1.0 of ssisUnit. This is now available on the Releases page.

ProductSample.zip

Updated Wiki: Product Sample Package and Test

johnwelch — Thu, 25 Sep 2008 15:38:27 GMT

Updated Wiki: Product Sample Package and Test

johnwelch — Sun, 24 Aug 2008 03:00:14 GMT

This is a sample SSIS 2005 package and unit test. It will also work under 2008, once the package has been upgraded.

The attached sample works with v1.0 of ssisUnit. This hasn't been released yet, but it can be built from the current source code.

ProductSample.zip

Updated Wiki: Getting Started

johnwelch — Wed, 20 Aug 2008 19:44:52 GMT

***Note: This example applies to the 1.0 version, which must be downloaded and compiled. The release version will be available soon.

The attached files contain a very simple package and unit test to illustrate the concept of ssisUnit. For a more complete sample, see Product Sample Package and Test.

Getting Started.zip

Updated Wiki: Getting Started

johnwelch — Wed, 20 Aug 2008 19:44:27 GMT

Updated Wiki: Getting Started

johnwelch — Wed, 20 Aug 2008 15:53:14 GMT

The attached files contain a very simple package and unit test to illustrate the concept of ssisUnit. For a more complete sample, see Product Sample Package and Test.

Updated Wiki: Getting Started

johnwelch — Wed, 20 Aug 2008 15:39:12 GMT

The attached files contain a very simple package and unit test to illustrate the concept of ssisUnit. For a more complete sample, see Product Sample Package and Test.

Updated Wiki: Product Sample Package and Test

johnwelch — Wed, 20 Aug 2008 14:26:38 GMT

This is a sample SSIS 2005 package and unit test. It will also work under 2008, once the package has been upgraded.

The sample package will be posted soon.

Updated Wiki: Home

johnwelch — Wed, 20 Aug 2008 14:24:43 GMT

UPDATED WIKI: Unit Test Structure

johnwelch — Wed, 12 Mar 2008 02:23:11 GMT

The unit test structure follows the traditional xUnit structure - setup, test, and teardown. The unit tests are defined in XML files. Setup and Teardown can contain multiple commands, which can perform different types of operations. In the current release, the supported command types are SQLCommand, ProcessCommand, and VariableCommand. In Setup, these commands are used to establish the test data needed for the test to execute. In Teardown, the commands can be used to clean up the data.

Test nodes contain a reference to a task, a task within the package (or the package itself), an expected result, and a command. The command is used to verify that the task has run successfully. For example, a Test node could reference an Execute SQL Task that sets a variable within the package. The Test node would contain a VariableCommand that retrieves the value of the variable and compares it to the expected result to determine if the Execute SQL Task performed as expected. The reference to the task can be the task name or the GUID of the task. If the task reference is the GUID of the package itself, the test is effectively for the entire package.

Setup and Teardown runs prior to and after each Test. If the unit test file contains 5 tests, Setup and Teardown will be run 5 times.

The unit test file can also include a TestRef node, which references another unit test file. This allows unit tests to be nested. The Setup and Teardown from a parent unit test will be added to the child's list of Setup and Teardown nodes, so this allows for defining a common set of Setup and Teardown commands to be used across multiple unit tests.

The ConnectionList node contains a list of Connection nodes. Connection nodes provide the connection strings to use for any SQL statements that need to be executed. In the future, the Connection node will support referencing a connection manager from the package, but this functionality is not yet implemented.

When the unit test is run, this is the sequence of execution for each test:

All commands in the setup node are executed.
The task referenced by the test is executed. If the task reference is the package guid, the entire package is executed.
The command contained in the test node is executed.
The value returned from the command is compared to the expected value for the test.
All commands in the teardown node are executed.

This sequence repeats for each subsequent test.

This is a sample of a unit test file:

<?xml version="1.0" encoding="utf-8" ?>
<TestSuite xmlns="http://tempuri.org/ssisUnit.xsd">
<Setup>
<SQLCommand connectionRef="AdventureWorks" returnsValue="true">
SELECT COUNT(ProductID) FROM Production.Product
</SQLCommand>
<SQLCommand connectionRef="AdventureWorks" returnsValue="false">
SELECT ProductID FROM Production.Product
</SQLCommand>
<ProcessCommand process="CMD.EXE" arguments="/c COPY c:\temp\temp.txt c:\temp\temp2.txt"/>
<VariableCommand name="ProductRowCount" value="20"/>
</Setup>
<Tests>
<Test name="PassedTestSQL" package="C:\Projects\SSISUnit\SSIS2005\SSIS2005\UT Basic Scenario.dtsx" task="SELECT COUNT" expectedResult="504">
<VariableCommand name="ProductRowCount"/>
</Test>
<Test name="FailedTestSQL" package="C:\Projects\SSISUnit\SSIS2005\SSIS2005\UT Basic Scenario.dtsx" task="SELECT COUNT" expectedResult="1">
<SQLCommand connectionRef="AdventureWorks" returnsValue="true">
SELECT COUNT(*) FROM Production.Product
</SQLCommand>
</Test>
<TestRef path="C:\Projects\SSISUnit\UTssisUnit\UTssisUnitPackage.xml" package="C:\Projects\SSISUnit\SSIS2005\SSIS2005\UTSimple.dtsx" task="{03894FFA-8636-4E81-B0CD-3F78E2CFBBEF}"/>
</Tests>
<Teardown>
<SQLCommand connectionRef="AdventureWorks" returnsValue="true">
SELECT COUNT(ProductID) FROM Production.Product
</SQLCommand>
<VariableCommand name="ProductRowCount" value="10"/>
</Teardown>
</TestSuite>

UPDATED WIKI: Home

johnwelch — Wed, 12 Mar 2008 01:26:45 GMT

UPDATED WIKI: Home

johnwelch — Fri, 07 Mar 2008 05:31:31 GMT

UPDATED WIKI: Home

johnwelch — Wed, 27 Feb 2008 06:05:10 GMT

Project Description
ssisUnit is a unit testing framework for SQL Server Integration Services.

ssisUnit is a unit testing framework for SQL Server Integration Services. It is loosely based on the xUnit family of unit testing frameworks, but is tailored to better support the SSIS environment. One of the bigger differences is that you do not have to write code to create the unit tests. Instead, we have taken a declarative approach to specifying the unit tests. The test information is all stored in XML files. Since many SSIS developers do not have a background in coding traditional applications, we felt it was important to deliver something that did not require an understanding of .NET development to use.

ssisUnit supports task level testing in SSIS. Any control flow task can have a set of tests created around it. This enables an SSIS developer to test individual tasks in isolation.