Closed
Description
This is currently on coredev 5.0 and 5.1 with the robot tests.
First failure:
Robot.Test Linkintegrity.Scenario: After you fix linked page no longer show warning
StaleElementReferenceException: Message: Element not found in the cache -
perhaps the page has changed since it was looked up
Stacktrace:
at fxdriver.cache.getElementAt (resource://fxdriver/modules/web-element-cache.js:9454)
at Utils.getElementAt (file:///tmp/tmpdwTdAw/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command-processor.js:9039)
at WebElement.getElementTagName (file:///tmp/tmpdwTdAw/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command-processor.js:12141)
at DelayedCommand.prototype.executeInternal_/h (file:///tmp/tmpdwTdAw/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command-processor.js:12661)
at fxdriver.Timer.prototype.setTimeout/<.notify (file:///tmp/tmpdwTdAw/webdriver-py-profilecopy/extensions/fxdriver@googlecode.com/components/command-processor.js:625)
Second failure:
Robot.Test Querystring.Scenario: Location query
Element locator 'css=.pattern-relateditems-result-select' did not match any elements after 30 seconds
See:
- http://jenkins.plone.org/job/plone-5.0-python-2.7-robot/4756/robot/
- http://jenkins.plone.org/job/plone-5.1-python-2.7-robot/561/robot/
These pull requests together passed the tests on 5.1, so they should have helped, but apparently not enough:
- Do not use run_on_failure from Selenium2Library. plone.app.robotframework#57
- Use
Plone Test Teardown
from p.a.robotframework master [5.1] #1655
More info, explaining those changes, is in this otherwise no longer relevant pull request: #1652
Relevant recent change on Jenkins: Firefox was updated from 34 to 46, with hopes of fixing this or similar failures.
Locally on my Mac the tests pass for me. Well, not always... This should get you the same environment as Jenkins:
- Install https://ftp.mozilla.org/pub/firefox/releases/46.0.1/
ROBOT_SELENIUM_RUN_ON_FAILURE=Debug bin/test --all -s Products.CMFPlone -m test_robot -t test_linkintegrity -t test_querystring
The Debug
is very relevant, because then you will notice when it fails: otherwise the test runner might just continue and report no failures.
Currently it fails locally for me after all with:
ValueError: Element locator 'jquery=:focus' did not match any elements.
Activity