New answers tagged

0

You can specify your test desired duration via "Duration (seconds)" input of the Thread Group If you want to have "stable" load of 1000 concurrent users after the ramp-up time make sure to tick "Infinite" box next to "Loop Count" You can observe how many virtual users were online in this or that period of your test execution using Active Threads Over Time ...


3

Looking into How bots work article it is quite enough to send normal HTTP POST requests using JMeter's HTTP Request sampler in order to simulate real users talking to the bot: You should be even able to record the requests from your browser/application to the Bot Controller, you should be interested in the ones which have api/messages in their Path. The ...


0

This is not a Jmeter issue. As the error message implies "User already exist!". It's because you already registered the user and just re-running the recorded scripts. Basically, they have the same details. You need to modify the payload/request body when you run it again. Ask your developer on which values should be unique. Here's sample code on how to ...


1

Most probably your system simply doesn't allow multiple registrations using the same credentials set, looking into your request body "suspicious" parameters are: email phone licenseId Well-behaved load test should represent real life application usage as close as possible, it means that each JMeter thread (virtual user) must represent a real user. Two ...


0

If you want to keep this Extract token Post-Processor at the same level as other Samplers - you will need to remove the Debug Sampler and use i.e. Debug Post-Processor instead as given your current Test Plan: Extract token Post-Processor is being applied to Login sampler and (hopefully) gets the token Extract token Post-Processor is being applied to Debug ...


Top 50 recent answers are included