CiviCRM Community Forums (archive)

I was experimenting a little with Selenium in order to speed up a test of a donation page, and found something really odd.

The page contains a custom profile with a number of Yes/No type questions.  When I recorded filling in the form in Selenium and replayed the page, the script died as soon as it got to the radio buttons.  The reason surprised me.

Using the Selenium "HTML" format for its tests, a click on one of the radio buttons looks like this:
<tr>
<td>click</td>
<td>qf_732258</td>
<td></td>
</tr>
That funny looking string, "qf_732258",  was the ID of the first radio button (a "Yes" answer).    Playback in Selenium failed because, well, every time you generate the page, the ID of the buttons changes to something completely random.

This makes it really hard to do anything not only in Selenium but also in JavaScript, since both systems want to know the DOM ID of the object you're manipulating.

Since the ID start with "qf_", I'm guessing this is QuickForm funniness.    Which likely means it would be hard to change this behavior.  But is there anything we can do so that the ID of these objects stays the same, so that it's even possible to use Selenium or jQuery on CiviCRM radio buttons?

Yeah, I figured it was at this level.

It appears that in general, you can pass in the ID with the $attributes array.  How that would work with groups of radio buttons I don't know, although I'd guess you folks directly call addElement for each individual button, so it's at least possible.

Not a critical problem, obviously, but it did look a little wonky.