Hi,
IMHO the API should only contain "portable" methods. In case user wants to do
something that is not portable, he has to accept to tie his code to a specific
testing engine (and cast ITestingEngine).
For example we can add specific methods to HtmlUnitTestingEngine and suggest
the user to do something like:
((HtmlUnitTestingEngine) getTestingEngine()).setUseResynchronizingAjax(true);
Regards,
Julien
>
>De : Jevon Wright <[email protected]>
>À : JWebUnit Development mail list <[email protected]>
>Envoyé le : Mer 10 Mars 2010, 7 h 52 min 01 s
>Objet : [JWebUnit-development] Using NicelyResynchronizingAjaxController
>
>Hi,
>
>It took me some time but (after committing r827 in SVN) I found how to use
>NicelyResynchronizingAjaxController for HtmlUnit-based tests with JWebUnit:
>
>https://sourceforge.net/tracker/?func=detail&aid=2697234&group_id=61302&atid=497985
>
>A question is, should this be provided as a public API method to simplify
>things? I imagine this is quite a common use case - however, (AFAIK) Selenium
>would not support this. Should we create an API method
>"setUseResynchronizingAjax(boolean)" for the WebTestCase, but make this method
>throw an UnsupportedOperationException in the Selenium implementation?
>
>Jevon
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
