In response to increasing market demand for well-performing applications, many organizations implement performance testing programs, often at great expense. Sadly, these solutions alone are often insufficient to keep pace with emerging expectations and competitive pressures. Scott Barber shares the fundamentals of implementing T4APM™ including specific examples from recent client implementations. T4APM™ is a simple and universal approach that is valuable independently or as an extension of existing performance testing programs. The approach hinges on applying a simple and unobtrusive "Target, Test, Trend, Tune” cycle to tasks in your application lifecycle—from a single unit test through entire system production monitoring. Leveraging T4APM™ on a particular task may require knowledge specific to the task, but learning how to leverage the approach does not. Scott provides everything you need to become the T4APM™ coach and champion, and to help your team keep up with increasing demand for better performance, regardless of your current title or role.
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
Presented by:
Scott
Brought to you by:
340 Corporate Way, Suite Orange Park, FL 32073 888‐2
MH PM Tutorial4/7/2014 1:00 PM
“Managing Application Performance: A Simplified Universal Approach”
hief performance evangelist for SmartBear Scott Barber is a respected leader in the
r
as director of
e
Scott Barber SmartBear
Cadvancement of software testing practices, an industry activist, and load testing celebrity of sorts. Scott authored several books―Performance Testing Guidance foWeb Applications, Beautiful Testing, How to Reduce the Cost of Testing, and Web Load Testing for Dummies―and more than 100 articles and blog posts. Founder/president of PerfTestPlus, Scott co-founded the WOPR, servedthe AST and CMG, and is a founding member of ISST. His industry writing, speaking, and activism focus on improving the effectiveness and business alignment of softwardevelopment practices. Learn more about Scott Barber.
RPT is:Inspired by Rapid Software TestingInspired 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 MethodologyRapid Testing Methodology
For more information about RST, visit:http://www.satisfice.com/info_rst.shtml
“What have we got?What do we want?
Evolved from:
What do we want?How do we get there…?”
‐‐Bob Barber (Scott’s dad)
… as quickly, simply, and … as qu c y, s p y, a dcheaply as possible?
2/19/2014
16
…a common man’s way of expressing the problem solving
h h l i l iapproach that classical engineers employ.
• Given: “What have we got?”• Find: “What do we want?”• Solve: “How do we get there?”
An approach to respond to a specific performance‐related question after 4 or fewer
What is it?
hours of team effort with 1 or more of:
A) The answerB) A partial answer
• To determine the value of additional effort Th l l f ff t t id th• The level of effort to provide the answer
C) Better questions to address the underlying concern
2/19/2014
17
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)
Conceptual Approach
• 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