Calendar:QA TODO: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(test cases completed)
(complet import/export test cases in litmus)
Line 87: Line 87:
||
||
Have a look: [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Calendar&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=notregexp&status_whiteboard=%5C%5Blitmus+testcase+wanted%5C%5D&keywords_type=allwords&keywords=&resolution=FIXED&resolution=DUPLICATE&resolution=WORKSFORME&emailtype1=exact&email1=&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=14D&chfieldto=Now&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= resolved bugs]
Have a look: [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Calendar&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=notregexp&status_whiteboard=%5C%5Blitmus+testcase+wanted%5C%5D&keywords_type=allwords&keywords=&resolution=FIXED&resolution=DUPLICATE&resolution=WORKSFORME&emailtype1=exact&email1=&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=14D&chfieldto=Now&chfield=resolution&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= resolved bugs]
|-
|
<strike>Add test cases in litmus. Scenario comes from [[Calendar:QA_TestDay:2006-10-17:Matrix | matrix]]</strike>
||
<strike>List of test cases that have been added to [http://litmus.mozilla.org/show_test.cgi?recently=added&num_days=3&match_limit=50 litmus]</strike>
|-
|-
|}
|}

Revision as of 15:46, 29 October 2006

Valid from September 5 to October 12

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>

QA wanted bugs

  • bug 351581 tested by Sebo and ssitter - needs more testing (esp. on unix and mac systems
  • bug 279739 needs some ideas how to test this, probably invalid (Sebo)
  • bug 351944 tested by Sebo and ssitter (Needs testing on Mac)
  • bug 353722 tested by ssitter (Needs to be tested on branch build of Lightning)
  • bug 347128 tested by Sebo (more needed? probably not,waiting on response from jminta)
  • <Add your accomplishment>

Upgrade testing from 0.3a2 and 0.3a1 Sunbird to 0.3 Sunbird

  • bug 353307 found relevant to upgrading from 0.3a1 (Sebo)
  • <Needs more testing: Add your accomplishment>

Upgrade testing from 0.1 Lightning to 0.3 Lightning (using 1.5 Thunderbird)

  • Bery found this to work without any issues!
  • Needs more testing: Add your accomplishment

Upgrade testing (if possible) from 0.2 Sunbird to 0.3 Sunbird

Need to create a list for people to follow in this process. see Calendar: Upgrading from Sunbird 0.2 <Needs testing: Add your accomplishment>

Upgrade testing from Calendar Extension for thunderbird to 0.3 Lightning

<Add your accomplishment>

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

<Add your accomplishment>

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