22 May 2013 18:18
Re: Tagging RF tests
Am 22.05.2013 18:09, schrieb Gil Forcada Codinachs: > Sorry to get you back so late! > > Thanks for the pointers and ideas, still I was thinking in something > different: > > My wish is to be able to run all tests always, but at the same time be > able to tag some RF tests in a way it's ok if they fail (so that jenkins > still considers that the build is fine). > > The underlying problem is that tests do run fine in our development > laptops but for some reason (and not much time to investigate) on the > jenkins server they do fail. Do they always fail on Jenkins or just randomly? Our coredev robot tests used to fail on Jenkins every now and then because sometimes the selenium tests try to access a component that has not been fully loaded yet. You have to make sure the tests wait until the page has been fully loaded (with "Wait until page contains" and "Wait until keyword succeeds") before typing in data or testing for content. See for instance https://github.com/plone/Products.CMFPlone/blob/4.3.x/Products/CMFPlone/tests/robot/test_overlays.robot for examples. Timo ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service(Continue reading)
RSS Feed