QA/Tools/Selenium/AMO Automation: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 10: Line 10:
## Change the |href=| filename to match each of your testcase filenames
## Change the |href=| filename to match each of your testcase filenames
# 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)
# 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)
[1] This is the base URL, and what your test scripts will key off of


== 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? ==
Line 15: Line 17:
# The idea is to not regress critical things like search, other functionality/page views
# 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
Confirmed users
9,511

edits

Navigation menu