Calendar:QA TODO

From MozillaWiki
Revision as of 20:20, 7 December 2006 by Ctalbert (talk | contribs)
Jump to navigation Jump to search

Valid from December 7 to December 21

This is the calendar QA To Do list. Please pick an item and give us a hand! Let us know what you did on which ever task by adding a comment in the "Accomplishments" column. To do that, simply click "Edit" above, and replace the "<Add your accomplishment>" text with a short summary of what you did. If you have any questions please log into irc://irc.mozilla.org and join the #calendar-qa channel.

Thanks for the Help

ToDo List
Tasks Accomplishments
  • Update Test Day wiki page for the Dec 19th
  • Announce test day for the Dec 19th on the Calendar NewsGroup and the Calendar Blog
  • Create any needed Litmus test cases for the Dec. 19th test day.

Accomplishments

Accomplishments

<Add your accomplishment>

QA wanted bugs.

  • bug 327752 needs tester with WebDav share on Windows server
  • bug 339960 needs tester with WebDav share on OpenXChange server
  • bug 353722 Needs input from dmose
  • bug 347128 tested by Sebo, needs more testing regarding ftp server conf
  • bug 340488 needs testing (upgrade test from Sunbird 0.2)
  • bug 312533 needs testing (ftp issue)

Need to create three wiki templates for test days:

  • A template for a "Confirm unconfirmed bugs" focused test day
  • A template for "Litmus testing" focused test day
  • A template for "Feature testing" focused test day.

By having standard templates to use, we can lessen the chance that we will leave out important information and we can be certain that all the pertinent information is included for each test day. The same person does not have to do all three, and you can use the existing test day wiki pages as starters.

<Add your accomplishment>

Create upgrade calendar seeds from the ICS files checked in with the dataloss bugs

Lets link ics files we encounter in bugzilla to Calendar:QA_ICSCollection

Need to continue testing the migration wizard!

Add the bugs you find here! :-)

Create generic branding litmus testcases (look after the types of issues found in Bug 351155)

<Add your accomplishment>

Every week or two we should quickly have a look if any bug that was resolved as Fixed|W4M|Dup need to be supported by litmus, marked as [litmus testcase wanted]

Only fixed are important but W4M gives you good test cases, duplicates make testing easier so also should not be skiped

Have a look: resolved bugs


FYI: Calendar Checkins in the last 24 hours