NUnit and Windows Workflow Foundation

"Mike Chess" <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <FC7DD4B0D06F7B43B837D62AC64786C401A0D000@pa-exch2003>
I'm new to using NUnit, so please forgive me if this question has been
asked before.

 

With class libraries built on the new Windows Workflow Foundation (WF)
so much of what happens is hidden in the library.  Methods that are
added to handle virtually anything in WF (like a CodeActivity) are
private to the workflow implementation.  There are declarative checks
(i.e. some options for IfElseBranchActivities) that are not in code at
all.  The workflow itself is not directly accessible as it is created
and managed by the WF runtime environment.

 

Classes that I create that are used by a WF library can certainly be
setup with NUnit tests.  What I'm struggling with is how I can use NUnit
to validate that the workflow itself is correct.

 

Has anyone had any experience with hooking NUnit up to WF?  Is there a
guide somewhere?

 

Any guidance, thoughts, or suggestions are appreciated.

Mike Chess
Senior Software Engineer
Provider Advantage NW, Inc.
800-337-5482 x3805 (P)
[email protected]

Join the ReVolution 
www.revenue360.net

________________________________

This email may contain confidential information. If you are not the
named recipient, you are not authorized to read, disclose, copy,
distribute, or take any action in reliance on the information. If you
have received this email in error, please immediately notify the Privacy
Officer at 1-800-337-5482. 

________________________________

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.