History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WET-209
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Venugopal S Shenoy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
WET

Launching the application through the ie.goto function skips the Login page, for the subsequent runs...

Created: 02/Sep/06 03:04 PM   Updated: 18/Jun/07 10:25 AM
Component/s: Native watir object model
Affects Version/s: 0.8.0, 1.0.0, 0.9.8_beta1, 0.9.8 Final
Fix Version/s: 1.4

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
Login to any application, which has a login page. (say "http://mail.yahoo.com"). Keep the session active, i.e., DO NOT log out.

Run the following script.
require 'WET'
include WET
ie = Browser.new()
ie.goto "http://mail.yahoo.com"

The second IE session that opens up, directly goes inside, skipping the login page.

Right now, the only way to again make the ie.goto "<URL>" to go through the login page, is by running the script with no IE sessions Open.

The present defect also prevents running of two sessions of the same URL. {Especially this is needed when we need to have two sessions open with different logins}


Note:
      (a) As far as I remember, till a month back, this was working FINE. Hence the bug can be classified as a regression bug.
      (b) This issue is NOT reproducible manually. i.e., even if one session is active, if the second session is launched with the same URL, the login page is shown.

 All   Comments   Work Log   Change History      Sort Order:
Raghu Venkataramana - 08/Sep/06 11:27 PM
This smells like an 'ie update' issue or something that automatically got changed about IE - or worse even - an unrelated windows update that has caused this change to happen. In any case, it is rather we wait for a couple of such automatic IE / Windows updates. It might happen (and historically, it has happened) that the problem gets automatically solved after a little while. After some time, if we find the issue is still there, then we can investigate into this.

Raghu Venkataramana - 10/Sep/06 04:15 AM
Degrading to Major - Two IE sessions from the same machine to the same host is never a great idea - I am quite confident that one would run into other issues (like cookie / session id caching).

Raghu Venkataramana - 02/Oct/06 04:17 AM
There are two points to be noted here:
a) Probably something about IE itself has changed.

b) This is not a typical usage scenario. In most cases, a tester would first log out as the currently logged in user and then log in as the new user.

Considering both these issues, I think it is safe to mark this as 'fix after 1.0'