Customer story · Performance testing
The year performance testing moved in-house
CommScope was asking for SAP performance tests so late in the lifecycle that the results could not change the outcome. They wanted the capability on their own team. We built it there.
01
Who CommScope is
CommScope is a telecommunications company founded in 1976. It started in coaxial cable for cable TV providers and now builds fiber optic cabling, wireless network equipment and infrastructure management systems.
02
Why the outsourced testing model was the problem
Leadership knew performance testing mattered on large projects. The outsourced model put both the process and the knowledge outside their control. Tests were requested too late in the lifecycle to mitigate what they found, with conversion deadlines approaching. Acquisitions added platforms and shifted timelines.
The outsourced model bought coverage and cost them speed and control. Nothing found in a late test could be acted on in time.
When in the project the test was being requested
The later a test runs, the less of the project is left to fix what it finds.
03
What late discovery costs, in the published research
Among the projects that ran over budget, the most common cause was an unexpected need for additional technology, which Panorama attributes to organizations finding fatal misfits late in the project. CommScope was asking for performance tests at the point where finding a problem no longer left time to fix it.
Panorama Consulting Group, The 2026 ERP Report. 170 organizations, January 2025 to January 2026. Covers enterprise software projects broadly. Does not isolate SAP performance testing.
04
Converting 72 SAP test cases to NeoLoad
SAP is not a standard HTTP application. Test scripts are built around the sequence of objects. Correlations and parameterizations are the wrong unit here, which takes SAP-specific skill and the specific tool.
- Load testing at expected conditions
- Stress testing to the breaking point
- Multi-hour endurance testing across multiple geographic regions
- Real-time monitoring during the tests
We converted 72 test cases to Tricentis NeoLoad, and the concurrent user load we proved was double what CommScope asked for.
“… there are so many variables and so many things that have to be modeled in order to do your performance tests because you’re typically not doing that in your production environment. I think the insight Perform brought to the table opened up our eyes to another way of thinking.”
Frank Kamely, Director, Information Technology, Testing & Automation at CommScope05
What CommScope has now
| After the engagement | |
|---|---|
| Test cases converted | 72, to Tricentis NeoLoad |
| Concurrent user load proven | Double what CommScope asked us to prove |
| Testing coverage | Load, stress and endurance, with system limits mapped |
| Endurance testing | Multi-hour, across multiple geographic regions |
| Budget and timeline | On budget, conversion ahead of schedule |
| Testing capability | Running on CommScope’s own team |
This engagement transferred a capability, so the results are scope and ownership. There is no before-and-after response time on this page, because before-and-after response times would measure a different kind of work.
“Perform had an absolute willingness to work with us and stay on target as schedules were constantly revised. Perform has the highest level of professionalism and technology experience. Perform is my first choice out of all vendors I have used for performance testing.”
Frank Kamely, Director, Information Technology, Testing & Automation at CommScope30 minutes with the engineer who would do the work. Bring the release that worries you, and you will leave knowing what it takes.