Blog post related to testing APIs
Last year, I had a great time contributing to the C# Advent Calendar with a post on combining API and UI automation. I was excited to sign up once again for the 2nd Annual C# Advent Calendar! Check out the page here with the full calendar: https://crosscuttingconcerns.com/The-Second-Annual-C-Advent This year, I want to talk about smoke …
I have written before a few times about implementing automated tests for REST APIs using C# (here and here). In those posts, I’ve used a utility method to handle the actual sending of the HTTP request, and another one to read the response. These methods help to illustrate what our automated tests are actually doing. However, I …
It’s been a bit quiet lately, and that’s because I’ve been very busy with creating a workshop and new talk for TestBash Manchester! Now that it’s done, I can finally blog about some of the stuff I did to create the workshop, and release an app for folks to practice with! Understanding The Problem I …
I signed up for the C# Advent Calendar with this post – be sure to check out the rest of the blog posts in the calendar! This post assumes you’ve got some experience with C# and Visual Studio, so I won’t be over-explaining some things. Comment if you get stuck or have questions! If you’re …
In my Testing RESTful Web Services talk, I touch on service virtualization briefly, and I include a short demo of using Fiddler‘s AutoResponder. I’ve been meaning to look into other (free) tools but haven’t had the chance. After a question on the Testers Slack, I realized I could do a short blog post on how …
Fourteenth in the HTTP Status Coop series is 503 Service Unavailable! The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. via Wikipedia Cooper says “no way!” 😀 For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on …
Lucky Thirteen, on a Monday the 13th, of the HTTP Status Coop series is 500 Internal Server Error! And no, I didn’t plan it that way! A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. via Wikipedia For the entire HTTP Status Coop series that’s been released …
Twelfth in the HTTP Status Coop series is 413 Request Entity Too Large (or Payload Too Large)! The request is larger than the server is willing or able to process. Previously called “Request Entity Too Large”. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop …
Eleventh in the HTTP Status Coop series is 408 Request Timed Out! The server timed out waiting for the request. According to HTTP specifications: “The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.” via Wikipedia For …
Tenth in the HTTP Status Coop series is 406 Not Acceptable! The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. via Wikipedia Clearly the request was *not* acceptable for Cooper… For the entire HTTP Status Coop series that’s been released so far, head over to …