You're doing it wrong

The document discusses best practices for Selenium testing. It suggests using descriptive names like "scripts" or "checks" instead of "tests", focusing on replacing humans with higher quality builds rather than automation, exporting scripts from Selenium IDE, using custom page object classes instead of inheriting directly from the test framework, storing locators externally rather than internally, using structural rather than brittle locators, feeding data externally rather than internally, using a page object pattern rather than procedural style, tagging scripts for discovery rather than suites, running scripts from a CI server rather than locally, using browser specific jobs rather than Selenium Grid for cross-browser testing, and using judgment in deciding what advice to follow rather than blindly implementing everything suggested.