Selenium Day Notes, Reference, and Best Practices

Grab a test plan from the counter near the table (where the food is).
SSH to the machine bugday.cnx.rice.edu, and enter the directory /opt/zope/bugday/Products/CNXSeleniumTests/skins/CNXSeleniumTests
Figure out what your test plan is basically called, like "Links" or "Forking". Copy the file SDSampleTestSuite.html.dtml and call the file (for example) SDForking.html.dtml.
Copy SDSampleTestPlan.html.dtml to something like SDForking-Modules.html.dtml.
Edit the suite file to point to your first test plan file -- that is, replace the string SDSampleTestPlan.html with the name of your test plan file.
Edit the test plan file to start building tests. To run your tests, go to, e.g., http://bugday.cnx.rice.edu/TestRunner.html?test=SDForking.html

To run your test suite in Selenium:
- http://bugday.cnx.rice.edu/TestRunner.html?test=[TestSuiteFile.html]
Selenium Command Reference
Basic XPath Syntax
Complete Test Plan File : to check how your test plan relates to others
SeleniumMacros

Maximize rigor, minimize fragility
- Given a choice among addressing schemes, use the one that's most specific, but least likely to change over time.
- Use the simplest addressing scheme that works consistently, e.g.: link=, then id=, then name=, etc.
Use goBackAndWait instead of goBack. More than one goBack without a pause and you will likely get errors. Thanks, Cameron!

For today, let's start everything with "SD" for SeleniumDay?. I can regularize them later.
Name your test suite files SD[something].html.dtml and your test plan files SD[something]-[somethingelse].html.dtml.
Example: SDLinks.html.dtml and SDLinks-AddLinks.html.dtml.
Studly caps (internal capitalization, meaning "mixed caps", or init-capped words) makes things easier to read.