When you establish a test plan you need to be clear on what you are trying to accomplish. For example sometimes I see asks where customers simply want to place calls in and have this stack up in queue because they are used to other systems and bottlenecks they have seen on those systems. This would not be a relevant test to run.
If you are concerned about throughput to a back-end system and potential bottlenecks then that is something to look at. You should first use your own set of tools to test this directly and then could test end to end. There may also be more efficient ways of testing this end to end than placing calls - such as using digital interactions.
If the test is more complex such as you have developed a custom desktop using APIs, which also have interdependencies with 3rd party systems, and want to test the performance at scale then you will typically want to start with automated 3rd party testing tools so that you can validate the performance under load in a controlled environment prior to end to end testing with Genesys.
And when I mention scale I'm considering thousands of simultaneous interactions. Sure you could develop something that is poorly written/behaved yourself and create problems at a lower load, e.g. calling 10 data actions prior to playing the first prompt in your IVR.
------------------------------
Donald Huovinen
Genesys - Employees
------------------------------
Original Message:
Sent: 01-03-2024 15:57
From: Max Gill
Subject: Load or stress testing of Genesys Cloud
We perform occasional stress tests on integrations to ensure our integrated ticketing/CRM system processes Genesys events at-scale.
------------------------------
Maksim Gill
Eccentex (Advanced Case and Email Management Platform for Genesys)
https://www.eccentex.com/genesys
------------------------------