FAQ

Tech questions + Expand All Questions

What is the CloudPuncher testing process?

The CloudPuncher testing process involves the following steps:
1. Create a CloudPuncher account.
2. Record a test using either a dynamic proxy or the AppPuncher recording tool.
3. If a test is recorded using AppPuncher, upload it to your CloudPuncher account.
4. Configure test scenarios.
5. (Optional) Parameterize your test - this will ensure a more realistic test execution.
6. Authorize hosts/domains targetted in the test.
7. Launch your test.
8. Analyze results.

How can I configure a load test?

Once a workflow is recorded you can then use Test Manager's Scenario Editor to configure the test by choosing client allocation policies, termination conditions, performance monitors, etc.

Why is test randomization important?

When a test is originally recorded, it will replay in the original form when conducting the load test.  This is not practical for real-world load testing and won't give you a realistic picture of how your application or website will respond when real users access your site.  CloudPuncher enables you to take an original test and easily introduce additional data sources, including having the ability to substitute different values (value substitution) for various activities that take place in a single workflow.  This process sufficiently randomizes your test scenarios to give you the most realistic test possible, using virtual users.

Am I going to have to write test scripts?

No, you simply record a test workflow and then configure a scenario for it using the CloudPuncher Scenario Editor, which is so simple to use that even a non-engineer could record and run load tests.

My application is built with Flash/Flex on the client side, can CloudPuncher test it?

Yes, CloudPuncher fully supports client/server communication mechanisms used by Flash, Flex and AIR clients. Whether it is remoting or data management requests, CloudPuncher can accurately replay them in the original form or allow dynamic value substitution (randomization).

Can CloudPuncher load test applications set behind a firewall?

Applications or sites deployed internally behind a firewall can be tested using a premise-based version of CloudPuncher. All of the same product features are supported, but the configuration would require additional setup of the computer resources used in a test. Please contact sales@cloudpuncher.com for more information.

Can I monitor our proprietary system while running a load test using CloudPuncher?

Yes, CloudPuncher provides a wide range of built-in monitors for many parts of your server-side infrastructure. These monitors can collect performance information about network resources, databases, web servers, application servers, integration servers, etc.. The system also supports custom monitors which can be registered with the system.