Oh well Selenium is one thing i tried to avoid for the half simple
cases. I know selenium will be a must for the complicated stuff anyway.
Anyway I will extend my browser mocks up to the level I need for
doing basic dom manipulation (getElementsById, etc....)
That should be sufficient enough to cover the simpler APIs...
Not that I really like to base tests on untested mockup APIs :-),
but it still is better than having nothing.
Btw. the testframework itself is already integrated into the JSF 2 core
I am still ironing the infrastructure out so... the usual take
everything with a grain of salt :-)
Werner
Matthias Wessendorf schrieb:
On Thu, Dec 4, 2008 at 11:23 PM, Werner Punz <[EMAIL PROTECTED]> wrote:
Hello everyone
today I started to work on the ajax parts of jsf2
for now I am still up to the tasks of setting up the entire
infrastructure.
So far I have found a decent unit test environment which integrates
into maven (Berlios JsUnit) which gives about the same functionality as
junit.
cool. I want something similar for Trinidad as well
(at least for those bits that are easy to test and don't need
(too much) mocks)
we do (internally) something with selenium, where we fire up browsers
in an automated test scenario.
Werner
