Testing RichFaces

[jwnorma]

Has anyone had any luck using automated frameworks to test RichFaces?

We are currently using Watij to test a web application using Facelets/MyFaces, but would like to upgrade to an AJAX enabled implementation. I know that RichFaces generates it's own ids for components, but is there anyway to give fields, inputs, etc uniquie identifiers?

I know that HtmlUnit, JWebUnit and a couple of other testing/automation framworks exist, that have similar functionality, but nothing seems to be able handle all of the js that Ajax pages require.

I am definatly interested in using RichFaces, but testablitity is a key concern.

Thanks

[sergeysmirnov]

I do not understand your statement about "RichFaces generates it's own ids for components". RichFaces does nothing over that the standard JSF does.

[sergeysmirnov]

We use Shale Test framework (with our extensions) and HtmlUnit on our side to test the developing components. However, it is more suitable for testing component rather than the web applications.

[jwnorma]

Thanks for the quick response!

I meant that RichFaces takes a tag like

<rich:inputText id="text1" value="#{bean.input}" />
and

creates html:

<input type="text" id="blah:j_id24:text1" ...}

is it possible to force the id like in MyFaces Tomahawk?

[sergeysmirnov]

richfaces has no rich:inputText component

[jwnorma]

I was using that merely as an example.

The question is the same, regardless of the component.

Can you force id's, or is there some other mechanism by which to uniquelty identify components once they are rendered.

[maksimkaszynski]

No, we don't force ids.
We follow JSF naming standards.

[maksimkaszynski]

Components could be easily located by their client ids.
<h:form id="f">
<a4j:commandButton id="b">

document.getElementById('f:b') will succeed