sergei

Your test should be at least 8 hours 20 minutes.

It means that your firewall was overloaded during the test.

Please clarify, do you record precondition steps or not? To create a correct scenario you need to record all your actions in browser.

I think there was some error during the test. Check the report and test logs. You can send your WAPT logs and Results (*.wpr file) to support. We will try to help you.

What build of WAPT Pro do you use and what are the test settings?

You can verify and run test as usual.

There were 36 simultaneous users only. If you want 1000 users you need to select Run Time option (first on Test Volume page) and enter time enough to start 1000 users. Or you can select Fixed number of users option and enter 1000 users. I don't know your testing objectives so I can't interpret your results. Formally all is OK, sessions are successful, and times are good.

WAPT can't record a Java applet if the applet uses own TCP socket.

In the latest version of WAPT you can just select an external browser for recording.

Your test duration should be more than 24000 seconds.

Current version of WAPT selects Negotiation (Kerberos) or NTLM authentication method as requested in server reply. To enable authentication just mark Authentication checkbox in profile properties and enter user names and passwords.

WAPT supports both methods.

If you use an external browser for recording you should record in it, not in the embedded left-hand pane.

Duration of your test is not enough. A vertical red line on the user load graph shows where the test will be ended.

You can use in Java Script context.variable("var_name") - gets/sets the value of the "var_name" variable.

I think Java Script is the better way to solve this problem.

Save File dialog box appears after download request was sent so no requests after that will be recorded. Note that WAPT downloads files but doesn't save them on disk. If you have any problems please send your profile and verification log to support

Enable encode checkboxes for corresponding parameters.

Most probably the problems appear because you have not parameterized the HTTP requests in your profile after recording it. Note that initially all requests are recorded as is. If you use a recorded profile without modifications, WAPT will simply repeat all the same requests with the same values of all parameters. However when working with dynamic site content, some parameters should have unique values for each session. The values of such parameters should be extracted from server response to the previous requests. You can read more about that using the following two links. http://www.loadtestingtool.com/help/working-with-session-variables.shtml http://www.loadtestingtool.com/help/parameter-value-dynamic-calculation.shtml (Note: The above links refer to WAPT Pro 2.0. If you use other version of the product, some GUI elements can be different, but the whole concept is the same. You can also find corresponding topics in the help file provided with your product.) Recently we also created a demo clip showing step by step how to perform the parameterization. You can download it here: http://www.loadtestingtool.com/quickstart/WAPTdemo.avi Also, I recommend you to use the "Verify test" button to check your profiles before running the test. It will execute each profile one time and log all the details. After the verification is finished you can expand the "Logs" folder in the left view. You will see all the requests and server responses logged during the profile execution. You can also use logs for test runs, but you need to choose the level of details on the “Log and Report Settings” page. Note also that when you record a profile, you should start from the very first URL that you use to access the web site. If you start recording from a page inside a user session, your profile will be incomplete and will not produce a valid session during the test.

Yes, you can just run load agents outside of your network.

Place all data into one CSV file and use it in $CSV function.

On average one Load Agent can emulate up to 2000 virtual users, so you need 3 Load Agents (one WAPT Pro license with two Load Agents and one additional Load Agent).

You cannot run multiple instances of WAPT Pro. A registered version can emulate 25 virtual users.

Could you send screenshots of IE proxy settings to support?

Check the WAPT log. You need to be sure that your profile works correctly before you will compare results of testing. Often times are different because some errors occurred during a test.