WAPT Cloud With a Silver Lining
You might have noticed that there are dozens of pretty good web performance testing tools on the market, which makes choosing the right one a tough task. We’ve been there, looking for a performance testing tool that meets our demands, and eventually chose WAPT Cloud by SoftLogica. But it wasn’t ideal. After using it for a while, we are now familiar with some of the issues you may face when working with WAPT Cloud. Read on to find out how you can tackle them.
Why We Chose WAPT Cloud
When one of our customers decided to move his solution to an Amazon environment, we were curious about how this transition would affect load speed and if the transition would improve performance. We knew we needed a decent web application performance tool for testing, so our team researched a bunch of solutions for web that would help us test speed, performance and load.
Since we needed the tool for a single project and weren’t planning on using it continuously, pricing was one of our main concerns. We wanted to find a tool that had an hourly and per-user pricing, not a monthly or yearly subscription. First, we looked at RadView’s WebLOAD, but it required paying for a set number of users a month in advance and we needed something with less commitment. We also skipped Frida because it required a lot of scripting before you could execute performance testing. And, finally, we chose WAPT Cloud from SoftLogica which had the most reasonable functionality/price ratio.
The tool seemed to check every box on our list. WAPT Cloud was created to test performance under load, allowed designing and running tests from the cloud, offered instant test results in the form of charts, supported major web development frameworks, didn’t have a steep learning curve and you only had to pay for what you used – perfect!
WAPT Cloud Issues
Or so we thought. During the setup of WAPT Cloud and while working with it, we bumped into a couple of obstacles that you are likely to face too.
First, there are hidden payments. WAPT Cloud charges include:
- Main WAPT Cloud instance ($5 per hour)
- Expanded WAPT load agents instances (2k users cost $10 per hour)
- VAT taxes for each instance (around 13-15% of the WAPT charge)
- AWS service charge for each instance ($0.567 per On Demand Windows m3.xlarge Instance Hour)
- AWS VAT (around 13-15% of WAPT charge)
Immediately after an instance is launched, WAPT Cloud charges you for the current and the next hour. For example, if you launch an instance at 3:55 P.M. and stop it at 4:01 P.M., you’ll be charged for two hours. Basically, you’ll be charged for every hour since the launch of an instance until you stop it, so never forget to do that. Here’s a piece of advice: it’s better to start an instance at xx:05 and stop it at xx:55, because it takes some time for the instance to finish a session.
We also faced difficulties with Amazon while trying to set up an additional machine for 2K users. Mind that to operate properly, all virtual machines have to be in the same WAPT Cloud security group. But because this setup was automatic, it automatically added the 2K machine to the wrong security group, and we couldn’t connect it to WAPT Cloud simply because it wasn’t visible.
For test recording, we recommend setting up a simple 30-day-free-trial version of WAPT on your Windows machine. The script can later be edited in terms of adding or removing additional parameters if needed, without spending money on AWS. You can easily move all test scenarios and setup parameters to the AWS WAPT Cloud using cloud services that can be managed via a web browser like Google Drive, Dropbox, etc.
We recommend recording scenarios using the embedded browser of the Windows machine – Internet Explorer. If you use Chrome, it will also record analytics, ads and pages you don’t need, possibly leading to errors during performance/load testing. Also, keep in mind that WAPT is a recording proxy server application and may record post/get requests from your Outlook, Skype etc. So, it’s better to record scenarios on a “clean” machine.
And, last but not least – the support of WAPT Cloud and AWS. SoftLogica, the company that created WAPT Cloud and is responsible for its support, sometimes answers emails immediately, but it often takes them 24+ hours to get in touch with you. And because of the time zone difference between Eastern Europe and the US, you’ll receive answers from Amazon’s support at the end of the working day, which isn’t very convenient. However, both support teams are willing to help and can provide alternate ways to fix issues with their software.
Over the two weeks that we’ve been using WAPT Cloud, our team has had some ups and downs with it. Still, we consider it a great web app testing tool and will keep using it for our future projects. Now that you know some peculiarities of working with WAPT Cloud, we hope you’ll enjoy using it too.