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

Bug #487666 reported by Björn Tillenius on 2009-11-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
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.

tags: added: windmill
tags: removed: story-windmill-layer
Gary Poster (gary) wrote :

Björn, is this still an issue?

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
status: Triaged → Incomplete

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
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  Edit
Everyone can see this information.

Other bug subscribers