Difference between revisions of "User:Foral/QA"
(→Developing OpenOffice.org) |
(→Translation) |
||
Line 32: | Line 32: | ||
you can try on it soon. | you can try on it soon. | ||
+ | |||
+ | =Feature Freeze Test(English)= | ||
+ | UI and [[Feature_freeze|Feature]] freeze QA Team may go on feature freezing test. | ||
+ | |||
+ | # Developer Team pass the information of new Feature/UI to QA/Documents Team | ||
+ | # QA Team make a feature freezing test documents. | ||
+ | |||
+ | ==History== | ||
+ | *[[Special:PrefixIndex/Feature_Freeze_Testing|Feature Freezeing Test]] | ||
=Translation= | =Translation= | ||
− | After UI and [[Feature_freeze|Feature]] freeze we | + | After UI and [[Feature_freeze|Feature]] freeze we go on translation phase |
− | translation phase and then Feature and L10N Test. | + | and then Feature and L10N Test. |
It is a first step for release. | It is a first step for release. | ||
− | # Developer Team | + | # L10N project lead may be planed and show you that plan. |
− | # Translation Team translate until "translation delivery deadline" | + | # Developer Team pass traslation files to translation team(we call "translation handover"). |
− | + | # we translate on online with [http://www.sunvirtuallab.com:32300/ pootle] or offline. | |
+ | # Translation Team translate until "translation delivery deadline" | ||
+ | # Translation Team pass back to Developer. | ||
− | we use | + | we use some of the document(glossary , translation memory) and tools for translation QA. |
+ | you should make it as soon as possible if you do not have it. | ||
+ | it is helpful for reduce the translation issues. | ||
*Tool | *Tool | ||
**[[Automating_Translation_QA]] | **[[Automating_Translation_QA]] | ||
+ | |||
*Guide | *Guide | ||
**[http://blogs.sun.com/reiko/entry/%E3%82%B9%E3%82%BF%E3%82%A4%E3%83%AB%E3%82%AC%E3%82%A4%E3%83%891 Japanese Translation Style Guide] | **[http://blogs.sun.com/reiko/entry/%E3%82%B9%E3%82%BF%E3%82%A4%E3%83%AB%E3%82%AC%E3%82%A4%E3%83%891 Japanese Translation Style Guide] | ||
− | *[http://wikis.sun.com/display/g11n/Translation+QA Translation QA] | + | * additional information. |
+ | ** [http://wikis.sun.com/display/g11n/Translation+QA Translation QA] | ||
==l10n / Feature Freeze Test == | ==l10n / Feature Freeze Test == | ||
Line 61: | Line 76: | ||
===Manual Test with TCM=== | ===Manual Test with TCM=== | ||
*Help Contens | *Help Contens | ||
− | |||
*Message | *Message | ||
*Product | *Product | ||
− | === | + | ===Automation Test and Check=== |
− | *[[ | + | * [[Automatic_Creation_Of_Dialog_Screenshots]] |
+ | |||
+ | |||
+ | ==History== | ||
*[[Special:PrefixIndex/JA/translation/Feature_Freeze_Testing|Feature Freezeing Test Japanese Translated]] | *[[Special:PrefixIndex/JA/translation/Feature_Freeze_Testing|Feature Freezeing Test Japanese Translated]] | ||
*[[Special:PrefixIndex/JA/QA/TCM/|l10n TCM Test History in Ja-NL(Japanese)]] | *[[Special:PrefixIndex/JA/QA/TCM/|l10n TCM Test History in Ja-NL(Japanese)]] | ||
− | + | ==People== | |
− | + | ||
*l10n tcm test:ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM | *l10n tcm test:ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM | ||
− | |||
− | |||
− | |||
=Bata Version= | =Bata Version= |
Revision as of 13:57, 12 June 2009
For Native Lang Project
Contents
What is Quality ?
Aim of test are improved quality. so what is a quality?of cause quality is satisfaction of OpenOffice.org. however, the Quality not equal reliability.just reliability is one of the quality. nobody satisfy if they could not use even if the product have perfect reliability.
for QA team,take preventive measures is most important.
What should we do?
for level 2 native-language project, it might be quality control team for your language and quality assignment member for l10n.
so we should do
- for term work
- we should test for rc/dev.
- for the daily work
- we should keep on try to make a good translation.
Developing OpenOffice.org
Coding and working on child work space with EIS (Environment Information System).
- AutomationCAT-0 tests
- Performance Tests
- ConvWatch Tests
Dev/Snapshot Version(Alpha Version)
we provide Developer Version every two week(?) you can try on it soon.
Feature Freeze Test(English)
UI and Feature freeze QA Team may go on feature freezing test.
- Developer Team pass the information of new Feature/UI to QA/Documents Team
- QA Team make a feature freezing test documents.
History
Translation
After UI and Feature freeze we go on translation phase and then Feature and L10N Test.
It is a first step for release.
- L10N project lead may be planed and show you that plan.
- Developer Team pass traslation files to translation team(we call "translation handover").
- we translate on online with pootle or offline.
- Translation Team translate until "translation delivery deadline"
- Translation Team pass back to Developer.
we use some of the document(glossary , translation memory) and tools for translation QA. you should make it as soon as possible if you do not have it. it is helpful for reduce the translation issues.
- additional information.
l10n / Feature Freeze Test
we go on l10n Test with "l10n CWS builds".
we should seek out the issues on product for reduce the issues
especially your language specific issues.
- Point
- forcus user and product.
Manual Test with TCM
- Help Contens
- Message
- Product
Automation Test and Check
History
People
- l10n tcm test:ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM
Bata Version
An early view of the next major release of OOo. A beta has all the features of the new release, but may still contain significant bugs
Manual test with TestCaseManagement
Development
RC Version(Release Test)
Aim of Release testing.
- release enginialing
- build and mirror by joost
- build by Maho(Mac OS port)
- build by ....
Release Meeting on IRC: Release Team Mailing List:
Release Engineering Team Lead - Martin Hollmichel
First Step
開始判定テスト/リリース・テスト工程受入れテスト
テストに耐えうるだけ安定しているかチェックするためのテスト。
AutomationCAT-0 tests :VCLTestTool Release Test
Release tests are those which must run . These tests should finish without any failure.
we need approximately 8 hours and use the VCLTesttool with a couple of selected test scripts (called the CAT-0 tests) to check the quality of an OpenOffice.org installation.
Second Step
Automation test with VCL Test Tool
Manual test with TestCaseManagement
Instalation
Support
WebSite
Link
- QA
- Product_Release/Builds_FAQ
- Product_Release
- QA_Metrics issues metrics
- QA_CETOOo
- QA_reloaded
- QA_status_Chart2
- Release_QA_Tracking_Tool
- HowTo_localize_qatesttool_environment
- Qa/Types_of_Test
- How_to_recognize_a_Showstopper
- Handling_Translation_Issues
- Sanity_Check_Of_L10n_Builds
- OOo_QA_Participation_Steps
- Handling_Translation_Issues
- i18n_l10n_test_guide_line
- L10n_testplan
- Product_Release/builds_uploaded
- TestcaseSpecifications
- Build
- KeyID_Build it is helpfull for fix the translation mistake.
- About Automation TestTool
- Automation
- QAAutomation talk about what leve of error show by testing tool
- QUASTe
- QATrack
- Blog
- Book
- Testing Computer Software(amazon.com) Cem Kaner/Jack Falk/Hung Quoc Nguyen