LoadFocus now provides easy testing for services that are using OAuth authorization (we support OAuth2.0 as OAuth1.0 was retired in 2012). We support all the OAuth 2.0 grant types: For testing a service that is behind a login (that has OAuth authorization) the only thing the user needs to do is: The call to the authorization server will be done only once before the performance testing of the API endpoints starts.
It’s been a while since we published our latest product updates, but the work on Loadero wasn’t paused. Our team was busy working on the newest features to make your performance testing with Loadero more convenient and effective.
For many companies, performance is the main reason to go with GraphQL. But is that a valid argument? Often developers compare GraphQL to REST APIs and see the N+1 requests (or over-fetching) as an important reason to go for GraphQL. Let's put that to the test and explore if GraphQL APIs actually can outperform existing REST APIs. For this, we'll take a GraphQL-ized REST API (from JSONPlaceholder) and test the performance of GraphQL and compare it to the REST approach.
When developing web applications, one of the important things is to provide smooth accessibility of your product to the clients. But that is not an easy task to accomplish as several factors come into play. Software testing requires coverage of many different devices, environments, and conditions. We in Loadero provide features to use different browsers, run tests from different locations, set different fake media for webcam and mic simulation, etc.
As a software engineer here at Grafana Labs, I’ve learned there are two questions that commonly come up when someone begins setting up a new Loki installation: “How many logs can I ingest into my cluster?” followed by, “How fast can I query these logs?” There are two ways to find out the answers.
Rendezvous is a French word commonly used in the load testing word. It sounds so fancy! I believe Mercury first coined and implemented it (I may be wrong) in LoadRunner. NeoLoad has it with the same name, and JMeter calls it Synchronizing timer. But what is it really, and how may we use it? Rendezvous is a function that stops the virtual users when they reach that instruction in the script. The function makes them wait until more virtual users get to that step or a timer runs out.
