SSIS脚本组件测试策略
这个问题具体涉及脚本组件。我知道 ssisUnit 等...
使用简单的 SSIS 脚本组件，足以让基本测试充实问题，但是我正在使用一个随着时间的推移而变得越来越复杂的脚本。
为了更好地测试功能，我正在考虑将脚本逻辑抽象到与包一起部署的 DLL 中，然后在脚本中使用自定义组件。优点是该功能将更具可测试性等，但它又是一个需要管理的部署工件。
我的问题是，有谁知道以更隔离的方式测试此类 SSIS 脚本比运行整个包并检查输出更好的方法？
This question is in respect to the script component specifically. I am aware of ssisUnit etc…
With simple SSIS Scripts Components, it’s sufficient to let basic testing flesh out issues, however I am working with a script that has grown in complexity over time.
To better test the functionality I am considering abstracting the script logic into a DLL that gets deployed with the package, and then use the custom component in the script. The advantage is that the function will be more testable etc but it’s one more deployment artefact that needs to be managed.
My question is, does anyone know of a better way to test such an SSIS script in a more isolated manner than to run the whole package and examine the output?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
CozyRoc 有一个 Script Task Plus，它基本上允许您创建可重用脚本的存储库。这应该允许您管理和修改脚本，而无需直接调整包。此外，这应该允许您确保通用脚本具有一致（相同）的代码，因为您不会到处复制文本块。我以前没有使用过这个功能，所以我不知道它是否有帮助，但它至少可以消除编译 DLL 的需要。但它无助于解决可测试性方面的问题，因此 DLL 解决方案最终可能会更好。
CozyRoc has a Script Task Plus that basically allows you to create a repository of reusable scripts. This should allow you to manage and modify the scripts without having to adjust the packages directly. Also, this should allow you to ensure that common scripts have consistent (identical) code since you aren't copying blocks of text all over the place. I haven't used this feature before so I don't know if it will help, but it might at least eliminate the need of compiling DLL's. It won't help address the testability aspect, though, so the DLL solution may end up being better.