sergei

Yes, you can emulate any browser, just change User-Agent in Default HTTP headers.

See an attached example Example.wpp

Your POST contains "json_payload" parameter. I think, you need to parameterize it too.

You need to use JavaScript operator to generate POST parameters.

You can access to the DOM of the last response only if it contains HTML code.

You can create POST request with POST parameters type "Text" and use a variable in request body. Before POST request you should create JavaScript operator and initialize a value of the variable in JavaScript.

Please, attach the profile (file with .wpp extension).

Do you want to add a post parameter with a new name or modify a value of some old one?

Yes, you need to create variable, initialize it by $CSV function and then you can use $Var function in URL Path instead of static number.

You forgot to attach files.

If you have loaded 1000+ username-password pairs you will have 1000 different users at the end of the test. WAPT calculates a number of username-password pair for particular user as a rest of dividing usernumber on number of pairs.

No, you should have received the serial number by email. If you haven't received the serial number, please, write to support.

You cannot do exactly what you want with WAPT. But you can approximate a load with a help of a number of users and delays between requests. For example, you can run 1000 users and set 1 second delay between requests and you will have a 1000 requests per second if the server will respond quickly.

Could you describe your issue in more details? Example of your profile will be very helpful.

WAPT does not have any predefined limit on the number of virtual users that it can generate. For different tests this number is different and depends on several parameters including the hardware of your system, network capability, tested server itself and, most importantly, the behavior of each virtual user. The most important parameter is the delays between requests sent by each virtual user (this is also called "User think time" in the product). If you disable these delays, each user will send requests one by one very frequently. As a result you can easily achieve more than 100 hits per second even with 10 simultaneous virtual users. That is why it is very hard to tell about "average" number of virtual users that can be emulated. If the performance of WAPT is insufficient for your test, you can use WAPT Pro. This version of the product can use several systems (load agents) for load generation. By adding more agents you can get almost unlimited load. We usually say that we can generate about 1000 virtual users per agent. Actually this can be done with "average" delays between requests (10-20 seconds). If you disable all delays, you will only get about 200 users, even though they will make more hits than 1000 users with average delays. You will not be able to get more because of RAM limitation.

In your case the parameter Shift of $Seq function should be more than a number of sessions for one virtual user (use 100 or 1000 for example) and you will have an unique value.

Could you send your profile to support?

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

No, it's a correct behavior of WAPT. You need to properly parameterize your profile so that server treats each session as a new visitor. Then set in WAPT Start and completion settings/Execute to 1000 and you will have 1000 users visited your site.

We have fixed the issue. You can download the latest build from http://www.loadtestingtool.com/forum/builds/WAPT7.5.zip

You can add a delay at the end of profile, and each virtual user will wait others.

Unfortunately now WAPT can upload only file which predefined in request. So you can make few upload requests with different files and select them randomly or you can emulate upload request and prepare upload data with help of JavaScript operator.

Could you attach a screenshot with the error?

I've attached an example. json post 1.wpp

You can use a variable only in the following after initialization requests. If you want to use a variable in the first request you should create it in Initial variables of profile properties.