We're happy to announce the release of automated error insights on your load tests. These help you to solve commonly seen issues with tests, and what you can do to try solve them.
We already support a wide variety of intelligent error parsing, but will continue to grow it in the future. Here is an example of a 429 HTTP error, which almost always indicated a server side (application) rate limit, and a short description to help solve it:
If you find any errors we do not yet cover don't stress, we get notified about any missing errors and will add to the system over time. As always, should you have any feedback please get in touch we love to hear it!
We've released quite a few new features in the last week, be sure to also check out:
Other interesting articles from our load testing experts:
Three New Test Examples
We have added three new locustfile guides we'd like to highlight. Random User Agents, Logging in with Basic Auth, and...
We've just launched Notifications
We're proud to announce the addition of our new eser notifications system. It allows users to receive notifications from LoadForge...