[ Send this article ]
Your message has been sent.
How would you like to send this article:
[ Save this article ]
Save this article to your account for easy access.
This article has been saved to your account.
Go to my account
This article has been emailed to your Kindle.
Send this article
Complete the form below to send this article, Testing and Debugging Windows Workflow Foundation 4.0 (WF) Program, to a friend (or to yourself). We will never share your details (or your friend's) with anyone. For more information, read our Privacy Policy.
by
Andrew Zhu | September 2010 |
Architecture & Analysis Cookbooks Enterprise Articles Microsoft
In the previous article we have dealt with working on our first WF program. In this article by Andrew Zhu, author of Microsoft Windows Workflow Foundation 4 cookbook, we will cover the following:
- Testing a WF program with unit test framework
- Debugging a WF program
(For more resources on this subject, see here.)
Testing a WF program with unit test framework
In this task, we will create a Test Project to do unit test for WF program.
How to do it...
- Add a Test Project to the solution:
Add a Test Project to Chapter01 solution and name the project as UnitTestForWFProgram as shown in the following screenshot:
- Add a workflow file to the Test Project:
Add a workflow activity to this project. Right-click the newly created Test Project, then go to Add | New Items... | Workflow | Activity and name the activity as WorkflowForTest.xaml. In the opening WF designer, create an OutArgument as OutMessage. Next, drag an Assign activity to Designer panel and assign string "Test Message" to the OutMessage argument as shown in the the following screenshot:
In WF4, workflow is actually an Activity class. We could see "Workflow" as a conception from a macroeconomic viewpoint, while consider "Activity" as a development concept.
- Create unit test code:
Open UnitTest1.cs file and fill the file with following code:
code 33
- Run it:
Set UnitTestForWorkflow as Startup project. Press Ctrl+F5 to build and run the test without debugging as shown in the following screenshot:
How it works...
In the preceding code snippet, [TestClass] indicates it is a unit test class, whereas [TestMethod] indicates a test method. When the Test Project runs, the test method will be executed automatically.
There's more...
In real application development, we can also create a separate Unit Test project and add a reference to the target project.
(For more resources on this subject, see here.)
Debugging a WF program
In this task, we will debug a WF program.
How to do it...
- Create a workflow project:
Create a new Workflow Console Application project under Charpter01 solution. Name the project as DebugWFProgram. In the opening WF designer panel, author a workflow as shown in the following screenshot:
- Create workflow host code:
Open Program.cs file and change the code to:
code 34
- Set debug break point:
Right-click an activity, select Breadpoint | Insert Breakpoint to add debug break point. - Debug it:
Press F5 to debug a WF Program; we can refer the following screenshot:
There's more...
We can also debug a XAML workflow. Open Workflow with XML editor, insert some breakpoints, then press F5; we will see the breakpoints as shown in the following screenshot:
Summary
This article detailed the tasks of testinf and debugging a WF program.
Further resources on this subject:
About the Author :
Andrew Zhu
Andrew Zhu is a technology support engineer at Microsoft (Microsoft Globe Tech Support Center) in Shanghai. Over the past few years, he has helped developers and his customers to develop WF, BizTalk, IIS, and ASP.NET applications.
Books From Packt
|
|
|
Post new comment