Unit Testing has settled into the mainstream. As developers, we write code that checks code, ensuring that the outcome matches some expected result. But, are we really? As end-users (which includes each one of us from time to time), when we ask a question, we don't just expect our answer to be right, we expect it to be right now. So as developers, why are we only validating for accuracy? Why aren't we going for speed? During this session we'll discuss meeting the performance needs of an application, including developing a performance specification, measuring application performance from stand-alone testing through unit testing, using tools ranging from Team Foundation Server to the command line, and asserting on these measurements to ensure that all expectations are met. Your application does "right." Let's focus on "right now."

1. going for speed
T E S T I N G A G A I N S T
P E R F O R M A N C E E X P E C TAT I O N S

2. why does
performance
matter?

3. poor performance = ?

4. stuck in traffic
in detroit
60hours
per
year
tinyurl.com/3c3df9g

5. flight is delayed
with american airlines
26%tinyurl.com/3j9hmje

6. auto fuel efficiency
power to the wheels
20%www.fueleconomy.gov/feg/atv.shtml

7. an annual loss of
$1285.66% www.fueleconomy.gov/feg/atv.shtml

8. poor performance = wasted time & money

9. why does
performance
matter to developers?

10. ?
throw at it?
what can we

11. more hardware!
let’s throw

12. more resources!
let’s throw

13. your overtime!
let’s throw

14. poor performance = a miserable life

15. suffer
does my app
?

16. 75%
sustain under

17. r:% advanced
metrics

18. but all that really matters...
perception

20. goals
establishing

21. what is the
target?

22. avoid buzzwords99.999% of the time

23. target
threshold
vs.
↼
↼

24. constraints
and
budgets

25. assumptions
validate

27. plan.execute( )

28. unit analysis
//MSTest Example
[TestMethod]
public void ShouldDoThis()
{
// Test Functionality
}

29. unit analysis
//MSTest Example
[TestMethod]
public void ShouldDoThisInUnder100ms()
{
// Test Functionality
// TODO: Write code to test for speed
}

30. unit analysis
//MSTest Example
[TestMethod]
public void ShouldDoThisInUnder100ms()
{
var stopwatch = Stopwatch.StartNew();
// Test Functionality
stopwatch.Stop();
int elapsedMs = stopwatch
.ElapsedMilliseconds;
Assert.True(elapsedMs <= 100);
}

31. unit analysis
//NUnit Example
[TestFixture]
public void ShouldDoThisInUnder100ms()
{
// Test Functionality
// TODO: Write code to test for speed
}

32. unit analysis
//NUnit Example
[TestFixture, MaxTime(100)]
public void ShouldDoThisInUnder100ms()
{
// Test Functionality
// Done. Keep being Awesome.
}

33. memory usage
Process.GetCurrentProcess().WorkingSet64
using System.Diagnostics;
GC.GetTotalMemory(false)
using System;

34. visual studio performance explorer
demo
profiling
studio
with

35. web
analysis

36. demo
visual studio web test

37. traffic flow
patterns
ORANVIRIYINCY | FLICKR.COM/PEOPLE/VIRIYINCY

38. demo
visual studio performance test

39. everything
simultaneously
run
!
rule#10

40. isolate data
at all times
!
rule#9

41. real user
test like a
!
rule#8

42. production
test on a
!
rule#7
clone of

43. production
test on
!
rule#6

44. turned off
tests can be
!
rule#5

45. !assumptions
validate your
rule#4

46. !budget
stick to your
rule#3

47. !design
performancestarts at
rule#2

48. want more
information?

49. Microsoft Debug Diagnostics Tool
tinyurl.com/DebugDiag
tinyurl.com/DebugDiagWP (Whitepaper)
Web Capacity Analysis Tool (WCAT)
bit.ly/ffq6dD
JetBrains dotTrace
jetbrains.com
Red Gate ANTS Performance and Memory Profilers
red-gate.com
HP LoadRunner
tinyurl.com/LoadRunner

50. Performance Testing Guidelines
for Web Applications
Microsoft Patterns & Practices
perftestingguide.codeplex.com
J.D Meier, Carlos Farre, Prashant Bansode,
Scott Barber, Dennis Rea

52. rule #1:
quality is
everyone’s job!

53. go for speed

54. # g o i n g F o r S p e e d
jay@aranasoft.com