The biggest feature in this release is a GUI for creating the unit tests. The test files are still XML, but the GUI abstracts away a lot of the detail involved in creating a test. A couple of things to be aware of with the GUI, however:
- It does not check to see if your test suite has been saved before closing. So remember, "Save Early, Save Often"
- It’s possible (even likely) that you will see some errors while using the GUI. Being the most recently developed part of ssisUnit, it’s had the least testing. So if you see an error, please open an issue on CodePlex.
If you are reading this, and wondering why anyone would want to unit test an SSIS package, please check out the TechEd Online presentation I posted about recently, Testing the SQL Database. You might also consider attending the Unit Testing an SSIS Package session at the SSWUG BI Virtual Conference. I’ll be covering the basics of unit testing SSIS packages, and an overview of using ssisUnit to automate the process.
If you are reading this, and wondering why unit test at all, I highly encourage you to check out Test Driven Development, By Kent Beck. Not a traditional read for database developers, but it will give you a completely different take on the importance and benefits of unit testing.