By mswatcher
via blogs.msdn.com
Submitted: Jan 29 2013 / 11:01
It's important to test any service you write to make sure that it's behaving the way you expect it to. In this blog post, I'll go through the main ways of testing a WebAPI service, exploring the benefits and drawbacks of each option so that you can test your service effectively. WebAPI testing can be broadly categorized into one of three groups: Unit testing a controller in isolation Submitting a request to an in-memory HttpServer and testing the response you get back Submitting a request to a running server over the network and testing the response you get back
Tweet
SaveShareSend
Tags: .net, frameworks, web services
-
Create a 3D CSS Animated Box with Sass and Compass
-
Domain Events with Ninject and ASP.Net Web API
-
Stumbling Into the Cold Expanse of Real Programming
-
15 useful WordPress Functions
-
Spring and the java.lang.NoSuchFieldError: NULL Exception
-
Quantifying Scientific Consensus, Zombies in R, and More Data Links
Add your comment
