<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx</link><description>A few years ago, when ASP.NET web services were the only (or at least most common) implementation of web services on the Microsoft platform, you couldn't really unit test services. Obviously, since you had programmatic access (via a proxy class) to the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#1201674</link><pubDate>Mon, 04 Dec 2006 03:36:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1201674</guid><dc:creator>Jimmy Rasmussens Blog</dc:creator><description>&lt;p&gt;A colleague of mine recently wrote about seperation of concerns in relation to unit testing WCF services.&lt;/p&gt;
</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#1206191</link><pubDate>Mon, 04 Dec 2006 19:35:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1206191</guid><dc:creator>Sean.McLellan</dc:creator><description>&lt;p&gt;Great post! &lt;/p&gt;
&lt;p&gt;In my organization we've been trying to figure out a way to unit test our services and this is exactly the scenario that we've discussed. &amp;nbsp;However, we DO use OperationContext.Current in our services in order to get identity info, and so we're currently developing our unit tests around the client proxy.&lt;/p&gt;
&lt;p&gt;I'll be looking forward to your future posts about how to do the integration testing -- I hope there's a way to latch into the WCF pipeline and have OperationContext.Current provide identity information without having to have the service be executing under WCF. &lt;/p&gt;
</description></item><item><title>Integration Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#1207320</link><pubDate>Mon, 04 Dec 2006 22:42:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1207320</guid><dc:creator>ploeh blog</dc:creator><description>&lt;p&gt;In my previous post about unit testing WCF services , I hinted at the need to perform integration testing&lt;/p&gt;
</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#1207369</link><pubDate>Mon, 04 Dec 2006 22:54:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1207369</guid><dc:creator>ploeh</dc:creator><description>&lt;p&gt;Hi Sean&lt;/p&gt;
&lt;p&gt;Glad you liked the post :)&lt;/p&gt;
&lt;p&gt;As you may have noticed, I've just posted my next article about WCF integration testing, although this particular article doesn't address the separation of concerns between service operations and, say, authorization.&lt;/p&gt;
&lt;p&gt;I may get to this subject in a later post, but until then, take a look at ServiceAuthorizationManager. Deriving from this class basically lets you write your authorization logic in a central place so you don't need to access OperationContext.Current in a lot of other places. In a custom authorization manager, you can, after authorizing the caller, extract all the necessary information about the caller and create an IPrincipal instance and place it on Thread.CurrentPrincipal.&lt;/p&gt;
</description></item><item><title>Mapping SAML Tokens to IPrincipals</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#1412089</link><pubDate>Thu, 04 Jan 2007 21:49:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1412089</guid><dc:creator>ploeh blog</dc:creator><description>&lt;p&gt;In my post about integration testing of WCF services , I briefly touched on the topic of authorization&lt;/p&gt;
</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#6735610</link><pubDate>Tue, 11 Dec 2007 17:51:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6735610</guid><dc:creator>Brad.Gearon</dc:creator><description>&lt;P&gt;I also feel this post is well written and very nicely explained. &amp;nbsp;Looking at it like that makes me wonder why I had questioned the method in the first place.&lt;/P&gt;</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#6735884</link><pubDate>Tue, 11 Dec 2007 18:28:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6735884</guid><dc:creator>ploeh</dc:creator><description>&lt;p&gt;Hi Brad&lt;/p&gt;
&lt;p&gt;Thanks - glad you liked it :)&lt;/p&gt;
</description></item><item><title>Implementing WCF Services Without Referencing WCF</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#8655247</link><pubDate>Thu, 26 Jun 2008 10:24:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8655247</guid><dc:creator>ploeh blog</dc:creator><description>&lt;p&gt;More than a year ago, I wrote my first post on unit testing WCF services . One of my points back then&lt;/p&gt;
</description></item><item><title>Unit Testing ADO.NET Data Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#9314610</link><pubDate>Tue, 13 Jan 2009 15:05:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9314610</guid><dc:creator>ploeh blog</dc:creator><description>&lt;p&gt;ADO.NET Data Services enables you to expose data (including, but not limited to, relational data) as&lt;/p&gt;
</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#9537578</link><pubDate>Wed, 08 Apr 2009 09:57:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9537578</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;A tool like WCFStorm might be useful in this case. It can create test cases &amp;nbsp;and invoke WCF methods so in a way you are doing Unit and Integration testing at the same time.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://geekswithblogs.net/Erik/archive/2009/04/02/130664.aspx"&gt;http://geekswithblogs.net/Erik/archive/2009/04/02/130664.aspx&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: Unit Testing WCF Services</title><link>http://blogs.msdn.com/ploeh/archive/2006/12/03/UnitTestingWCFServices.aspx#9539792</link><pubDate>Thu, 09 Apr 2009 11:38:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9539792</guid><dc:creator>ploeh</dc:creator><description>&lt;p&gt;Hi Alex&lt;/p&gt;
&lt;p&gt;Thanks for sharing :)&lt;/p&gt;
</description></item></channel></rss>