Shane Landrum - 22/Jun/06 09:41 AM Although, now that I think about it, this might also be a documentation bug. From http://openqa.org/selenium-rc/perl.html : "Test::WWW::Selenium does not require explicit start/stop commands (since these will be handled during test cleanup), and allows you to quickly make any Selenium method a test simply by adding the suffix "_ok" to any Selenium method. Hence, instead of using $sel->click you can use $sel->click_ok to make it a test. In addition, for each Selenium getter (get_title, ...) there are six autogenerated methods (<getter>_is, <getter>_isnt, <getter>_like, <getter>_unlike, <getter>_contains, <getter>_lacks) to check the value of the attribute)." If you're binding the assert/verify/waitfor commands differently than this, it should be communicated clearly.

Dan Fabulich - 15/Oct/06 11:44 PM The reference.html docs are only true of HTML Selenese; the Perl driver has its own Perldocs (which don't claim that you can do "waitFor" commands, etc). Most Selenese features are there because the Selenese language is so simplistic; e.g. the "store" commands exist because Selenese doesn't have normal variables, so Perl doesn't need them. Specifically, in Test::More, there's no difference between assert/verify commands. Just use Test::WWW::Selenium to run "*_ok" commands; the test will continue running. As for the waitFor commands, you can implement those yourself just by sleeping and checking getters. Still, you're right, this would be a handy feature to add to T::W::S.

Andras Hatvani - 05/Nov/08 12:48 PM Changing issue type

Luke Closs - 05/Nov/08 03:08 PM You can use the $sel->wait_for_page_to_load_ok() method if you want. It could be nice to have these in the core library as a nice to have. If you'd like to provide a patch, my latest code is here:   http://github.com/lukec/selenium-rc-perl/tree/master Cheers, Luke