Jubula supports AUT's written with the HTML GUI toolkit according to the following points:
- We strongly recommend writing HTML AUT's so that they are conform to the W3C standard. You can check whether your AUT is W3C conform using an online validator: http://validator.w3.org
- Some of the Jubula actions in the concrete toolkit (i.e. which are theoretically valid for all AUT types) may not (yet) be supported. In some cases, this is because the component doesn't exist as such in HTML AUT's (menu bars for example). In other cases, text components such as tables or lists do not have a concept for dealing with selection as they do in e.g. Swing.
- The autrun option to start AUT's 3.7.2.6 cannot be used for HTML AUT's .
- There is a minor difference in the way that clicks are performed in HTML compared to other supported toolkits. In other toolkits such as Swing, an API is used to simulate actions at the OS level so that the the computer itself can't distinguish whether it came from a tool or a keyboard. A normal click by a user in a browser would go via the mouse through various layers to the webserver, resulting in a request to that webserver. The clicks in the HTML toolkit are performed by firing DOM events using Javascript therefore bypassing the mouse level. So, although the computer can tell the difference, the webserver can't.
- HTML AUT's can be tested in single-window or multi-window mode. If your AUT has functions that cause new windows to open, then you should specify this in the AUT configuration. You can then map components from different windows, and also use specific actions to switch windows during your test. Multi-window mode on Internet Explorer is considerably slower than on Firefox - this is a known issue registered at Selenium.
Copyright BREDEX GmbH 2013. Made available under the Eclipse Public License v1.0.