We simulated three scenarios simultaneously:
– creation of 40,000 new customer accounts
– completion of the full purchase process (login, delivery method, payment, confirmation email)
– load on the product search engine

We replicated the scenario of adding a random product to the cart, selecting a shipping method, filling in data, and proceeding to the payment confirmation stage — where the process stopped during mobile banking authorization.
The next scenario verified whether products remained in the cart upon returning to the store and tested the ability to complete the order.

We prepared bandwidth load tests using dynamically changing locations. The tests revealed that the client had only one uplink, which turned out to be a critical weakness. In addition to stress testing, we provided a set of recommendations for optimization and performance improvements.

We implemented continuous monitoring of all banners and ad display correctness. Each page was retrieved in full size (1908×13801 pixels, ~20 MB). Data was stored for 3 months, and error/unavailability alerts were sent directly to the responsible asset owner.

We accepted the challenge. For the production application, we prepared a login scenario using the trusted profile with authorization through the mObywatel app and online banking. The scenario was executed every 3 minutes, each time from 3 random locations chosen from a pool of 30. Locations included wired, wireless, and satellite (Starlink) connections.

To verify service availability, we implemented a login scenario with trusted profile and authorization. This provided real-time observation of the production account and environment.

We prepared bandwidth load tests using dynamically changing locations. The tests revealed that the client had only one uplink, which turned out to be a critical weakness. In addition to stress testing, we provided a set of recommendations for optimization and performance improvements.

We implemented continuous monitoring of all banners and ad display correctness. Each page was retrieved in full size (1908×13801 pixels, ~20 MB). Data was stored for 3 months, and error/unavailability alerts were sent directly to the responsible asset owner.

Monitoring the current routing path allowed detection of both packet loss and unexpected changes in routing.
With route monitoring, the client could immediately detect unfavorable path changes leading to their infrastructure from one of the operators. Thanks to quick intervention by network engineers and contacting the operator, the issue was addressed before it impacted performance and service visibility on the Internet.
Route analysis in Monit24, even every minute around the clock, verifies the actual routing path and reports problematic changes to the right people. Alerts enable instant response before the issue becomes visible in network load/interface utilization charts.

In our laboratory, we set up a courier terminal with a scenario covering parcel receipt, dispatch, and completion of W-Z documentation. Alongside scenario playback, we monitored the loading of individual components fetched from several services, requiring VPN authentication.

Our team granted access to PROD access to fully replicate end-user experience. We also installed and configured mobile banking apps. Processes were monitored every minute from over 40 different locations in Poland, including wireless networks. Scenario replay ensured 100% real-time visibility of the production environment.

WebAppCheck simulated completing the insurance purchase form and correctly sending confirmation to the provided email address.
MobileAppCheck reproduced key processes such as policy registration and error notifications within applications. These services ensured a high SLA and shortened response times in cases of unavailability for both B2C clients and field agents.