Your SlideShare is downloading. ×
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Rapid Performance Testing: No Load Generation Required
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rapid Performance Testing: No Load Generation Required

61

Published on

Load testing is just one—but the most frequently discussed—aspect of performance testing. Luckily, much of performance testing does not demand the same expensive tools, special skills, environments, …

Load testing is just one—but the most frequently discussed—aspect of performance testing. Luckily, much of performance testing does not demand the same expensive tools, special skills, environments, or time as load testing does. Scott Barber developed the Rapid Performance Testing (RPT) approach to help individuals and teams with the non-load aspects of performance testing. RPT is fast and easy, requires no investment in tools or special skills, is applicable throughout virtually any development cycle by anyone on the team, and most importantly reduces the frequency of those performance issues that threaten, or even negate, the value of load testing. Through examples and case studies, Scott shares the RPT approach and grants you exclusive access to his “Top Secret RPT Tips, Tools & Utilities” webpage. Immediately following this session, join Scott in the TestLab for real-time demonstrations on applications of your choosing and for an opportunity to have Scott coach you while you practice RPT.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
61
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. W5 Concurrent Class 10/2/2013 11:30:00 AM "Rapid Performance Testing: No Load Generation Required" Presented by: Scott Barber PerfTestPlus, Inc. Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
  • 2. Scott Barber PerfTestPlus, Inc. CTO of PerfTestPlus and recognized worldwide as a thought-leader in software system performance and testing, Scott Barber describes himself as a “tester, author, speaker, disrupter, and dad.” Scott is the author of Web Load Testing for Dummies and co-/contributing author of Performance Testing Guidance for Web Applications, Beautiful Testing, and How to Reduce the Cost of Testing.
  • 3. 9/19/2013 Rapid Performance Testing: No Load Generation Required 1 © PerfTestPlus, Inc. By: Scott Barber Chief Performance Evangelist SmartBear Software, Inc. 1
  • 4. 9/19/2013 Chief Performance Evangelist SmartBear Software, Inc. scott.barber@smartbear.com @sbarber Co-Founder: Workshop On Performance and Reliability www.performance-workshop.org Author: Co-Author: Contributing Author: Books: www.perftestplus.com/pubs About me: about.me/scott.barber Performance Testing 2
  • 5. 9/19/2013 What is Performance? System or application characteristics related to: Speed: - responsiveness - user experience Scalability: - capacity - load - volume Stability: - consistency - reliability - stress What is Performance Testing? Testing designed to: Inform software system optimization by balancing: • Cost • Time to market • Capacity while remaining focused on the quality of service to system users. 3
  • 6. 9/19/2013 Performance vs. Load Testing? The Performance Lifecycle is: Conception to Headstone Not Cradle to Grave 4
  • 7. 9/19/2013 Who is Responsible? Where does it fit in the SDLC? 5
  • 8. 9/19/2013 Personally, I’m fond of… Performant Application Delivery © PerfTestPlus, Inc. Preventing Poor Performance with a little work… every day… from every one. © PerfTestPlus, Inc. 6
  • 9. 9/19/2013 © PerfTestPlus, Inc. © PerfTestPlus, Inc. 7
  • 10. 9/19/2013 Key Points • • • • Entire Lifecycle Entire Team Focused Individual, Role, & Team Accountability & Responsibility Continuous & Collaborative “DevOps” • • • • • • • Code Profiling Requirements Revision Design Validation Budgets Units & Components Monitoring Tuning Perf Team • • • • • Load/Stress Testing Environment Config Capacity Planning Concurrency Checks Situation Analysis Individual • • • • Snapshots Comparisons Niche Concerns Mini-Field Studies (UAT) • “What-if…” © PerfTestPlus, Inc. © PerfTestPlus, Inc. 8
  • 11. 9/19/2013 RPT is: Inspired by Rapid Software Testing Consistent with Rapid Software Testing themes Sanctioned by James Bach, Michael Bolton & the RST instructors to as a specific implementation of the Rapid Testing Methodology For more information about RST, visit: http://www.satisfice.com/info_rst.shtml Evolved from: “What have we got? What do we want? How do we get there…?” --Bob Barber (Scott’s dad) … as quickly, simply, and cheaply as possible? 9
  • 12. 9/19/2013 …a common man’s way of expressing the problem solving approach that classical engineers employ. • Given: “What have we got?” • Find: “What do we want?” • Solve: “How do we get there?” What is it? An approach to respond to a specific performance-related question after 4 or fewer hours of team effort with 1 or more of: A) The answer B) A partial answer • • To determine the value of additional effort The level of effort to provide the answer C) Better questions to address the underlying concern 10
  • 13. 9/19/2013 Conceptual Approach 1. Receive Question • • 2. 3. 4. 5. 6. Clarify the question Understand the driver(s) behind the question Generate Test Coverage Outline (TCO) (~20 min) • Simplest path to (partial) answer(s) • Comprehensive path to (partial) answer(s) Transform TCO into Rapid Strategy (~20 min) • Only tasks that fit in time box • Stick to tasks requiring available resources Execute Strategy (~2.5 hrs) • Snapshots are your friends • Anecdotal is sufficient Consolidate/Analyze Data (~30 min) • Identify patterns • Confirm patterns (time permitting) Report Results (~20 min) • Answer(s) / Time or Effort to get answer(s) • Follow-on questions of interest ~4 hr © PerfTestPlus, Inc. Addendum 11
  • 14. 9/19/2013 The Bottom Line © PerfTestPlus, Inc. Questions? 12
  • 15. 9/19/2013 Demo & Resources Scott’s “Secret RPT CheatSheet”: http://qikpad.co.uk/p/RPT Rapid Strategy Examples: http://www.mindmeister.com/267329863?t=UkxsZQfDKF http://www.mindmeister.com/267331147?t=D8tCoW05En http://www.mindmeister.com/267331063?t=AiWwSdPusv Demo: GTMetrix.com WhichLoadsFaster.com Contact Info about.me/scott.barber Chief Performance Evangelist SmartBear Softwear, Inc. E-mail: Scott.barber@smartbear.com Web Site: SmartBear.com Blog: scott-barber.blogspot.com Twitter: @sbarber 13

×