[JIRA] [acceptance-test-harness] (JENKINS-33730) ATH needs to be made to work with 2.0

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title

Tom FENNELLY commented on JENKINS-33730   Re: ATH needs to be made to work with 2.0 Oliver Gondža Hey Oliver. I pushed the small few changes I have made to ... https://github.com/jenkinsci/jenkins/pull/2196 (don't worry Daniel Beck ... we're not going to merge it ) https://github.com/jenkinsci/acceptance-test-harness/pull/87 Oliver Gondža I'm really stuck on an issue with the selection of the "Execute shell" option from the "Add build step" dropdown. I'm seeing an issue with it on WarningsPluginTest.should_detect_warnings_of_multiple_compilers_in_console_freestyle, where it's unable to find .//A[@href][@id='Execute shell' or normalize-space(.)='Execute shell' or @title='Execute shell' or .//img[@alt='Execute shell']]. When I run it in my IDE, setting a breakpoint where the findElement fails, I'm able to go into the dev console in the browser and execute... $x(".//A[@href][@id='Execute shell' or normalize-space(.)='Execute shell' or @title='Execute shell' or .//img[@alt='Execute shell']]") Sure enough, when I execute this, it returns an empy array. But ... when I manually click on the "Add build step" dropdown I can actually see the "Execute shell" option + when I then execute the above xpath it actually works i.e. it finds it. See maybe it's some sort of timing issue? Still not sure how the config page changes have caused this. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.