| || |
I am testing the application for mobile handset. It is regarding the SMS and WAP Push, ...
Does anyone know how to do the performance testing for an application for mobile handset?
Re: WAP testing
Testing should be done manually on the mobile device, to generate enough load.
Here are the possible few scenarios...
1) Generate several MO - SMS continuously.
2) Generate several MT - SMS's.
3) Generate several MT - WAP Push messages.
Re: WAP testing
a significant problem here is the unknown transmission time over the Mobile Phone Network and the Exchange(Switches) within it.
When designing a performance test for a transaction using a mobile phone, I have always mapped out the entire transmission path.
e.g. a complete SMS transaction may consist of:
1. Phone user inputs the message on phone and push Send button
2. Phone internal operating system sends SMS to Mobile Phone Network
3. Network sends SMS to a central exchange switch
4. Central exchange determines target phone to send SMS to and sends SMS to network.
5. Network sends SMS to target phone
6. Target phone receives SMS and processes it
7. Target phone alerts phone user
8. Phone user requests to view message
From the above, I can see that there are some parts of the transmission time whose response time is unknown - the network and the exchange switch - hence I try to control or minimise the effect of these parts, e.g. through testing late at night when volumes on the network are low, or by using a local test network and exchange.
As to generating many simultaneous transactions for performance testing, this is very difficult. The best done so far has been to use 20 people all doing preset transmissions for 10 minutes. It is where a network engineer and a phone hardware engineer are needed!