On Tue, Oct 27, 2009 at 9:58 AM, Naoko Komura <nkomura(a)wikimedia.org> wrote:
Thought to share the early concept of automating user
interface testing
using Selenium. The following plan was outlined by Ryan Lane. The goal
is to have the central location of client testing, and open up the test
case submission to MediaWiki authors and allows the reuse of test cases
simultaneously to multiple users.
http://usability.wikimedia.org/wiki/Resources#Interaction_testing_automation
Feel free to add your comments and input to the discussion page.
(preferred over email thread)
Will keep you all posted with the progress.
Thanks,
- Naoko
Usability Initiative
This sounds like a good idea, but I'm having difficulty telling from
the Selenium documentation what the output looks like or what it is
able to test. It appears that one runs scripts in (or on top of) a
browser interface, so I assume the output is either the resulting HTML
after appropriate widgets have been clicked or an image of the
resulting rendered page? And so one would then compare that content
to previous versions and other browser versions of the same page to
check for bugs and regressions, yes? Is that gist of how Selenium is
designed to operate?
-Robert Rohde