Posts

Showing posts with the label Performance Testing

Network Emulation in Performance Testing

In today's interconnected world, conducting performance testing on the LAN with excellent bandwidth, low latency, zero corruption etc. and released onto a WAN directly don't make sense.  Identifying network related issues during end of release cycle by conducting performance testing from cloud or data center also is not a good idea.  If performance testing needs to be added in the development cycle than emulation of WAN like environment becomes very important. Different connection types that might need simulation: VoIP/RoIP Satellite Cloud DSL/ADSL/XDSL Microwave OC-3 2G/3G/4G T1/T3/E1/E3 Wifi/WiMax GPRS Dial up Different network conditions that might need simulation: Busy Peak Times Limited Bandwidth Long Distance Information Corruption Jittery Connections De-Sequencing of Data Duplication of Data Network Traffic Bursts Fragmentation of Data Partial or Total Outage

Mobile Performance Testing Checklist

Mobile Performance Testing Checklist Smartphones & tablets are the reality and a large mass of people are moving to use it for bussiness applications, entertainment, social networking, healthcare applications etc. It's mandatory for businesses to assess performance of mobile apps before releasing it to public. Responsiveness of mobile apps is one of the big factor for organization to capture the market. Below are list of things to consider specific to mobile performance testing. Have you considered- Client side considerations Application performance against different mobile phones in the market? CPU utilization Memory utilization I/O Cache size availability Rendering (2D / 3D) Application performance against different mobile phones & browsers in the market? JS Engine processing Number of threads executing the requests Memory leakage by the application? Battery consumption by the application? Internet data usage by the a

Checklist for Designing Better Performance Test Scripts

Checklist for Designing Better Performance Test Scripts Make sure the script doesn’t contain incorrect or extraneous URLs. The urls specified should be in correct sequence. It might be possible while recording, script writer would have gone to his / her popular website. It can be validated by using test tool’s “playback” feature to confirm what the script actually does. Identify all dynamic data (as the response from server) present in a script and correlate it. Usually it can be found by recording scripts two times and making comparisons between them. Parameterize scripts to support dynamic data set. In presence of dynamic data, every simulated user exercises the exact same path but avoids responses from the cache and exercises database interactions properly. Use proper checkpoint(s) / assertion(s) for all steps involved in the transaction. Absence of checkpoint might result in better response time when a page is not getting downloaded completely / correctl

Performance Testing Questionnaire Template

For latest article on this topic, please check here 1.          Project Context   What is the system needed for? (Brief description of project) Who are the end users of the system? Do you have any existing performance concerns? When would you like to start the assignment?  When would you like to finish it? Domain (use þ ) o Retail                        o Insurance                              o Healthcare o Avionics                    o Real time/Embedded             o Enterprise E-Biz o Games                      o Others (Please specify: ____________________) o BFSI Technical (use þ ) Type of application o Client Server                         o Web Application                    o Multimedia                o Consumer Electronics             o Others (Please specify: ____________________) Architecture of the system (2/3 tiers

Sample Performance Testing Run Report

Image
                                                Performance Test Report For XYZ Client For 250 Concurrent Users (1 st Run)             Revision History A – Added, M – Modified, D – Deleted S. No Date Version No Page No Change Mode (A/M/D) Brief description of change 1 09-06-2010 1.0 All A First Performance Report – For 250 Concurrent Users 2 10-06-2010 1.1 All M Added observations 3 4 5 6 7 Table of Contents 1       Introduction .. 3 2       Definition and Acronyms . 3 3       Document Reference . 3 4       Test Environment .. 3 4.1        Load Ge