Selenium: Difference between revisions
From Genecats
Jump to navigationJump to search
Line 15: | Line 15: | ||
** [http://seleniumhq.org/docs/06_test_design_considerations.html Test Design Considerations] | ** [http://seleniumhq.org/docs/06_test_design_considerations.html Test Design Considerations] | ||
* [http://agiletesting.blogspot.com/2006/03/ajax-testing-with-selenium-using_21.html Testing Ajax apps with Selenium] - note that | * [http://agiletesting.blogspot.com/2006/03/ajax-testing-with-selenium-using_21.html Testing Ajax apps with Selenium] using waitForCondition - note that waitForCondition is now part of Selenium core (not a plugin as this article mentions). | ||
=Element Locators= | =Element Locators= |
Revision as of 01:23, 19 November 2011
This is mostly a place holder while we develop more content. Here are some useful links...
The Basics
- Testing Ajax apps with Selenium using waitForCondition - note that waitForCondition is now part of Selenium core (not a plugin as this article mentions).
Element Locators
A common way to find elements on a page using Selenium is xPath, however, we should use CSS selectors when possible, as the tests run faster - especially in IE. Here's some info:
Selenium Resources
- The Official Selenium Blog
- Selenium Users Group (Google)
- Selenium Wiki
- OpenQA Selenium Wiki
- SauceLabs Selenium Blogs Posts
- Selenium Examples blog - examples and tips for Selenium
- Selenium Conference
General Automated Testing Resources
- The Testing Blog
- Software Testing Best Practices blog
- Web application testing checklists: