Jump to content
WAPT Forum

sergei

Administrators
  • Content Count

    683
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sergei

  • Rank
    Advanced Member

Recent Profile Visitors

23433 profile views
  1. Hi, With WAPT you can test web servers and client server applications which communicate by HTTP(S) protocol.
  2. Please, send your profile and logs to support@loadtestingtool.com
  3. Hi, 1. It is not possible. We doesn't gather such data. 2. Yes if it delays your next click.
  4. No, it means that WAPT will try to reconnect and send request again.
  5. We will consider it for on of the future versions.
  6. 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..
  7. 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.
  8. 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.
  9. Hi In this case you can use $LOrder function with different values for different loop iterations.
  10. 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.
  11. 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
  12. If you enable a full logging then you can find a content of your downloaded file in corresponding response.
  13. sergei

    Parameters in reports

    Thank you for the bug. We will fix it in the next build.
  14. It isn't simple feature as it seams. We have such feature in our backlog and discuss it.
  15. 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.
×
×
  • Create New...