Performance testing as a part of Agile

About

Andrey Kovalenko

5 last years in IT - again.

3 years of developing and implementing distributed protected networks

2 last years - performance engineer.

kovalenko.andrey.odessa

Performance testing

Performance testing: The process of testing to determine the performance of a software product.

Performance - sub-characteristic of one of the quality characteristic - efficiency.

Why do we need performance?

What is performance?

Load testing - to verify application behavior under normal and peak load conditions.

Stress testing - To determine or validate an application’s behavior when it is pushed beyond normal or peak load conditions.

Capacity testing - To determine how many users and/or transactions a given system will support and still meet performance goals.

Performance testing flow

What do we need for it?Performance testing

=

Performance testing = long and expensive process

Agile&Performance

When?

When?

Performance in Agile - Gut)Code optimization

Application failure

Bottleneck early detection

Release date

Real customer data and scenarios

Resolving performance issues

Cheap! Fast! Quality!

Cheap! Fast! Quality! (Part 2)

HP LoadRunner – best of the best!

Some stuff to learn

• Deep knowledge of HTTP load generation, measurement software• Experience with Oracle/MSSQL Databases and SQL tuning and scripting,

Oracle AWR reports and trace logs Deep knowledge and experience in Windows and Linux OS: Red Hat Scripting: Python, shell, Perl, etc.

• Strong understanding on OS, network, Web servers and browsers.• Strong in performance requirement analysis, and construction of performance

test cases.• Strong understanding of Java, JSP, and JavaScript coding and the use of Java

SDK performance tools.• Experience with HTTP and web services• Deep knowledge in Java Performance (CPU, Memory, IO, SWAP, Network

usage), hotspot detection, GC logs, optimization and analysis of bottle-necks using various profilers.

• suggest option for resolutions of problems Work individually on the tasks, not required full attention from the TL, but yet, a Team player - working closely with Developers, TLs and architect.

• Able to send executive summary of the tests

Q&A