Launchpad itself

Asserting that a node exist in Windmill test, directly after waiting for it, sometimes fails

Bug #487666 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Low
Deryck Hodge

Bug Description

If you have code such as ...

        client.waits.forElement(xpath=ADD_COMMENT_BUTTON)
        client.asserts.assertNode (xpath=ADD_COMMENT_BUTTON)

... the assertNode() call sometimes claims that the node doesn't exist. It might be that waiting for a node checks that the node is there in a different way than assertNode() does, and that forElement() gets to know that the node is there, before the DOM is actually modified to contain the node. But that's just a guess, I haven't looked at the actual code yet.

Björn Tillenius (bjornt)
tags: added: windmill
tags: removed: story-windmill-layer
Revision history for this message
Gary Poster (gary) wrote :

Björn, is this still an issue?

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
status: Triaged → Incomplete
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 487666] Re: Asserting that a node exist in Windmill test, directly after waiting for it, sometimes fails

On Tue, Mar 16, 2010 at 01:53:50AM -0000, Gary Poster wrote:
> Björn, is this still an issue?

Yes, should be. We worked around the issue by rewriting the tests that
were failing, but I don't think the underlying issue has been fixed.

    status triaged

Changed in launchpad-foundations:
status: Incomplete → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

Windmill is dead.

Changed in launchpad:
assignee: nobody → Deryck Hodge (deryck)
status: Triaged → Won't Fix
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.