Automating performance testing results best practices part1 preview

Automating performance testing results: best practices. Part 1

In this article, we start with a major topic, and then, in the following parts, we’ll go deeper into super-hardcore stuff.
Test reports automation is the way to optimize testing costs and make performance testing more affordable. By cutting the cost, you will also be able to attract smaller businesses as customers. Good news: test reports automation is possible with the help of such popular tools as Grafana and InfluxDB, that all testers are already familiar with, to say the least.

Contact center and IVR performance testing intro

Contact center and IVR performance testing

Modern contact centers are often complex systems that involve close interaction between IVR, customer relation management (CRM), and many other services. Therefore, besides testing the performance of IVR itself and telephone communication channels, PFLB offers comprehensive testing services that allow you to evaluate the performance of both overall and individual services and to identify the influence of system components on each other.

Performance Testing of Blue Prism Intelligent Robotic Process Automation for Banking

The client is the biggest bank in Europe, with 98 million individual clients, 2.7 million corporate clients, and 278,000 employees. Although they had been using Blue Prism RPA for a while, they decided to perform the first ever load/performance testing of their software, so it was all new to them. PFLB played the guiding part, making the client aware of all the details of load testing and running the service. After the project, the client’s business indicators increased notably, so they returned to us with another service request.

FIS Profile Banking System Load Testing

Our client, a large state-owned bank, pays special attention to the stability of the FIS Profile system which serves more than 65 million customers, 55 million contracts, 9 million loan agreements, and 45 million cards. PFLB conducts banking application testing for each of the system releases. On average, a release contains about ten changes to the functionality of the system, each of which requires detailed elaboration and specific testing.

Banking System Load Testing for Payroll Card Programs

Our client is one of the largest commercial banks, with European offices and state participation. The bank had a goal to minimize performance and resiliency risks in IT infrastructure and salary program systems, such as possible disruptions in payroll card services, payroll accounting delays, and system failures during registry processing.
PFLB provided performance testing of payroll systems. The testing challenge was to understand the structure of component interaction given a variety of registry types and a large status model.

How to speed up jmeter part 2 preview

How to speed up JMeter. Part 2

We continue our series of articles about optimizing the popular load testing service JMeter. In the previous article, we highlighted the possibilities of significantly speeding up JMeter by configuring agent monitoring and optimizing components and service settings. In this part of the Apache JMeter load testing tutorial, we…

How to speed up jmeter part 1 preview

How to speed up JMeter. Part 1

Apache JMeter load testing doesn’t need to be advertised; nonetheless, not enough attention is paid to the load script speed. In this article, we take a look at different approaches to writing load scripts in an optimal way that allows saving money on the load testing machines. This…