Concerning setFormParameter, it is now deprecated, since it is to much related with HttpUnit. No need to implement it, just throw UnsupportedOperationException("setFormParameter");
The right way is to use more specific methods : setTextField, select**, check**, ... This make test cases more understandable (does this word exist ???)
----- Message d'origine ----
De : Jon Frisby <[EMAIL PROTECTED]>
À : [EMAIL PROTECTED]; [EMAIL PROTECTED]
Envoyé le : Mercredi, 7 Juin 2006, 2h20mn 23s
Objet : Another Selenium fix...
Can you tell me what the expected behavior of setFormParameter is?
For the moment I have it delegate to setTextField, but I suspect that
that's wrong behavior (thus it's not included in my patch)...
-JF
The right way is to use more specific methods : setTextField, select**, check**, ... This make test cases more understandable (does this word exist ???)
----- Message d'origine ----
De : Jon Frisby <[EMAIL PROTECTED]>
À : [EMAIL PROTECTED]; [EMAIL PROTECTED]
Envoyé le : Mercredi, 7 Juin 2006, 2h20mn 23s
Objet : Another Selenium fix...
This patch compensates for the fact that the Selenium client library
doesn't actually wait for the page to finish loading when you do an
open() or click(). This was resulting in me having to add
Thread.sleep(some_way_too_large_number) in my tests for things to work.
doesn't actually wait for the page to finish loading when you do an
open() or click(). This was resulting in me having to add
Thread.sleep(some_way_too_large_number) in my tests for things to work.
Can you tell me what the expected behavior of setFormParameter is?
For the moment I have it delegate to setTextField, but I suspect that
that's wrong behavior (thus it's not included in my patch)...
-JF
_______________________________________________ Jwebunit-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
