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:
Changes to tests using random
If you use random features in your tests you may notice a new limitation when saving tests, which is that...
Announcing the LoadForge CLI helper
We are proud to announce the availability of lf-cli - our command line tool for easily interacting with LoadForge!