Systems | Development | Analytics | API | Testing

%term

API Load Testing Mistake #2: Not Calibrating Virtual Users to Real Users - @SmartBear Talks

A huge part of your strategic plan for load tests built into your app development business processes is understanding and ensuring that the user profiles or the actions that your simulated users take in any testing environment accurately depict what happens in a real-world use case. That's why you need to be very careful with setting up virtual users in your load tests. We will investigate possible issues with Damion White, software testing consultant from WiseClouds, in this video.

Make Your Keyboard Great Again! - User Story

We are all familiar with this scenario, you work on your training code, fix “all” of the bugs (the ones you know about), wait for a few iterations, see that batch size wasn’t wrong and nothing blows up, and then you happily go home. However, when you come back into the office the next day look at your loss and test accuracy you’re horrified to find that the experiment crashed on the first test cycle because you pointed your test set in the wrong folder 🙁

Tracing With Zipkin in Kong 2.1.0

There is a great number of logging plugins for Kong, which might be enough for your needs. However, they have certain limitations: Most of them only work on HTTP/HTTPS traffic. They make sense in an API gateway scenario, with a single Kong cluster proxying traffic between consumers and services. Each log line will generally correspond to a request which is “independent” from the rest.

Node.js Logging: A How-to Guide

When visiting a new website, it is quite normal to get carried away by the bells and whistles of the fancy UI and UX and not be able to appreciate all the lower level, back-end code that runs tirelessly to ensure a smooth and fast website experience. This is because your front-end HTML code has a visually rich browser page interface as a platform to showcase its output. Whereas your back-end, server-side code usually only has a console at its disposal.

10 Reasons Why Test Automation Fails

We know that test automation is expected to make processes faster and easier in software organizations and also to enhance the quality of the software significantly. However, in reality, test automation fails around 64% of the time to deliver according to the expectations as per Cigniti. Here are some of the main reasons why test automation fails for your web automation:

Yellowfin Embedded Analytics Walkthrough for Product Teams

As a recognized leader in embedded analytics, Yellowfin has been designed and built to enable you to embed amazing analytical experiences into your software. From a highly integrated dashboard module and full self service reporting, to enabling best practice integration that blurs the lines between analytics and your application and workflows. Modernize your reporting environment with Yellowfin to ensure your customers engage with your data, discover insights faster through automation and innovate with contextualised analytics.