how to save money on performance testing preview

How to Save Money on Performance Testing?

One of the main reasons is a widespread misbelief that testing your system is rather expensive. In some cases it is not cheap, indeed, say, when you want to test a complex system in a short time before release. But such situations are rather an exception than a rule: much more often, system performance testing requires a very moderate budget, while offering an opportunity to save money! How? Read further, and find out!

bank increases load capacity by 450 to deal with business growth preview

Bank Increases Load Capacity by 450% to Deal with Business Growth

Our client’s bank was absorbing other banks, and the number of individual clients was growing. The system was not ready for expansion or integration. The owners started to suspect bottlenecks when problems with paying salaries to corporate clients’ employees arose. As a result, in the next pay period, the load on the system increased dramatically, and the system got overloaded. People did not get their salaries in time, as the system crashed.

API Micro Focus ALM and Performance Center preview

API Micro Focus ALM and Performance Center: Basics for Performance Testing Engineers

In this post, we are sharing our experience of using API Microfocus ALM in the hope that load testing engineers who use LoadRunner or Performance Center will find it interesting. Working with API directly is useful for test automation, and/or to prepare for test launch with Jenkins or similar tools. We collected this list of examples and useful functions based on our experience.

Automating Performance testing results Best Practices preview

Automating Performance Testing Results: Best Practices. Part 3

In Part 1 of this tutorial, we had a close look on how to update your load testing environment to make load testing results automation possible. Instead of preparing your load testing report manually for days, with the environment discussed above, your data structure will depend on you, not you on your data structure.

In Part 2, we’ve tackled a problem that engineers in every load testing company complain about, — namely, how Grafana slows down the system, — and several other quick fixes to your Grafana dashboards. We plunged into multiple databases and data sources, retention policies and tag filters.

Finally, in this part we want to enable you to automate your test reports using all the infrastructure you have hopefully designed after reading through parts 1&2.