Top Banner
Rapid Performance Testing: No Load Generation Required 1
25
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Rpt west13 sb_print

Rapid Performance Testing:No Load Generation Required

1

Page 2: Rpt west13 sb_print

By:

Scott BarberChief Performance Evangelist

SmartBear Software, Inc.

© PerfTestPlus, Inc.

Page 3: Rpt west13 sb_print

Chief Performance Evangelist SmartBear Software, Inc. [email protected]@sbarber

Co-Founder: Workshop On Performance and Reliabilitywww.performance-workshop.org

Scott Barber

Co-Author:Author: Contributing Author:

Books: www.perftestplus.com/pubs About me: about.me/scott.barber

Page 4: Rpt west13 sb_print

Performance Testing

Page 5: Rpt west13 sb_print

System or application characteristics related to:

Speed: - responsiveness- user experience

Scalability: - capacity- load- volume

Stability: - consistency- reliability- stress

What is Performance?

Page 6: Rpt west13 sb_print

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.

Page 7: Rpt west13 sb_print

Performance vs. Load Testing?

Performance is to Load

Rectangle is to Square

as

Page 8: Rpt west13 sb_print

The Performance Lifecycle is:

Conception to Headstone

Not

Cradle to Grave

Page 9: Rpt west13 sb_print

Who is Responsible?

Page 10: Rpt west13 sb_print

Where does it fit in the SDLC?

Page 11: Rpt west13 sb_print

Personally, I’m fond of…Performant Application Delivery

© PerfTestPlus, Inc.

Page 12: Rpt west13 sb_print

Preventing Poor Performance witha little work…

every day…from every one.

© PerfTestPlus, Inc.

Page 13: Rpt west13 sb_print

© PerfTestPlus, Inc.

Page 14: Rpt west13 sb_print

© PerfTestPlus, Inc.

Page 15: Rpt west13 sb_print

“DevOps” Perf Team Individual

• Code Profiling• Requirements Revision• Design Validation• Budgets• Units & Components• Monitoring• Tuning

• Load/Stress Testing• Environment Config• Capacity Planning• Concurrency Checks• Situation Analysis

• Snapshots• Comparisons• Niche Concerns• Mini-Field Studies

(UAT)• “What-if…”

Key Points• Entire Lifecycle • Entire Team Focused• Individual, Role, & Team Accountability & Responsibility• Continuous & Collaborative

© PerfTestPlus, Inc.

Page 16: Rpt west13 sb_print

… to address random performance questions.

© PerfTestPlus, Inc.

Page 17: Rpt west13 sb_print

RPT is:Inspired by Rapid Software TestingConsistent 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

Attribution

Page 18: Rpt west13 sb_print

“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?

--Addendum added by: Scott Barber

Evolved from:

Page 19: Rpt west13 sb_print

…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?”

Which is…

Page 20: Rpt west13 sb_print

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 answerB) 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

What is it?

Page 21: Rpt west13 sb_print

1. Receive Question• Clarify the question• Understand the driver(s) behind the question

2. Generate Test Coverage Outline (TCO) (~20 min)• Simplest path to (partial) answer(s)• Comprehensive path to (partial) answer(s)

3. Transform TCO into Rapid Strategy (~20 min)• Only tasks that fit in time box• Stick to tasks requiring available resources

4. Execute Strategy (~2.5 hrs)• Snapshots are your friends• Anecdotal is sufficient

5. Consolidate/Analyze Data (~30 min)• Identify patterns• Confirm patterns (time permitting)

6. Report Results (~20 min)• Answer(s) / Time or Effort to get answer(s)• Follow-on questions of interest

~4 hr

Conceptual Approach

© PerfTestPlus, Inc.

Page 22: Rpt west13 sb_print

Addendum

Page 23: Rpt west13 sb_print

The Bottom Line

© PerfTestPlus, Inc.

Page 24: Rpt west13 sb_print

Questions?

Page 25: Rpt west13 sb_print

Contact Info

about.me/scott.barber

Chief Performance EvangelistSmartBear Softwear, Inc.

E-mail:

[email protected]

Blog:

scott-barber.blogspot.com

Web Site:SmartBear.com

Twitter:@sbarber