Topic on Talk:Requests for comment/Unit testing

A community member requests a document that fulfills the following:

• Imagine being a contributor who wants to add code and test it
• Link to internal step-by-step instructions rather than general external definitions of a term
  • (the "target group") will probably know the meaning of a term or tool - the point is how to use things in mediawiki context as a contributor
• Add linked steps on
  • where to commit the code
  • where to commit the tests
  • what button to press on what page to start the tests (if necessary)
  • where to watch the results
  • whom to call/ask if something breaks or tests fail
• Add infos about
  • which tools contributors can trigger themselves
  • which ones have to be started by wikimedia staff or automatically

so I'm just noting that here so people can tell me "that already exists! LINK" or improve existing documentation accordingly.

where to commit the code

• SVN (see below)

where to commit the tests

• Core tests
  • Selenium tests: (SVN trunk)/selenium/ (For those that still use/play with it)
  • PHPUnit / QUnit: (SVN trunk)/phase3/tests/ (and apparently some selenium tests are back in there)
• Extension tests
  • Should be under a folder in the extension's directory I think (although I can't find any to confirm)

what button to press on what page to start the tests (if necessary)

Don't need to (unless running local setups)

where to watch the results

• CR, someone will comment/fixme the revisions if appropriate
• IRC, CC spams the channel on a failed test (from phpunit tests)

whom to call/ask if something breaks or tests fail

• Mark it in CR (if someone elses fails)
• Attempt to fix it (preferably if its yours, or you can attempt to do others)

which tools contributors can trigger themselves

• None (Unless they are self hosting/running the tests on their boxes)
  • CC automatically does the PHPunit tests
  • Krinkle manages the TestSwarm on the TS (JS tests)

which ones have to be started by wikimedia staff or automatically

• Automagically
  • If CC breaks -> ^demon/Hex

Peachey88 wrote:

which tools contributors can trigger themselves

• None (Unless they are self hosting/running the tests on their boxes)
  • CC automatically does the PHPunit tests
  • Krinkle manages the TestSwarm on the TS (JS tests)

I'd make that instead:

• • TestSwarm automatically does the QUnit tests (currently on TS by Krinkle, to be moved to WMF)