http://www.andygoundry.com/2009/09/04/using-cucumber-webrat-and-selenium-to-test-ajax-form-field-validations/ web developer Wed, 21 Dec 2011 14:54:09 -0500 http://wordpress.org/?v=2.8.4 hourly 1 http://www.andygoundry.com/2009/09/04/using-cucumber-webrat-and-selenium-to-test-ajax-form-field-validations/comment-page-1/#comment-228 andy Mon, 23 Nov 2009 11:49:03 +0000 http://www.andygoundry.com/?p=439#comment-228 Many thanks for your comment Jason and for a great tool! Version 2 sounds like a great evolution too. Many thanks for your comment Jason and for a great tool! Version 2 sounds like a great evolution too.

]]> http://www.andygoundry.com/2009/09/04/using-cucumber-webrat-and-selenium-to-test-ajax-form-field-validations/comment-page-1/#comment-199 Jason Huggins Fri, 04 Sep 2009 19:56:46 +0000 http://www.andygoundry.com/?p=439#comment-199 Andy, as the creator of Selenium, I have to apologize for the behavior you found in Selenium. :-) But thanks for finding the work around! Selenium's goal is to test web apps just as a user would. But since it was implemented in JavaScript, we cut some corners. We're fixing this, though, in Selenium 2.0 -- we'll be using Native OS mouse and keyboard Events to interact with elements on a web page, so there won't be any need for event fackery behind the scenes. (Though we'll still leave fireEvent in place for those hard-to-predict edge cases that'll still need the fackery.) Andy, as the creator of Selenium, I have to apologize for the behavior you found in Selenium. But thanks for finding the work around! Selenium’s goal is to test web apps just as a user would. But since it was implemented in JavaScript, we cut some corners. We’re fixing this, though, in Selenium 2.0 — we’ll be using Native OS mouse and keyboard Events to interact with elements on a web page, so there won’t be any need for event fackery behind the scenes. (Though we’ll still leave fireEvent in place for those hard-to-predict edge cases that’ll still need the fackery.)

]]>