Clik here to view.
Runscope and the BlazeMeter Continuous Testing Platform
Today, we're really excited to talk about the release of the BlazeMeter Continuous Testing platform, and the integration of Runscope's API Monitoring capabilities as part of this new offering.We have...
View ArticleClik here to view.
Error # 1 – “Making a lousy menu choice” -- or using the wrong HTTP method
Just as we can choose a bad dish in a restaurant, we can sometimes use the wrong HTTP method, which can often be blamed on poor/unclear menus (documentation). Even though they should, the endpoint...
View ArticleClik here to view.
Error # 2 - "Forgetting the Seasoning or Using http:// Instead of https://
Just like failing to add salt to a dish causes a diner to wince, forgetting a single “s” can cause some surprises during API testing. Many APIs will only support HTTPS, while others may support a...
View ArticleClik here to view.
Error # 3 – 5-Star Service
A good waiter will find out what’s wrong with your order and correct the problem with minimal fuss. Similarly, a good API error message will help developers quickly determine coding issues and what’s...
View ArticleClik here to view.
Error # 4 – Reservations Required
Trying to get a same-day reservation at a popular restaurant can be nearly impossible, especially during peak dinner hours. In the same way, some APIs require ‘authorization’ and you must be careful...
View ArticleClik here to view.
Error # 5 – That's Not How I Expected It To Taste
Ordering your favorite dish at a new restaurant can often result in an unexpected taste and ingredients. Failing to acknowledge the quirks and details of how APIs and tools behave differently can also...
View ArticleClik here to view.
Error # 6 – Confusion in the Kitchen – or not Specifying Content-Type or...
When at the restaurant, we can never assume that the kitchen will be aware of your dietary requirements mentioned when you placed your order. It’s the same with APIs, especially when negotiating the...
View ArticleClik here to view.
Error # 7 – “I Didn’t Order That!” – or APIs Returning Invalid Content Types...
So, you thought you ordered mac and cheese but the server places a bowl of nachos in front of you. It’s the same story with APIs. Like cases where an API returned an HTML error page instead of the...
View ArticleClik here to view.
Error # 8 – Lost in Translation
Have you ever tried to order from a restaurant when you and the waiter don't speak the same language? You might face similar confusion when trying to debug SSL errors since returned messages can be...
View ArticleClik here to view.
Error # 9 – "Waiter There's a Fly in My Soup"
Like an old cheese board, API data problems can be rich, varied, and smelly. This can include: • Content-length mismatched to actual content length causing connections to be prematurely closed and...
View ArticleClik here to view.
Error # 10 – Tea Anyone?
No waiter worth their salt would crack a joke after they tell you that the kitchen has a problem with your order. Same in development, right? Wrong! Back in 1998, a group of developers jokingly...
View Article