Confirmed users
9,511
edits
QA/Tools/Selenium/AMO Automation: Difference between revisions
Jump to navigation
Jump to search
→Sounds great and all, but what does this do for / how does this help AMO?
No edit summary |
|||
| Line 18: | Line 18: | ||
== 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? == | ||
Pros: | |||
# The idea is not to regress critical things like search, other functionality/page views | # The idea is not to regress critical things like search, other functionality/page views | ||
# Should let us focus on verifying new functionality works as expected | # Should let us focus on verifying new functionality works as expected | ||
# | # Rapid turnaround on automating user actions | ||
Cons: | |||
# Not a subtitute for a unit test | |||
# Can't really test layout well | |||