On Thu, Jul 7, 2011 at 8:28 AM, Chad innocentkiller@gmail.com wrote:
On Thu, Jul 7, 2011 at 11:23 AM, Sumana Harihareswara sumanah@wikimedia.org wrote:
Thanks for the test & test suite! Just wanted to update you that it
seems
like fewer and fewer MediaWiki developers are interested in Selenium
tests,
and many are moving to other tools for automatic testing:
That being said: is there any reason to leave the Selenium support in core anymore?
I believe work still needs to be done to provide a test harness that uses QUnit for 'live-wiki' tests -- the current QUnit tests are standalone and run from static files, so can't test interaction with server-side behavior.
With our current QUnit tests you can see if your JS code does something on some input data or HTML you construct, but you can't, say, confirm that issuing a click event on the watch tab submits an API request and comes back with the expected result.
Interaction tests also tend to modify data -- by performing edits, creating accounts, changing settings, deleting things, undeleting things, etc. So, like the parser & phpunit tests that are potentially destructive, they either need to run on dedicated testing sites where that's acceptible, or the test harness needs to be able to set up / tear down a temporary wiki copy. Unlike the parser & unit tests, that temporary copy has to be actually exposed via the web so client-side tests can run.
-- brion