2,088
edits
m (→QA) |
|||
| Line 43: | Line 43: | ||
** 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 litmus [http://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&testgroup_id=39&subgroup_id=661 test suite for localizers to use] during locale signoff. | |||
* Test Tools and Infrastructure | * Test Tools and Infrastructure | ||
| Line 49: | Line 50: | ||
*** Investigated integrating killableprocess.py into buildbot. We'd have to implement this in the twisted layer. I'm going to try filing a bug at them to see if we can get someone else to do this. | *** Investigated integrating killableprocess.py into buildbot. We'd have to implement this in the twisted layer. I'm going to try filing a bug at them to see if we can get someone else to do this. | ||
** Litmus- worked on {{bug|370211}}: updating cookie code to track test runs [coop] | ** Litmus- worked on {{bug|370211}}: updating cookie code to track test runs [coop] | ||
* Misc | |||
** Test Suite/HArness Survey followup: | |||
*** Working on mapping test suits to modules [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 preferred 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 = | ||
edits