TestPlan

test_http_window / fails sometimes with selenium

Bug #537950 reported by edA-qa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TestPlan
Fix Committed
Low
Unassigned

Bug Description

This has happened a few times while running test-selenium. It always works in HTMLUnit and usually work with selenium.

00000161-01 CHECKPOINT-FAIL testplan.auto.unit.func.Check:Predicate-NoMatch:
        Error: no match found
        Predicate: xpath://p[@id='other']
        Function: getLocator
AutoStack: in {Unknown} in selenium at step 116
        Inside call to unit.func.Check
        /opt/testplan-main/dist/tests/samples/testplan_test/test_http_window.test:19: Check //p[@id='other']
        Inside call to unit.func.ChildExec
        /opt/testplan-main/dist/tests/samples/testplan_test/All.test:35: exec test_http_window

Related branches

lp://staging/testplan
Revision history for this message
edA-qa (eda-qa) wrote :

I'm able to reproduce this error virtually at will. All it takes is to run this test twice in parallel (with spawns). This extra test is now test_multi_window and I'll work on fixing it.

Curious, the error goes away if I simply put a "Sleep 1s" before the SetCurrentWindow in test_window.test (that is, before the one that requires the new window to be open). This may thus be some timing issue we haven't seen. Perhaps selenium isn't waiting, or reporting success when the window isn't yet open.

Revision history for this message
edA-qa (eda-qa) wrote :

I've put in a delay before forcing open the new window.

Note that unless the below issue is ever resolved in Selenium there is little we can do. Their test suite/use cases must be not include much for windows if that isn't supported (our test case is extremely basic)
http://jira.openqa.org/browse/SEL-628

Changed in testplan:
status: Confirmed → Fix Committed
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.