sergei

Could you give us a link to your site so we can check the recorder?

You should parameterize your profile. We have sent you an example of properly parameterized profile.

It isn't possibly now. We will add this in one of next builds.

It isn't possibly automatically. But you can use JavaScript operator and manually parse a page.

Unfortunately, it is not possibly.

You can use Random operator or JavaScript to emulate this feature.

You can use JavaScript to set variables for different profiles.

We have updated the information on our registration server, so you can register now. To comply with the license agreement, please make sure that all previous installations of the product are removed.

Do you receive this response during recording or a test run?

Yes, it does. We 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

Could you provide a link to your site? You can send it to support@loadtestingtool.com.

In this case you can use Java Script operator, but it is available in WAPT Pro only.

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/workin...variables.shtml http://www.loadtestingtool.com/help/parame...lculation.shtml 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.

Could you describe the problem in more details or give me an example profile?

There are no bugs. Each user sends a request or receives a response very quickly. Therefore per user bandwidth usage is high. But an overall WAPT bandwidth usage is low because you set a long user think time. Your virtual users perform quick actions and then wait a long time.

Please, send your results (a file with .wpr extension) to support@loadtestingtool.com.

What doesn't work for you? IP or server name usage?

Could you send your profile and full log to support@loadtestingtool.com?

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/workin...variables.shtml http://www.loadtestingtool.com/help/parame...lculation.shtml 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.

You should use IP of the server.

Could you give me a link to the site? Also you can try the latest build from http://www.loadtestingtool.com/forum/builds/WAPT7.0.zip

Please, download the latest build from http://www.loadtestingtool.com/forum/builds/WAPTPro2.0.zip. If the crash still exists, give me your profile, please.

I think during this time no page was finished. WAPT shows statistics only after page request with all page elements were completed.

In the field "Server" on a request properties tab enter an IP address instead of a server name.

Please, download the latest build from http://www.loadtestingtool.com/forum/builds/WAPT7.0.zip. If the crash still exists, give me your profile, please.