> Common Questions Asked in getting a loadtest to run

  During loadtest, user often encounter problems getting the loadtest
  to perform properly. Oftentimes there are questions being asked on
  how to run loadtests especially when there are instances that will
  require the user to make minor modifications in order to permit the
  loadtest script to run properly.

  Here are the most common problems we hear from people who are using
  eValid to impose server load using the LoadTest feature. Our answers
  immediately follows the question.-

  (1) Q: Server restricts two simultaneous login's from the same
         user name / password.

      A: You can change the name / value pairs as specified when
         creating a loadtest. This allows the user to have multiple
         instances of eValid running while performing a login using
         different name / value combinations.

  (2) Q: The login works fine the first time but fails the second time

      A: Having the cookies left behind from a previous playback can
         sometimes dramatically increase the chances of the second
         playback to fail. There is a special command in eValid to
         manage the cache effectively to avoid failures during playback.
         By selecting the "Never Use Cahe" option in the cache manager,
         eValid automatically removes all the cache including the cookies
         as soon as playback is started.

  (3) Q: On playback, the loadtest is affected by modal dialogs

      A: When performing a loadtest, it is essential that the windows
         are not interrupted or halted in any way. Having modal dialogs
         that pop-up during playback can adversely affect the outcome
         of the loadtest being ran. By using the -S switch when running
         the loadtest in batch mode, this ensure that any type of modal
         dialog that may pop-up during playback is suppressed to ensure
         the smooth and trouble-free operation of the loadtest.