Get help with testing, discuss unit testing strategies etc.


Post by gpeng »

Below is a recorded event sequence by Siesta, on a web app based on Ext JS 3.4.1

(1) { click: "#fakeusername", offset: [10, 10] },
(2) { action: "type", text: "admin" },
(3) { click: "#password", offset: [73, 19] },
(4) { action: "type", text: "admin" },
(5) { click: "#LoginForm .x-btn-text", offset: [19, 6] },
(6) { click: "#ux-startbutton .icon-cog", offset: [42, 6] },
(7) { click: "#options-1169 .icon-cog", offset: [45, 12] },
(8) { click: "#refresh-1171 .x-menu-item-text", offset: [20, 7] },

On step (7) and step (8), dynamic IDs are detected by Siesta. We know those are dynamic IDs and the rules how the app generate them - with a prefix (options or refresh in the above) and a static counter which increases each control is generated. as those control created and destroyed, the counter keep increasing.

My question is if it is possible to have some function to identify the ID by those limited pieces of information such as prefix and the counter number and etc.?

Post by mats »

Hmm, Siesta should ignore any auto generated id's as they won't be stable. Can you create a simple test case for us that we can inspect?

Post Reply