Any developers whom have ever created a service that interacts with people via SMS, how did you test you application for integrity under heavy load? Im in the middle of helping the company I work create an appointment reminder system that interacts via SMS among other contact types. This system will be using a 3rd party SMS gateway (SMS API), and will quite possibly send thousands of texts a day (or more). Issue is there are only 9 people in the company, and we cant gather that many phone numbers. Any ideas on how to test the ability to text several hundred people at once or several thousand a day? How do you load-test your application if you don't have thousands of phones with different numbers?
Website Load Testing Tool
You will have to set up kannel gate, and push messges to smpp or http interface, then you can count and verify messages received by kannel. SoapUI usage described in the link above. They have great knowledge base on it.
Load testing – real, serious load testing – is hard. In a perfect world, you want to exactly simulate the kinds of queries that the end users will be throwing. 5 Free RADIUS Server Testing Tools. Be used for load testing and even as an automated pinging and monitoring solution with uptime statistics and email/SMS. Dictionary deities demons bible pdf. Open Source Load Testing. Open Source Load Testing Tools: Which One Should. The Gatling Project is another free and open source performance testing tool.
Selenium Load Testing Tool
To be short just mock http service you need write assertions and use your application on it. But in case you want to test your SMS aggregator nothing would help, and i guess that no one would give you 100 sms/sec for testing or on volume less than 10 millions messages per month – Feb 2 '15 at 22:44. It may be of some help to you. We have once done the same thing in one of our project where we had to test USSD (Unstructured Supplementary Service Data) and SMS (Short Message Service) using the SMPP (Short Message Peer-to-Peer) protocols. Goal was to find a break-point where the CPU usage goes above 80% and Memory usage goes above 70%, for this we had to put load over the application with tones of SMS and USSD codes being fired. We have used the tool for this purpose, it provides the functionality of sending and receiving lots of SMS using the SMPP protocols. The only challenge was its configuration which took a lot time for me and my colleague to complete, for the USSD part we used both JMeter and SMPPSIM.
Application has complete tree-node structure defined for purchasing products like buying a message pack which can be accessed via USSD code.111.12.3# (for example, this code is pointing to a product which can be purchased via USSD call). JMeter simulated load with 500 concurrent users running for Forever (Loop Count = Infinite) and then hitting the web interface of SMPPSIM which in turn was calling the USSD code.111.12.3# through different mobile numbers (test numbers) passed via CSV files to SMPPSIM and then buying 1000s of products simultaneously which increases load over the server to find the breakpoints. From the SMPPSIM and application logs we used to calculate that how many SMS and USSD products got success and how many got failed to deliver & check-out. The irony of the solution was it took several days in its configuration (as everything was being configured over Linux servers and I didn't have knowledge of working over black screens with Linux commands), but it worked and served our purpose well. After that we presented report got the application performance tuned and released the project successfully. I will suggest you too to use the SMPPSIM but first need to do a little study about the same.