Re: Plone coredev robot tests broken.

Timo Stollenwerk wrote:
> I already upgraded our Jenkins nodes to the latest Firefox (32.0) and
> our coredev jobs to use the latest Selenium version (2.43.0). This fixed
> some robot tests but not all.

Ouch. We (internally) didn't haven't seen any tests broken after the
versions have been updated, so very unfortunate :( And even this happens
only a few times in a year, it's still a lot.

There's a theoretical option of changing to phantomjs, but its webdriver
support has problems of its own (e.g. last time I tried, it could not
see opened dropdown menus).
> It is also really annoying that all warnings are included in the robot
> reports, e.g.:
>
> http://jenkins.plone.org/job/plone-5.0-python-2.7/3258/robot/report/robot_log.html#s1-s1
>
> It would be great if somebody could have a look how to get rid of those.
>
> @Asko: Any idea how to disable those warnings?

Robot Framework docs says there is a setting for the log level. I'll
make a new release for robotsuite, which sets the level from an
environment variable. (It could also be set implicitly as a part of Open
test browser keyword in p.a.robotframework, but the first options feels
more generic.) I'll ping @Timo, once this is available.

Regards,
Asko

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk