A Lesson From My Testing Journey
On February 20th, I shared my career journey for the first time to a large audience. I gave a Ministry of Testing Masterclass called “Not All Who Wander Are Lost: …
Blog
Codemash 2018 Recap
It’s taken far too long to put this together! Here are my Storify posts of my live-tweeting the sessions from Codemash January 9-12 2018! Precompilers (Day 1 and 2): https://storify.com/g33klady/codemash-2018-precompilers-day-1-2 …
24 Hour Hackathons… with dinosaurs!
I recently participated in my company’s 24 hour hackathon. I pulled together my tweets on Storify here: https://storify.com/g33klady/jurassic-hack-ql-technology-24-hour-hackathon-of-2 It was a super cool experience, and I’m looking forward to learning more …
2017 Recap & Looking Forward to 2018
2017 was eventful, to say the least. I submitted 8 talks to 6 conferences. I was accepted to 5 of those conferences, gave an extra talk at one of them …
C# Advent Calendar – Combining Integration and UI Automation in C#
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 …
Using Fiddler AutoResponder for quick service or response mocking
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 I demo’d AutoResponder in my talk. It gives a quick idea of the tool and one way you could use it. I love Fiddler*, and there’s so much more you can do than what I’ve been able to use. Please don’t take this post as a “this is the only way you can do things” – I’ll be the first to admit that even though I’ve used Fiddler for years, I feel like there’s so much more to know about it!
*Note: I am not paid by Telerik/Progress for my endorsement; I just love the tool 😀
HTTP Status Coop – 503 Service Unavailable
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. …
HTTP Status Coop – 500 Internal Server Error
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, …
HTTP Status Coop – 413 Request Entity Too Large
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. …
HTTP Status Coop – 408 Request Timed Out
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 …