QA/Execution/Web Testing/Selenium Guidelines: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
* wherever possible, use relative--not absolute--URLs in |open| commands
* wherever possible, use relative--not absolute--URLs in |open| commands
=PHP=
=PHP=
* Locating elements
** xpath: for elements that have dynamically generated xpaths use 'contains'.
          for e.g. if xpath for 'remove add-on' link has the add-on ID
          in it (id('addon-2464')/a[1]) and we do not know the add-on ID then
          we can write the xpath with 'contains'
          //div[@id,'addon-2464'][2]/a[1]) => //div[contains(@id,'addon- ')][2]/a[1]

Revision as of 23:25, 23 October 2009

Here be some Selenium guidelines (mostly for writing, but include running here too).

IDE

  • click vs. clickAndWait - use the latter on anything that requires network activity, but if you use the former on other buttons/links, your script will pause indefinitely
  • verifyLocation - use w/regexp; otherwise it'll be absolute (I think)
    • e.g. ...
  • wherever possible, use relative--not absolute--URLs in |open| commands

PHP

  • Locating elements
    • xpath: for elements that have dynamically generated xpaths use 'contains'.
         for e.g. if xpath for 'remove add-on' link has the add-on ID 
         in it (id('addon-2464')/a[1]) and we do not know the add-on ID then
         we can write the xpath with 'contains'
         //div[@id,'addon-2464'][2]/a[1]) => //div[contains(@id,'addon- ')][2]/a[1]
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Selenium_Guidelines&oldid=178087"