L10n/HomePage/Status/2007-05-16: Difference between revisions

Jump to navigation Jump to search
No edit summary
 
Line 20: Line 20:
New this year we will delay Beta 2 to get localized builds. We will be putting in place a 2-week string freeze, meaning there will be 2 weeks before the release of Beta 2 without any string changes. We expect this will enable Localizers to be able test their version before this string freeze. We will offer two types of testing, 3rd party testing by Smartware and our own QA testing.  The SmartWare testing will test for language accuracy for all Tier 1 and most of Tier 2 locales and should take 3 days per locale. They have specialists in each locale and should be able to handle the work over 2 weeks. Other locales will get Mozilla QA testers to spot check each locale for e.g., funny font interpretation, help menu accuracy, etc., which should take 30 minutes per locale per platform. This timing will be affected by whatever other priorities the QA team will be doing for Fx3.  
New this year we will delay Beta 2 to get localized builds. We will be putting in place a 2-week string freeze, meaning there will be 2 weeks before the release of Beta 2 without any string changes. We expect this will enable Localizers to be able test their version before this string freeze. We will offer two types of testing, 3rd party testing by Smartware and our own QA testing.  The SmartWare testing will test for language accuracy for all Tier 1 and most of Tier 2 locales and should take 3 days per locale. They have specialists in each locale and should be able to handle the work over 2 weeks. Other locales will get Mozilla QA testers to spot check each locale for e.g., funny font interpretation, help menu accuracy, etc., which should take 30 minutes per locale per platform. This timing will be affected by whatever other priorities the QA team will be doing for Fx3.  


We haven't dropped idea of some level of automated testing done between beta 1 and beta 2 to give us an idea of how well tings are running or not; although this is dependent on many variables. There are XML parser tests, QA test for preferences like key branding and possibly more. If we can write an automated to get screen shots on all 3 platforms we may be able to reduce work required to look at a particular build. This would be good possibly using eggplant and Tracy and Juan from the QA team could possibly work on this. This automated testing would still need to happen when UI is frozen (either 2 week string freeze period or after beta 2). It is best to use builds the Localizes and Build team have signed off on and apply the same test and time cycle as we did for Fx2.  
We haven't dropped idea of some level of automated testing done between beta 1 and beta 2 to give us an idea of how well things are running or not; although this is dependent on many variables. There are XML parser tests, QA tests for preferences like key branding and possibly more. If we can write an automated tool to get screen shots on all 3 platforms we may be able to reduce work required to look at a particular build. This would be good possibly using eggplant and Tracy and Juan from the QA team could possibly work on this. This automated testing would still need to happen when UI is frozen (either 2 week string freeze period or after beta 2). It is best to use builds the Localizers and Build team have signed off on and apply the same test and time cycle as we did for Fx2.  
ACTION: Tim will check in on this
ACTION: Tim will check in on this


Our next discussion item (for next week) is to ensure the testing requirements are clear. Meaning, to know exactly which tests we want done during what time period. A bad thing would be tests oozing out of now where (like let's add this one and that one, etc). We need to define exactly what our main focus for this should be; ensure we're working on same main tests; furthermore, it would be nice to write a list of what we're planning with rob. Axel has created a [[L10n:Testing|write-down00 for l10n-testing (not in right order) but is intact. He has also [[L10n_Talk:Testing|proposed]] another way to conduct the search testing. This will also be a discussion item for next week. Folks can also check out [Firefox:1.5.0.12-2.0.0.4:Test_Plan:beta_checks]
Our next discussion item (for next week) is to ensure the testing requirements are clear. Meaning, to know exactly which tests we want done during what time period. A bad thing would be tests oozing out of nowhere (like let's add this one and that one, etc). We need to define exactly what our main focus for this should be; ensure we're working on same main tests; furthermore, it would be nice to write a list of what we're planning with rob. Axel has created a [[L10n:Testing|write-down]] for l10n-testing (not in right order) but is intact. He has also [[L10n_Talk:Testing|proposed]] another way to conduct the search testing. This will also be a discussion item for next week. Folks can also check out [[Firefox:1.5.0.12-2.0.0.4:Test_Plan:beta_checks]]


ACTION: Tim to get Clint and RobCee to attend next week's session
ACTION: Tim to get Clint and RobCee to attend next week's session
Confirmed users, Bureaucrats and Sysops emeriti
1,737

edits

Navigation menu