vodqa-chennai-20jul2013: performance testing on desktop
TRANSCRIPT
![Page 1: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/1.jpg)
RE-THINKING PERFORMANCE
TESTING
![Page 2: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/2.jpg)
CATEGORIES
Performance
Load Stress
• Not for finding bugs• Response/Interaction
times• Profiling• Planning & forecasting• Infrastructure decisions
• Identifying limits• Identifying load
characteristics• Planning & forecasting• Infrastructure decisions
• Identifying app behaviour outside boundaries
• Identifying graceful handling strategies
• Planning & forecasting• Infrastructure decisions
![Page 3: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/3.jpg)
DESKTOP APPS• Do not have multiple users accessing
simultaneously
• Reduced network consideration
• Reduced shared resource consideration
• Data store can be co-located
• Common expectations around response of native applications
• Testing requires different approaches
![Page 4: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/4.jpg)
APPROACH
Data Access
Modules
Presentation Model
![Page 5: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/5.jpg)
A SAMPLE APP
![Page 6: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/6.jpg)
METRICS
![Page 7: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/7.jpg)
ADVANTAGES• UI finicky-ness eliminated
• Relevant performance numbers gathered
• Fluff reduced
• Easier to maintain
![Page 8: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/8.jpg)
DISADVANTAGES• Code intensive
• Requires significant dev involvement
• UI-Presenter hook-up performance might be missed
• Over-enthusiastic test-optimisation might skip vital layers
![Page 9: vodQA-Chennai-20Jul2013: Performance Testing on Desktop](https://reader035.vdocument.in/reader035/viewer/2022071814/55a50a4b1a28abc43e8b45d2/html5/thumbnails/9.jpg)