sergei

Check the Authentication option of Profile Properties and enter credentials.

If request id is generated by server you need to extract it from response and then use it. You can use various WAPT operators for this.

Usually you need to parameterize only one profile to simulate 100 different users.

If you want to use WAPT variable from JavaScript you should use method: context.variable("var_name") - gets/sets the value of the "var_name" variable;

There is something wrong with your IP spoofing settings. How to setup IP spoofing you can know from our instruction http://www.loadtestingtool.com/help/how-setup-ip.shtml

It looks like a problem with your network. Do you use IP spoofing?

You can use one of WAPT functions or JavaScript operator.

In WAPT Pro you can use JavaScript operator for this.

It's Ok. Send me your profile and verification log. I'll try to understand your issue.

Could you give me your profile and verification log or send them to support?

Sorry, I'm wrong. You can convert request to subrequest (drag and drop), then convert to page element (right click menu) and then uncheck.

I think in your case the session ID is handled via cookies.

Could you give me the error message from WAPT?

You can convert to subrequests and uncheck them or delete.

Into the registration dialog click the button "Enter activation code".

Could you give me your profile or send it to support?

Usually it's a site-specific problem.

You can test a Web Service if you can interact with it over HTTP.

To avoid a ban from Google you can use many Load Agents with IP spoofing. You need to send requests from many as possible different IPs. Also you can add X-Forwarded-For header to default HTTP headers. To reduce a number of requests to Google you can exclude some requests from test.

Who actually does send request to Google: client's web browser or your server? Could you give me a link to your site or an example of profile?

The problem isn't related to the load testing. Real users will produce the same requests. It's a subject of your agreement with Google.

The WAPT internal browser doesn't support some IE interfaces e.g. autocomplete. So if you have faced to such error you need to use an external browser for recording.

You can enable full logging for your test and check all times manually.

It means that you need to parameterize your requests properly.

WAPT performs the next request only after the previous request was completely received. Usually if you get a response very quick it is an error. So check the WAPT logs for errors. Also in the logs you can see what exactly was received from server.