From jQuery JavaScript Library

Scheduled goals

• Complete a unit test page for each UI module. Example:
  • Html: http://dev.jquery.com/view/trunk/ui/tests/uiTest.dialog.html
  • Js: http://dev.jquery.com/view/trunk/ui/tests/uiTest.dialog.js
• Run tests in all supported browsers and create tickets for failures
• Review code and docs to ensure complete coverage of tests
• Perform tests at major milestones as requested by the sprint dev team

Completed tasks

How to participate

The following test pages already exist:

• http://dev.jquery.com/view/trunk/ui/tests/uiTest.dialog.html
• http://dev.jquery.com/view/trunk/ui/tests/uiTest.draggable.html

You can

• Complete these test pages by writing any missing unit tests (compare docs and source code for which are missing):
  • dialog - rworth
  • draggables - rworth
• Write tests for other modules (put your name below if you're working on it):
  • accordian - ThrushAAX
  • datepicker -
  • droppables - rworth
  • resizables - digitalspaghetti
  • selectables - ThrushAAX
  • slider - digitalspaghetti
  • sortables -
  • tabs -
• Run unit tests in supported browsers and file a new ticket for any tests that fail. Examples:
  • #2516 [draggable] Unit Test failure: draggable-options-dragPrevention
  • #2517 [draggable] Unit Test failure: draggable-options-helper-function

Types of Tests

• default tests - calling with no options, calling on a clone, calling on an empty set, calling on a detached (not in the DOM) node
• options - may be any combination of:
  • true/false
  • range of values
  • setters - setTimeout( "$('#foo').data('<option>.<plugin>', <value>);", 3000);
• callbacks - each callback should call uiTestLog('<callback name>')
• methods - test for both chainability and seperate calling

Testers

• miksago: FF3, FF2.0.12, IE6, Opera Portable (AU, +11GMT)
• digitalspaghetti: Vista: FF2, FF3, IE7, Safari 3 | Ubuntu: FF2 (UK, GMT)
• scott_gonzalez: IE6 (US, -4GMT)
• ThrushAAX: XP: FF2, IE7, Opera 9.26 (US, -5GMT)
• xover: Any latest version browser on Leopard/Vista/Fedora9. (Norway, CET / GMT+1).

IRC

Keynotes

Writing a unit test:

• Have a look at the code to both: uiTest.dialog.html and uiTest.dialog.js
• Each test is two files, a *.html and a *.js one.
• The *.html file has two elements, #foo and #bar, these can be used for acting a test on.
• The main file uiTest.js converts the json to html. The test html file just includes any js files, and has some test-specific styling.
• 4 default tests for each plugin - calling with no options, calling on a clone, calling on an empty set, calling on a detached (not in the DOM) node
• Each link in a test links to a unit test, which we have to run manually.
• Test should be able to be used for the documentation as well. So each option will have a test for init, set, get, etc.

Full Logs

The logs for this groups irc channel (#jquery-sprint-test) on Freenode can be found at JQuerySprint/test/irclog