Khalid Abuhakmeh

At RIMdev, We are closing in on 7 months of using our Automation libraries to test a WebAPI application. This post will explain some of the best practices we've found to get valuable and fast(ish) tests. Here, in no particular order, is our wisdom learned through the school of hard knocks.

We just released Supurlative and one of my favorite features is Formatters. It gives you the ability to intercept any type and perform custom logic. In our current API work, we wanted to intercept a type that implemented a generic interface. That type is an IRange<T> interface.

This extension method runs on my tears

We recently released Supurlative, a hypermedia centric url and template generator. Part of generating templates is removing the constraints off of existing routes. To do this accurately without side effects, we need to iterate over each key/route pair and register them into our temporary RouteCollection. Sounds easy right? Well not so much, . . .

Links and templates are at the heart of a Hypermedia API. It is important to generate correct resource links in addition to properly defining the capabilities each resources exposes via url templates. ASP.NET WebAPI comes with first class support for generating urls using the RouteCollection class. SupUrlative attempts to standardize the way . . .

Expectations vs. Reality

Custom error pages are one of the last development items on the creation of an ASP.NET application. During development, we want to see the yellow screen of death early and often to ensure users don't see the error pages at all. I've personally added custom errors to many web applications, and even wrote about it in a previous post.

I've been working with government generated HTML this week.By the looks of it, I assume the HTML I am working with is generated and exported directly from Satan's Word Processor. Here is a small sample of what some of this html looks like.