Hi all,

maybe someone had the same problem before. I already found out, that one can do automated testing by using the unique-id-extender, connect it to anchor-components. This is true for test-applications which use a request/response record/replay mechanism (as does Visual Studio or WebPerformance).

Now some of our quality-assurance guys switched my attention to tools, that use a more interactive approach by parsing the DOM for elements (based on xpath or alike) and then performing methods on these elements (there are Seapine QA Wizard and Ranorex Studio for instance). We are actually using RANOREX.

Well, the problem is, that the unique-ids are not being transported right through to the DOM, so these tools do not have reliable anchors to retrieve elements, while the unique-ids would be a perfectly satisfying way.

@gizmox: Are there any plans, or would you mind thinking about, to bring the unique-ids to the DOM as well?
 

@users: Does anyone have the same problem and a solution to it?

Thank you anyway in advance,

Kristof

Hi Ori,

thanks for the reply. I'm not quite sure whether this is a bug or rather a feature-request ;-)
 

The following scenario:
I added a form to an application and added a unique-id extender to that form. I then set the "Unique ID on..."-property of some textboxes to values as "txtUsername", "txtPass" and alike.

When I look at the xml that gets transferred between the client and the server, I actually CAN see the CUID-attributes on the respective nodes, which contain the IDs that I have set up before.
My problem is now, that these unique-IDs are not used in the DOM. The elements have the id that gets generated by VWG ("TRG_7" and alike) but do NOT contain any attribute, that contains the unique-id.
This happens to complicate automated testing with tools like RANOREX Studio or QA-Wizard, as these tools do not capture the request/response pairs (as visual studio does), but the locate the elements to be tested by querying the DOM (for instance by applying xpath-expressions).

It would be fine, if VWG could put the unique-id into the "name" attribute or a custom attribute like "vwguniqueid". This way, our testers can easily locate the controls by the unique-id and doing automated acceptance-tests would be a pleasure.

Did you get my point?

Best regards,

Kristof

Hi Ori,

yes, I do not see the IDs in the HTML-Elements when investigating through DebugBar or FireBug. I'm using 6.4 P4. Is Beta1 available somewhere? I will have a look at the lik you provided and let you know about the result ASAP.

Regards,

Kristof