Hi Marc,
Marc Guillemot schrieb:
the 2 patches make sense to me. Can you open an issue in WebTest and a
separate issue by HtmlUnit for that (tests are naturally appreciated)?
I added an issue:
http://webtest-community.canoo.com/jira/browse/WT-432
I'll try to provide a test case too.
I also submitted the HtmlUnit patch:
http://sourceforge.net/tracker/index.php?func=detail&aid=1950342&group_id=47038&atid=448266
Unfortunately the HtmlUnit tests don't run in my sandbox (I had to skip
them when building the package), but maybe I'll find out how to run a
single test so that I can provide a test case for the bug.
Btw, do you already use WebTest/HtmlUnit for the functional tests in
Cocoon or Lenya?
In Lenya we're using WebTest, but unfortunately the coverage is by far
not sufficient. It seems promising to keep the "HTTP API" as simple as
possible (e.g. REST / APP) so that we can use fundamental, reusable test
snippets which are easy to understand (e.g., checking for HTTP status
codes instead of complex XPaths). This is what we try at the moment when
integrating the new WYSIWYG editor (firedocs).
Among the tools I tried until now Canoo WebTest is the easiest to use,
and a low entry barrier is quite important for me when it comes to
writing tests :)
I don't know to which extent Cocoon uses web tests. They have a
test/htmlunit directory containing about 20 classes, but I'm not sure if
there are more tests in the blocks (modules).
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
