QA/Tools/Selenium/AMO Automation: Difference between revisions
< QA
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
== Sounds great and all, but what does this do for / how does this help AMO? == | == Sounds great and all, but what does this do for / how does this help AMO? == | ||
# The idea is to not regress critical things like search, other functionality/ | # The idea is to not regress critical things like search, other functionality/page views | ||
# Limitation: not a unit test | # Limitation: not a unit test | ||
[1] This is the base URL, and what your test scripts will key off of | [1] This is the base URL, and what your test scripts will key off of | ||
Revision as of 09:06, 3 July 2008
Selenium IDE/RC and AMO, or: How I Learned to Stop Worrying and Love Automation
Questions? Feedback/suggestions? Email stephend@mozilla.com
How to record and play back Selenium IDE scripts
- Record the script(s) with Selenium IDE
- Be sure to record relative, not absolute paths (i.e. /en-US/firefox/some/AMO/url/, rather than https://preview.addons.mozilla.org/en-US/firefox/some/AMO/url
- Download and install Selenium RC -- literally just unzip it into its own folder
- From the command line, issue: java -jar selenium-server.jar -htmlSuite "*firefox" "https://preview.addons.mozilla.org" [1 -- just a footnote, don't enter me!] "/Users/stephend/Desktop/selenium-remote-control-1.0-SNAPSHOT/htmlSuite/testSuite.html" "/Users/stephend/Desktop/results.html" (substituting, of course, the folder name of your RC version and path/to/tests and path/to/results.html)
Sounds great and all, but what does this do for / how does this help AMO?
- The idea is to not regress critical things like search, other functionality/page views
- Limitation: not a unit test
[1] This is the base URL, and what your test scripts will key off of