Launchpad itself

LaunchpadUser.ensure_login() fails if the current page is a +login page

Bug #461759 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Björn Tillenius
Launchpad itself 3.1.10

Bug Description

If you call LaunchpadUser.ensure_login() in a Windmill test, it will fail if the browser already is on the +login page. The code will assume that the user is logged in, and will try to press the "logout" button, which doesn't exist.

Related branches

lp://qastaging/~bjornt/launchpad/windmill-problems
Deryck Hodge (community): Approve (code)
Diff: 164 lines
4 files modified
lib/canonical/launchpad/windmill/testing/constants.py (+2/-2)
lib/canonical/launchpad/windmill/testing/lpuser.py (+28/-19)
lib/canonical/testing/layers.py (+8/-0)
lib/lp/bugs/windmill/tests/test_bug_tags_entry.py (+10/-9)
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit

Fixed in devel r9787 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/9787>

Changed in launchpad-foundations:
status: In Progress → Fix Committed
Diogo Matsubara (matsubara)
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.