Get help with testing, discuss unit testing strategies etc.


Post by gpeng »

We have a web app which use ExtJS 3.4.1. Loading our app into Siesta seems working fine. A sequence of event was below
(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] },

which basically is,
a. Load main logon screen, a blank screen with 3 controls only (user, pass, and logon button)
b. Type in user/pass and logon (step 1 to 5)
c. The main operation screen appears and more sequences of clicking operations… ( step 6 and more)

Above sequence works up to (5), after (5) Seista does not do anything. I am suspecting that the newly loaded UI is not in the Siesta domain(?), is there something to do to make this work?

Post by mats »

"Newly loaded UI" means navigating to a new HTML page? Then you need this setting (only available in the Standard version).

https://www.bryntum.com/docs/siesta/#!/a ... ateContext

Post Reply