sergei

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. If you still cannot find the reason of the problem, please send your profile (.wpp file) and log file with the test verification data to support. To save logs right click on the Logs folder and choose "Save Logs" from the menu.

This should work. Could you send your profile to support?

No, Silverlight module is enough.

We are working on it. It will be available in future versions. If you want to exclude some tables from report, you can edit XSL templates from ReportTemplates folder. It's undocumented hack.

WAPT can recognize JSON requests if JSON module is installed. You can use variables into JSON requests.

Usually it means that you need to parameterize your profile.

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. If you cannot find a problem in WAPT logs, send them and profiles to support. We will try to help you.

You need to enable proxy for a load agent. Open "Load Agent Settings" dialog (Distributed Test Run -> Load Agents -> Edit...) and check "Use proxy server while performing the test" option.

I can't reproduce your problem. Please update your WAPT and let me know if the problem still exists.

It's all amount of data that was sent/received during test for the corresponding profile. Yes, session is one execution of profile from begin to end. Failed session is session where one of requests was executed with error.

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. If you still cannot find the reason of the problem, please send to support your profile (.wpp file) and log file with the test verification data to me. To save logs right click on the Logs folder and choose "Save Logs" from the menu.

If a link to a product thumb is dynamic you need to convert such page element to sub-request and make its link dynamic.

Then you need $Hidden(__RequestVerificationToken,0).

WAPT records and repeats requests.

$Hidden function searches value in input field (e.g. ) by name (e.g. UserSession) and returns its value (e.g. 75893.0884568651DQADHfApHDHfcDtccpfAttcf)

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.

Sub-requests are needed for a proper Referer management. All sub-requests have a main request as Referer. If you convert page element to sub-request it will have own separate statistics in report.

You should uninstall WAPT from the old machine, install it to the new machine and register WAPT as usual.

WAPT can record HTTP traffic only. So if Java uses own native sockets that the answer is no.

Yes, you can setup different users on Profile properties page. Check Authentication checkbox and enter usernames and passwords.

We released WAPT Pro 2.5 which can use other browsers (Firefox, Chrome, External IE) for recording. You can download it from http://www.loadtestingtool.com/forum/builds/WAPTPro2.5.zip New version of regular WAPT will be released soonest. Now you can download beta of WAPT 7.5 from http://www.loadtestingtool.com/forum/builds/WAPT7.5.zip

It is a normal behavior for NTLM authentication recording. Just enter credentials and continue recording.

What is your hardware specification and how many virtual users did you run?

Ok, we will think.

Use an unique file name for each virtual user (for example, use $UserID for file name) and merge files after test completion.