http://mestachs.wordpress.com/2012/08/13/selenium-best-practices/ best and worst development practices Wed, 22 May 2013 05:48:45 +0000 hourly 1 http://wordpress.com/ http://mestachs.wordpress.com/2012/08/13/selenium-best-practices/#comment-2618 Sat, 13 Apr 2013 11:56:38 +0000 http://mestachs.wordpress.com/?p=766#comment-2618 [...] Read the full article… [...]

]]> http://mestachs.wordpress.com/2012/08/13/selenium-best-practices/#comment-2610 Thu, 04 Apr 2013 06:33:08 +0000 http://mestachs.wordpress.com/?p=766#comment-2610 Most framework encourage id/name for form/request binding so it fits “natural” to reuse them. Css Classes in my experience are more there to route the locator in the correct area of the page in case of non-unique name. And for xpath I avoid them like the pest.

]]> http://mestachs.wordpress.com/2012/08/13/selenium-best-practices/#comment-2603 Tue, 02 Apr 2013 19:13:49 +0000 http://mestachs.wordpress.com/?p=766#comment-2603 ID is the easy way, but it’s also the cheap way out. If you code with IDs, you can never have two elements on the same page. Using class names gives you the same concept, but you can have multiple elements on the page

]]>