|
|
|
STAREAST 2006 Concurrent Sessions
Go To: Agile Methods | Exploratory Testing | Outsourced Testing | Performance Testing | Security Testing |
Special Topics | Test Automation | Test Management | Test Metrics | Test Techniques
View by Date
| Performance Testing | | | Wednesday, May 17, 2006 11:30 AM |
Trends, Innovations, and Blind Alleys in Performance Testing
Ross Collard, Collard and Company
Scott Barber, PerfTestPlus
Join experts Scott Barber and Ross Collard for a lively discussion/debate on leading edge performance testing tools and methods. Do you agree with Scott that performance testing is poised for a great leap forward or with Ross who believes that these “silver bullets” will not make much difference in resolving the difficulties performance testing poses? Scott and Ross will square off on topics including commercial vs. open source tools; compatibility and integration of test and live environments; design for performance testability; early performance testing during design; test case reuse; test load design; statistical methods; knowledge and skills of performance testers; predicting operational behavior and scalability limits; and much more. Deepen your understanding of the new technology in performance testing, the promises, and the limitations.
• The latest tools and methods for performance testing
• Opportunities and limitations for performance testing complex systems
• Compare the effectiveness of your performance testing to others |
| | | Wednesday, May 17, 2006 1:45 PM |
Using Production Failure to Jump Start Performance Test Plans
Sandra Bourgeois, Massachusetts Mutual Life Insurance Company
Learning from a production system failure is not a model MassMutual Financial Group would have chosen. However, when one of their key applications failed under load in production, they turned on a dime and changed their performance testing approach, focus, and capabilities. Let’s set the scene: They ran large numbers of transactions through a performance test tool and, then, went live with a new application that was to be used by all their key users. Within hours, the application had ground to a virtual halt under normal production load. What went wrong? Join Sandra Bourgeois to find out not only what went wrong but also what they learned from failure and how they set about to improve their knowledge, skills, and tools. This is your chance to learn from their mistakes and avoid repeating them in your organization.
• Lessons learned from the performance failure of a mission-critical application
• DITL (Day In The Life) performance test and why you need one
• Component and integrated performance tests of complex architectures |
| | | Wednesday, May 17, 2006 3:00 PM |
Progressive Performance Testing: Adapting to Changing Conditions
Jeff Jewell, ProtoTest LLC
An inflexible approach to performance testing is a prelude to disaster. “What you see at the start isn't always what you get in the end,” says Jeff Jewell. Based on his experience performance testing applications on numerous consulting projects, Jeff demonstrates the challenges you may face testing your applications and how to overcome these obstacles. Examples from performance testing on these projects will demonstrate some of the ways that changing conditions of the projects and the information they discovered in early tests caused the testing approach to change dramatically. Find out how hardware configuration, hardware performance, script variations, bandwidth, monitoring, and randomness can all affect the measurement of performance. Learn to use the data from early tests to guide the rest of the performance testing effort and take back new insights in what to look for to make your tests accurately predict production performance.
• Real-world examples of e-commerce and online banking performance tests
• Performance testing challenges presented by test environments
• Using early performance tests to guide the way |
| |
|
|
