sergei

Hi Jiri Yes, it is a correct behavior. When WAPT automatically parameterizes the value it changes the value to the variable in the static text.

It seems a little bit strange. I have double checked and for me it works good. Could you give me your scenario?

Hi Jiri, What counters do you use? Do you import the counters from an old scenario or create the new from scratch?

Hi, Yes, WAPT supports REST API testing.

Hi Pooja, No, you can't test an application communicating through the TCP protocol if this protocol is not subset of the HTTP(S) protocol.

We use JScript from Windows Scripting Host. You can find more here https://docs.microsoft.com/en-us/previous-versions/hbxc2t98(v=vs.85)

You need to enable server status reports in the Apache server. You can find out more information here https://httpd.apache.org/docs/2.4/mod/mod_status.html

In this case you can use the $JavaScript function instead of the JavaScript operator in the each page request you wish to check for errors.

For the complex validation rules you can use JavaScript and the log.error method.

Hi, With WAPT you can test web servers and client server applications which communicate by HTTP(S) protocol.

Please, send your profile and logs to support@loadtestingtool.com

Hi, 1. It is not possible. We doesn't gather such data. 2. Yes if it delays your next click.

No, it means that WAPT will try to reconnect and send request again.

We will consider it for on of the future versions.

Hi, During a test all load will come to a server from WAPT Load Agents and x64 Load Engines selected for a test load generation..

For a request Performance Degradation Factor is a ratio between average response time and baseline time. For a profile Performance Degradation Factor is a root-mean-square value of all requests' PDF. It allows you to quickly understand that there are requests which badly out of the average.

During recording, WAPT measures a time between two requests. Then it multiplies it on 0.5 and 1.5 and gets User Think Time values. During a test, WAPT calculates random value within these boundaries.

Hi In this case you can use $LOrder function with different values for different loop iterations.

According to your logs, you used only one connection per virtual user. You need to parameterize the profile correctly before you can make a reliable conclusion on the dependence between the number of connections and session faults.

Of course, the number of simultaneous connection significantly impacts on the test results. To understand a source of problem you need to check the logs. Also you can give me your logs or send them to support@loadtestingtool.com

If you enable a full logging then you can find a content of your downloaded file in corresponding response.

Thank you for the bug. We will fix it in the next build.

It isn't simple feature as it seams. We have such feature in our backlog and discuss it.

In your case WAPT didn't parameterize this dynamic value because it is not transferred in form hidden field. You need to parameterize such value manually.

Please, update your version, it's an already fixed bug.