2,088
edits
WeeklyUpdates/2007-03-26: Difference between revisions
Jump to navigation
Jump to search
m
→QA
m (→QA) |
|||
| Line 51: | Line 51: | ||
** Updated the Update Checker preferences [bc] | ** Updated the Update Checker preferences [bc] | ||
** Checked in the counter reftests and we are now running them. See [https://bugzilla.mozilla.org/show_bug.cgi?id=3247 bug 3247] (yes, this is a very old bug!) [robcee] | ** Checked in the counter reftests and we are now running them. See [https://bugzilla.mozilla.org/show_bug.cgi?id=3247 bug 3247] (yes, this is a very old bug!) [robcee] | ||
** Completed a | ** Completed a [http://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&testgroup_id=39&subgroup_id=661 litmus test suite for localizers]. The point is to have localizers use this during locale signoff. | ||
* Test Tools and Infrastructure | * Test Tools and Infrastructure | ||
| Line 60: | Line 60: | ||
* Community | * Community | ||
** Helped Emily Chen (Sun China) prepare for their testday and got her setup with admin rights in Litmus. [tracy] | ** Helped Emily Chen (Sun China) prepare for their testday and got her setup with admin rights in Litmus. This will be focused on Firefox. It is more Solaris oriented but we should be able to get some good general feedback about Firefox on any platform. [tracy] | ||
** Bugday on Tues March 20th: Jay's topic; Hendrix work - Sessions slow still. | ** Bugday on Tues March 20th: Jay's topic; Hendrix work - Sessions slow still. | ||
** Bugday planning document completed. [tracy] | ** [[Mozilla_QA_Community:Bug_Day:Planner|Bugday planning document]] completed. [tracy] | ||
* Misc | * Misc | ||
** Test Suite/ | ** Test Suite/Harness Survey follow-up: | ||
*** Working on mapping test suits to modules [ray and tchung] | *** Working on mapping test suits to modules. They will review this in a brownbag session next week. [ray and tchung] | ||
*** Working on the roadmap/flowchart to lead developers wanting to do unit tests from the type (C++ or JS) and nature (layout, content, directory services, etc) to a | *** Working on the roadmap/flowchart to lead developers wanting to do unit tests from the type (C++ or JS) and nature (layout, content, directory services, etc) to a recommended harness for them to use. This will include harness documentation, how to write the first unit test, and sample test cases. [ray] | ||
= Product Management and Marketing Updates = | = Product Management and Marketing Updates = | ||