Jump to content
WAPT Forum

sergei

Administrators
  • Content Count

    718
  • Joined

  • Last visited

Everything posted by sergei

  1. You can disable the ASP prompt in Settings -> Prompts.
  2. You can enable full logging and check the times manually to ensure that all calculated correctly. Also check that you have received the same response as in Mozilla.
  3. Usually in this case you need to parameterize your virtual user profile properly.
  4. You can combine these requests into a task and set up how to measure a task time.
  5. You can find description of report data in the Help file: Next to the name of each request you can see how many times it was processed at the specified periods of time. If some column in the table is empty, it means that request wasn't executed during a period specified in column header.
  6. A solution will be specific for your site. Could you give me the link to your site?
  7. Usually it means that your server is overloaded.
  8. WAPT records webservice requests as usual HTTP requests. Could you give me the webservice URL?
  9. Yes, I can. What is your problem?
  10. You can use validation rules for the whole profile. Or if your ajax calls are identical that try to use the Loop operator instead of lots of requests.
  11. Could you provide access to your site? Could you give me your profile to check the issue?
  12. Typically, this means that your web server is overloaded.
  13. Please, try the WAPT Pro 3.0 and let me know the results.
  14. We will fix it in the next build.
  15. Is your site available? You can send your profile and logs to support. We take a look at them.
  16. Yes, WAPT can do that. Just record and execute your profile. Only completed requests are included in the statistics.
  17. I think you need to parameterize dynamic data in your profile. If you still have the issue, please send your profile and logs to support.
  18. You can create a variable in previous request and use it in the URL Path. Your URL Path will look like /restpath1/restpath2/$Var(some_var_name).
  19. You can found an example in our demo clip: http://www.loadtestingtool.com/quick-start-guide.shtml
  20. You can check the logs and find the requests with errors. Usually they were the requests of page elements.
  21. We have a demo clip. You can download it here: http://www.loadtestingtool.com/quick-start-guide.shtml
×
×
  • Create New...