The PAC aims to promote engagement between various experts from around the world, to create relevant, value-added content sharing between members. For Neotys, to strengthen our position as a thought leader in load & performance testing. Since its beginning, the PAC is designed to connect performance experts during a single event. In June, during 24 hours, 20 participants convened exploring several topics on the minds of today’s performance tester such as DevOps, Shift Left/Right, Test Automation, Blockchain and Artificial Intelligence.

1. Life Shift in Performance Testing
- Gayatree Nalwadad –
Principal QA Engineer @ Fidelity Investments
ECS – Enterprise Cyber Security

2. • What do the Exécutives want?
• Important phases in Performance Testing
• The Playbook for Performance testing Process
• What’s and How’s of Method level testing in Agile world
• Importance of Results Analysis
• Performance Testing Troubleshooting Techniques
• Performance Reports Representation
• Collaboration within the Agile Team and the stakeholders
• Retrospective regime

3. Innovation is our Legacy
Quality is our Priority
Samsung Tagline
Quality is Everyone’s Responsibility

4. What do the Exécutiveswant?

5. Important phases in PerformanceTesting
Capacity data

6. The Playbook for PerformanceTestingProcess
Standard Approach (Waterfall)
 All phases of performance testing
 Regression
Agile Approach
 Sprint based testing
Scenario based / toned down approach
 Customize the process for fast failure
Educating the team on the PERF concepts and terminologies
 like TPS, 5 min Peak TPS

7. What’s and How’s of MethodLevelTestingin AgileWorld
• Performance Testing in Agile
Sprint Planning Sprint in Action Sprint N Retro Deployment
Gather NFR/Review Changes
Write PERF Scripts
PERF DIT Testing(VMs)
PERF Testing
Design workload Capacity, Stress Tests
Spike, Longevity Test
Monitoring / Capacity
Data
Exit Criteria/Signoff
Dynatrace
Test Data setup

8. Importance of Results Analysis and Monitoring
 What are the data points/parameters
 How the parameters correlated
 What type of reports
 PROD monitoring to catch issues show-up after long usage
 Investigator hat
 Right monitoring queries

9. PerformanceTestingTroubleshootingTechniques
• Dependency of the type of error/issue at hand
• Where to start?
• Look for errors in the tool, in the app error logs
• Which layers to look
 Tool->Script->Data->App->Webserver->Middle layer->DB
• Different Hats to wear! Investigator hat, System engineers hat
• Finding thread NOT safe code
• Thread dump Analysis
• GC behavior

10. PerformanceReportsRepresentation
 Types of Reports (HTML, Word, PDF, xlsx)
 Parameters included in the report and what they say
 Key metrics indicator
 Comparison reports
 Trending reports
 Presenting and Sharing with the team and stake holders

11. Collaborationwithinthe Agile Teamand Stakeholders
• Internal team communication
• Direct Communication with Stake holders
• One-on-ones with team members
• Educating the team on the performance processes
• And knowing what help is needed from performance testing
and supporting the team

12. RetrospectiveRegime
 The Bi-weekly dedicated time to reflect and review on the work done by team is a powerful time
 Helps to tune the process early in the cycle
 Different perspectives