I've done quite a bit of WF development using 3.5 over the last few years, but am just now ramping up on WF in 4.0. I have a TDD bent, and while WF 3.5 was difficult at times to unit test, I'm wondering if anyone could share their strategy for unit testing workflows in WF 4 and/or point me to resources that would help get me started?
+1
A:
The easiest approach is, just like in WF35, to separate the implementation from the activity so they can be tested independently of each other. The activity extension is just a regular class so use whatever you are comfortable with. Most activities can be unit tested quite easily using the WorklfowInvoker.
Maurice
2010-06-30 18:19:06
agreed, and I will certainly do that. That said, any testing examples or best practices from your own use that you'd like to share?
Brandon Satrom
2010-07-01 14:18:57