November 12, 2012

Introducing Resource Thief for Desktop Application Stress Testing

Helix ALM
Community
We've just released a new tool to make stress testing of desktop applications easier! Resource Thief allows you to better understand how your desktop applications behave in unfavorable operating environments.
  • Simulate disk, memory, and network limitations
  • Run existing test cases under simulated conditions to assess and improve application behavior in stressed environments
  • Spend more time testing because you'll no longer have to maintain virtual machines or create crazy configurations in the lab to test application behavior
This isn't a tool you're likely to use every day, it's better deployed near the end of a sprint or release cycle to verify application behavior at the boundaries. It's targeted at developers, testers, and support folks to help them test and better understand application behavior in less-than-ideal environments. When's the last time you actually verified application performance under your advertised minimum system requirements? What happens if your customer is on the road and loses wifi right in the middle of working on something with your tool? These are things that don't really matter until they do—and a  customer is on the phone wondering why your application crashed and lost all of their work.

For Software Testing

Developers and testers are all doing testing today, and this is a simple tool that anyone can pick up and start using in about 30 seconds. Fire up Resource Thief near the end of a development cycle and verify that things work when the network connection dies, a hard disk runs out of space, or memory is limited.

For Support

When a customer reports an issue and is running on a system that just barely meets your minimum system requirements, how do you reproduce it? Your team members have all upgraded to the flashy new Windows 8, so it'll be hard to reproduce a seemingly random crash the customer is experiencing on XP. Jeff wrote a great blog post along those lines, re-hashing just how hard it can be on support folks to track down these kind of issues and provide helpful information for development to fix them.