eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Summary
eValid has several methods for handling user login processes. Even though eValid recordings are very reliable, login problems are fairly common. Here are some suggestions about how to overcome the most often encountered difficulties.

• Cookie(s) Already Exist.
  Do you have login which places a cookie? If so very often the login process will fail because, on eValid playback, the cookie is there and thus can't be created (re-created).
  • Solution: Edit in a DeleteCookies command or adjust the eValid cache to run without cookies (that is turn "Keep Cookies" off).

• Existing Login State.
  Are you already logged in? If you are, eValid may record your login activity correctly but may not apply it correctly during playback.
  • Solution: Make sure you are logged out before trying to log in.

• Input Field Focus.
  eValid needs to know which field from which to extract data, but if the field on the page is for some reason not in focus then eValid won't work correctly because it won't be able to record what you've typed. In many types of login pages the RETURN/ENTER key will not be recorded whereas a click will be.
  • Solution: Click in the field before typing in data. Doing this will assure that the field is in focus. After that the RETURN/ENTER key will work as expected.

• Secure Session IDs Wrong.
  An existing secure session may be in effect, and it may be using secure session IDs to control access.
  • Solution: Clear the prior session so you start in a "non logged in state". Or, insert SecureDataID commands in your eValid as appropriate.

• JavaScript Login Process.
  In some cases when JavaScript passages handle a login eValid may fail to record correctly if you do not have the correct object or element recording mode(s) set.
  • Solution: Make sure element mouseover recording is ON. You can toggle this state with ALT-F11. Make sure the overall selection of recording modes is correct. You may have to use absolute recording or Applet recording, depending on the method used in the login page implementation.

• Existing Windows From Prior Login.
  If there are existing windows during the login process, and the login uses a new window, you are likely to have problems because eValid, on playback, always begins by deleting all existing sub-windows.
  • Solution: Normally, eValid will warn you about existing initial windows, but if the windows are sub-sub windows this method may not work. Instead, start the login process earlier, so that the process creating the necessary initial windows is completely included.

• Login Via Application Window.
  In this case, a Windows application window is used to establish login information, which is then transmitted to the server.
  • Solution: Use Application Mode to record the sequences in the Application Window.

• Modal Dialog Login.
  Some sites use a modal dialog to collect login information. You know if a dialog is "modal" if you cannot do anything in the parent browser face as long as the modal dialog appears.
  • Solution: There are special modal dialog commands in eValid that are fed to the script for later automatic playback via the script window. Use eValid: Window > Script Window to display the script window, and then use the Insert > ModalDialog Commands option.

• Flash Object Handles Login.
  Flash objects are opaque so you need to use absolute recording to feed login data into a Flash object.
  • Solution: F11 toggles the eValid recording engine's abiltiy to record absolute clicks ON and OFF. Make sure it is toggled ON.

• Applet Object Handles Login .
  Applets are opaque to eValid but eValid has special applet-mode recording capability and a special set of commands intended solely to interact with an Applet.
  • Solution: Use applet mode recording. See eValid: Settings > Miscellaneous Recording > Applet Recording options.

Related Information
You may want to also see this page, which gives information on setting up your test's Initial Conditions correctly.