5 min read · Performance Testing · Telecommunications
Non-functional testing across browser, mobile, DVR, Roku and Xbox for a US cable operator
Quality Engineering · Performance & endurance testing
Engagement
How the work ran.
Client names and implementation details are withheld where they are not approved for publication.
Case study
Challenge
A US telecommunications and media company serving 32M+ customers needed peak and endurance proof for an auto-scaling AWS video estate spanning smart devices — replacing brittle Core-Java load scripts while holding 99.9% success and availability.
Approach
Over 12 months VST ran 30+ peak tests and multi-day endurance runs (120 hours each), captured device APIs with Fiddler and Wireshark, and rebuilt load as JMeter scripts that dynamically emulate an online video player.
Engagement model
Quality Engineering · Performance & endurance testing
Technology
JMeter, Fiddler, Wireshark, Instana, Splunk, AWS
Outcome
15,000 peak concurrent users sustained against 99.9% SLAs; 100+ performance defects raised with monitoring uplift.
Industry
Telecommunications
Practice
Quality Engineering
Value delivered
- Endurance runs exposed storage that would saturate in 48 hours.
- Findings included cache behaviour, data integrity and sticky-session server errors.
- Instana and Splunk gave architects a single view across solution components.
Related cases
Nearby engagements by category, industry or stack.
Open another story that shares the same delivery lens or technology footprint.
Related practice
Release with confidence, at the pace the business needs.
Quality Engineering — Quality engineered into the delivery pipeline — automated, continuous and covering function, performance and security.
This engagement sits inside our Quality Engineering practice. Explore the full scope, outcomes and how we usually start.
Explore Quality Engineering →Next step
Have a similar problem — or need more clarity?
If this challenge looks like yours, book a short discovery call. If the problem is still fuzzy, we will help you name the constraint before anyone builds a large plan.
Start a conversation
Tell us whether you need software built, a release assured, or operations taken on.
Start with a 2–8 week advisory if the problem is still a choice — then a project, a named engineering team, or managed operations.
- Phone
- +91 70303 83783