Below you’ll find answers to the questions we get asked the most about WebLOAD. If you cannot find the information you need, please contact us.
WebLOAD can be deployed on premise or in the customer’s cloud account (in which case it is managed by the user), or it can be used in a SaaS model. For detailed information on WebLOAD’s cloud deployment options, see this page.
This question may refer to either of the following scenarios. In either scenario the answer is yes:
- If you need to load test an application that runs on the cloud, then yes – it can be tested using WebLOAD regardless of whether you run WebLOAD on-premise or as SaaS on the cloud).
- If you need to generate load from the cloud, again the answer is yes – WebLOAD provides two options for running distributed cloud loads:
- SaaS load testing using the WebLOAD cloud
- Self managed using any public cloud platform
For more information, see this page.
WebLOAD supports a wide range of protocols and technologies, including the most popular these days like Angular, signalR, SAML, WCF, single-page-applications (SPA), and others. For a full list, see the supported technologies page.
WebLOAD’s all-inclusive pricing is affected by the maximum number of concurrent virtual users, your deployment method (SaaS or on-premise), the subscription term and number of testers (single or multi-tester). To determine which of WebLOAD’s flexible pricing options is right for your load testing needs and get a quote, see this page.
Yes. WebLOAD can generate browser-level load using selenium scripts.
See the Selenium Website Performance Testing page.
WebLOAD helps you identify the root-cause of problems by collecting client-side, network, and server-side performance data (from operating systems, web servers, application servers, networks, and database servers) and correlating your load scenario with data related to CPU, memory, capacity, processes, disk I/O, queue data, etc. WebLOAD also integrates with APM tools like AppDynamics, Dynatrace, New Relic and Nagios.