1. The first step in performance testing is to capture non-functional requirements from stakeholders to define test scope, targets, resources, and deliverables. 2. The second step is to build a test environment that closely approximates production, including necessary load injection capacity and monitoring. 3. The third step is to script use cases, identifying session data, input requirements, and checkpoints for each use case. 4. The fourth step is to build test scenarios defining test type, users, load profiles, and monitoring for each performance test. 5. The fifth step is to execute the performance tests, running dress rehearsals and different test types in a cycle of execution and problem resolution.

1. The Process of
PerformanceTesting
FromThe Art of PerformanceTesting, Chapter 4
Presentation by Sebastián Lagoueyte

2. Last-Minute Exercise
Limited time to test.You have to deploy at a certain date.

3. PerformanceTesting Approach
So you don’t fall to the same pitfall

4. Non-functional Requirements Capture
(NRC)
Step One

5. “A Scoping Exercise”
Gather performance NFRs from all relevant stakeholders.

6. At the very least
Deadlines
Resources (internal or external)
Test environment
Key use cases
Performance targets
Deliverables
Procedures

7. Allow enough time to
capture all of the Non-
Functional Requirements
This usually takes a couple of days

8. PerformanceTest Environment Build
StepTwo

9. Test environments
should be a close
approximation of the
production
environment.

10. To build:
1. Allow enough time to configure
2. Take into account all deployment models or environments
3. Also take into account links to external systems
4. Provide enough load injection capacity
5. Ensure that the application is correctly deployed
6. Provide software licenses
7. Deploy performance testing tool
8. Deploy Key Performance Indicator (KPI) monitoring

11. Use-Case Scripting
StepThree

12. Some use cases require more time to script
than others. Allow half a day per use-case.
Ideally, most of the work is done for you before testing.

13. For each
case, you
should…
Identify the session data requirements.
Usually happens after you begin.
Confirm and apply input data
requirements.
Decide how you will checkpoint the use
case.
Indentify and apply any scripting
changes required.
Ensure that the use case replays
correctly.

14. PerformanceTest Scenario Build
Step Four

15. This should be simple, since you should have defined
each performance test as part of your NRC.

16. Consider
What kind of test will this represent? (Pipe-clean, volume, soak, stress)
Decide how many load injectors and virtual users you require
Decide on each load injector profile (Big-Bang, Ramp-up, Ramp-
up/Ramp-down, delayed start)
How long will the test run for?
Do you need to spoof IP addresses?
Do you need to simulate different baud rates?
What runtime monitoring needs to be set up?
Any effects that the application technology will have on your test

17. PerformanceTest Execution
Step Five

18. Run and monitor your tests. Carry out a dress
rehearsal of each performance scenario.
This should be straightforward. It should be a matter of validating
your application’s performance targets.
The only unknown is how many test cycles will be
required.

19. Execution process order:
1. Execute dress-rehearsals or pipe-clean tests as a final
check
2. Execute volume tests
3. Execute isolation tests to explore revealed problems
4. Execute stress tests
5. Execute soak tests to reveal memory leaks
6. Execute any other tests that are not performance related

20. Allow a minimum of five days.
Reruns of the testing cycle will be required, since any problems that surface
during execution have to be dealt with

21. Post-Test Analysis and Reporting
Step Six

22. The final step consists of collecting and analyzing data
from all tests run
You also create reports, a performance baseline and possibly retest

23. Carry out final data collection
Uninstall software
Determine success or failure (following performance targets)
Document the results

24. QuestionsTime

25. Why should you ensure that the application is
correctly deployed? (in the test environment)
What’s the most common problem with
PerformanceTesting?

26. Thank