Digital Experience Monitoring (DEM) Software Resources

Naveen, There are several ways to shift forward to leverage the CX Models from the QA team. The first method is to leverage the CX Model, as the visual design and customer journey map. Meaning created the CX model in place of a traditional visual tool like Visio. By laying out the journey in the CX model the developers can leverage the test cases as they code to ensure things are working as designed. The QA team will be able to leverage and expand upon the test cases generated from the CX Model. This would start all the way back in the design phase of the project. it is a mind shift to think about testing prior to writing the code. The second way to leverage the CX models for the QA team would be to leverage the crawling / auto discovery function of the CX Model. This is used in cases where the coding was done and now we need to build the test case library. By calling from Cyara CX Model each journey can be documented and test cases can be auto-generated. The QA team can now run the different tests and test accounts multiple times to ensure the goals and tests are completed and successful. One of our customers talked at our xChange2020 online event about their journey to automation. https://cyara.com/lp/xchange-2020-session-replays/ I would recommend watching the session Automated Testing for the IVR by Mark Shaw for some additional insights. If you have more questions please feel free to let us know. Bill LaRuffa Solutions Architect Manager - NALA Cyara.

Ideally we start by showing them the ease of documenting an IVR via the Crawler to start with, and then show how test case creation can be streamlined once a CX Model is populated sufficiently. Then, once the initial concepts are introduced the internal (customer) power users would then hand hold them through some of the more advanced concepts like Modules, Decision nodes and Data Driven modeling. Once the user can adopt the more advanced concepts in CX Model design you can start populating Test Data and create data files (or import filtered data files from a Master data file) to allow you to achieve very fine control over test case creation. In parallel with teaching more advanced concepts, you promote mastery of starter concepts by working to get the CX Model completed down all branches. This can be adopted as part of your normal documentation processes, developing your IVR and CX Model in parallel to ensure your system of record and your QA platforms are always in sync. Additionally, your Customer Success Manager is an excellent resource to assist you in finding resource available to assist with that training and adoption goal. Resources available include the knowledge center, learning management system and Customer Success led workshops. For more in depth and targeted training, Cyara also has a training department that can provide instructor led training.

Hi there Hugo, Thanks for reaching out! We do have options for further customizing error groups. You can set up your own custom error group hasher by creating a GroupingKey that sets your own grouping options, and passing the GroupingKey through on the error payload. By adding the GroupingKey in the onBeforeSend (https://github.com/MindscapeHQ/raygun4js#onbeforesend) method you can capture each payload and assign a custom error group id. There is a JavaScript example of setting up custom error grouping on our blog (https://raygun.com/blog/custom-error-grouping/). All the best, and let me know if you have any further questions.