Testing with Selenium

answered 2006-12-08 09:13:22 +0800

admin
18691 ● 1 ● 10 ● 130

Orignial message at:
https://sourceforge.net/forum/message.php?msg_id=4049796

By: henrichen

1. I tried the Selenium IDE with a simple ZK page. It seems when Selenium fill out textbox, it does not fire corresponding onblur, onfocus, etc. Those are important triggering point for the ZK Ajax framework. Unless those event is properly simulated, I don't think it is compatible with ZK.

2. Those id is uuid so they are different from the zul soruce. And yes, the uuid can change if some source is changed. This is the second issue.

3. ZK may provide some kind of "recording" mechanism and at least allow playback in the component's id level.

/henri

answered 2006-12-08 17:36:35 +0800

admin
18691 ● 1 ● 10 ● 130

Orignial message at:
https://sourceforge.net/forum/message.php?msg_id=4050454

By: manuel_moreno

Hi henri,

I have investigated a little further,

I think that the second issue is the most important, because if it is not resolved somehow, it will be difficult to integrate ZK with any automated web testing tool, since if your source changes the uuid could change and you could get false faliures of your already developed tests. It would be an extra effort to distinguis between real faliures and false ones, and also more effort to fix the broken tests.

I've got some ideas, Possibly they don't fit into the ZK architecture, but maybe it is of some help so here they go:

Idea 1.- Add an optional tag to the components, call it uuid, or custom-uuid, which would be unique in the desktop. ZK in the rendering phase could add a prefix to the custom-uuids, so that they don't conflict with the ones that ZK generates.
This solution adds a extra effort to the developers who want to use automated web testing, because they must use id and custom-uuid. The developers would have to keep track of the custom-uuids they use so that they don't repeat them.

Idea 2.- Define a deterministic uuid generation rule for the components that have an id set on the zul code. This generation rule should be based on the fact that ids are unique in the namespace. The generated uuid, should be something similar to an access path to the components.
This idea is better in the sense that is lower effort for developers, they don't need to do anything else, but maybe the length of the generated uuid is very long, I don't know if that matters very much.
Maybe the extra effort for the developers is to set the id for macrocomponents, as they generate their own namespace... and what we need is to get an invariant uuid



For the first issue (Selenium not firing the events correctly) I think it is because Selenium is only generating the events it needs to fill the components with the values, but Selenium team didn't think that for filling the forms, they also had to fire the onFocus events and so...
I don't know why ZK needs this events triggered to simply fill a component with a value... are there important things happening behind the scene with that events?

Thanks,
Manuel.

answered 2006-12-11 01:46:59 +0800

admin
18691 ● 1 ● 10 ● 130

Orignial message at:
https://sourceforge.net/forum/message.php?msg_id=4052766

By: henrichen

For the event issue, the textbox component count on the Javascript event to fire the ZK onChange event and sends entered value to the Java component of the textbox in server side.

The uuid issue. I agree with you that it is the tough one. Unless we can record and identify the concerned component some way, or any such pure browser side testing tool is not possibly working with ZK.

/henri

answered 2007-02-21 15:09:23 +0800

admin
18691 ● 1 ● 10 ● 130

Orignial message at:
https://sourceforge.net/forum/message.php?msg_id=4169902

By: jwyseu

It is possible for selenium to fire events of a component. So you can add a fireEvent "id of component" change/focus/blur to the script to simulate the events. I got it working for a textbox in this fashion. The script will get complicated very fast though and you have to know which events to call and in what order.

For a textbox, the following worked:
<tr>
<td>fireEvent</td>
<td>_pc7</td>
<td>focus</td>
</tr>
<tr>
<td>type</td>
<td>_pc7</td>
<td>textToInsert</td>
</tr>
<tr>
<td>fireEvent</td>
<td>_pc7</td>
<td>blur</td>
</tr>

I was trying something like that for a listbox (used as a grid) but did not find the right event to trigger the select.

We still have the problem of the changing ids ...