Once those have adequate coverage, move on to the next set.
As far as requirements breakdown – yes, you do need to understand what the package is supposed to do in order to test it properly.
This session was an introduction to the scripting objects in SSIS, and how they can be used to extend the built in functionality. This session was on testing data-centric applications, both during development and how you can continue validating your data in production. Not just any testing, but real tests that help you truly verify the state of your code, applications and data.
I like Test Driven Development, but really any approach that focuses on automated, repeatable tests that verify meaningful functionality I find hugely beneficial.
* I did a webinar this week for Pragmatic Works’ “Free Training on the T’s”. You can also download the slides from my Sky Drive, and ssis Unit can be downloaded from Code Plex.
We had great turnout for the session, and a lot of great questions. This helps ensure that code continues working as expected, and that you don’t have hidden “side effects” associated with your changes.
I promised to make my presentation and demos available, so here they are. I found out recently that I’ll be able to attend the PASS Business Analytics Conference this year, which I’m pretty excited about.I didn’t have time to address all of them during the webinar, and I had a number of requests to share my answers with all the attendees, so I thought I’d write up a blog post on the questions that I didn’t get a chance to answer. I would create a known set of data in a test version of the source database.I would then create a unit test for the data flow task that checks that the output includes the data with the proper transformations.Devin Knight (a co-worker at Pragmatic Works) is delivering this, and he puts together great sessions.Power View is one of those technologies that I don’t spend a lot of time with, but I know I need to know it better, and this session should help with that.