Calendar:QA TODO

From MozillaWiki
Revision as of 20:48, 9 November 2006 by Sebo (talk | contribs)
Jump to navigation Jump to search

Valid from October 31 to November 14

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

<Add your accomplishment>

  • Update Test Day wiki page for the 14th
  • Announce test day for the 14th

Announcement done (ctalbert)

Urgent: QA wanted bugs. Need to address as many as possible by QA Chat on November 9th

  • bug 287514 needs tester with Solaris system
  • bug 348806 needs tester with iCal app. or response from reporter
  • bug 327752 needs tester with WebDav share on Windows server
  • bug 339960 needs tester with WebDav share on OpenXChange server
  • bug 293562 needs testing with Mac server (ctalbert?)
  • bug 353722 tested by ssitter and lilmatt (Needs to be tested on branch build of Lightning)
  • bug 347128 tested by Sebo (needs more testing regarding ftp server conf!)
  • bug 249796 has been tested by Sebo - needs to be closed with follow-up bugs
  • bug 340488 needs testing (upgrade test from Sunbird 0.2)
  • <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

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

<Add your accomplishment>

Check out event dragging. Especially with recurrences. Bugs to be found! (see e.g. bug 352862 and bug 336952)

<Add your accomplishment>

Continue to add testcases to litmus from bugzilla bugs

Damian

- marked as wanted (complete)

- already added into Litmus (complete)

(there are a few more but there is not clear how to create good test case)

Litmus: test cases with id>2636 have not been assigned to subgroups

<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

Add test cases in litmus. Scenario comes from matrix

List of test cases that have been added to litmus


FYI: Calendar Checkins in the last 24 hours