|
|
(4 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | For Native Lang Project
| + | =品質リスク= |
− | =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.
| + | =OpenOffice.org= |
− | | + | ==OpenOffice.org 3.1== |
− | =What should we do?=
| + | ==OpenOffice.org 3.2== |
− | for level 2 native-language project,
| + | ==OpenOffice.org 3.3== |
− | 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|EIS (Environment Information System)]].
| + | |
− | | + | |
− | *AutomationCAT-0 tests
| + | |
− | *Performance Tests
| + | |
− | *ConvWatch Tests
| + | |
− | | + | |
− | **http://blogs.sun.com/GullFOSS/entry/tests_on_eis
| + | |
− | | + | |
− | ==Dev/Snapshot Version(Alpha Version)== | + | |
− | we provide Developer Version every two week(?)
| + | |
− | you can try on it soon.
| + | |
− | | + | |
− | ==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===
| + | |
− | *[[JA/QA/TCM/30 Beta]]
| + | |
− | | + | |
− | ==Feature Freeze Test(English)==
| + | |
− | After 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=
| + | |
− | After UI and [[Feature_freeze|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 translation plan.
| + | |
− | # 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 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
| + | |
− | **[[Automating_Translation_QA]]
| + | |
− | *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]
| + | |
− | * additional information.
| + | |
− | ** [[NLC/localizedQA]]
| + | |
− | ** [[Testing_my_translation]]
| + | |
− | ** [http://wikis.sun.com/display/g11n/Translation+QA Translation QA]
| + | |
− | | + | |
− | ==History==
| + | |
− | *[[Special:PrefixIndex/Translation_for|Translation Plan]]
| + | |
− | | + | |
− | =l10n / Feature Freeze Test =
| + | |
− | we go on l10n Test with "l10n CWS builds".<br>
| + | |
− | we should seek out the issues on product for reduce the issues especially your language specific issues.
| + | |
− | | + | |
− | after this phase l10n and developer team try to fix all of them from high priority
| + | |
− | so some of the issues carry on next release.
| + | |
− | | + | |
− | *Point
| + | |
− | **forcus user and product.
| + | |
− | | + | |
− | ===Manual Test with TCM===
| + | |
− | | + | |
− | | + | |
− | | + | |
− | ===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/QA/TCM/|l10n TCM Test History in Ja-NL(Japanese)]]
| + | |
− | | + | |
− | =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
| + | |
− |
| + | |
− | ==Step 1==
| + | |
− | it is not must step but i recommend it.
| + | |
− | | + | |
− | 開始判定テスト/リリース・テスト工程受入れテスト<br>
| + | |
− | テストに耐えうるだけ安定しているかチェックするためのテスト。
| + | |
− | | + | |
− | ===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.
| + | |
− | | + | |
− | ==Step 2==
| + | |
− | ===Automation test with VCL Test Tool === | + | |
− | | + | |
− | ===Manual test with TestCaseManagement===
| + | |
− | | + | |
− | ==Step 3==
| + | |
− | # update the test status on QATrack
| + | |
− | # set the status as APPROVED in qatrack
| + | |
− | # get an approved build distributed to the mirror network
| + | |
− | | + | |
− | * [[Testing_my_translation]]
| + | |
− | * [[Release_Action_List_for_QA]]
| + | |
− | *pick from [http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=10219 this mail]
| + | |
− | | + | |
− | =Other QA=
| + | |
− | ==WebSite==
| + | |
− | *[[Website/Issues]]
| + | |
− | | + | |
− | =Link=
| + | |
− | *QA
| + | |
− | **[[Product_Release/Builds_FAQ]]
| + | |
− | **[[Product_Release]]
| + | |
− | **[[QA_Metrics]] issues metrics
| + | |
− | **'''[[QA_CETOOo]] '''
| + | |
− | **'''[[QA_reloaded]] '''
| + | |
− | **'''[[QA_status_Chart2]] '''
| + | |
− | | + | |
− | **'''[[HowTo_localize_qatesttool_environment]]'''
| + | |
− | **'''[[Qa/Types_of_Test]]'''
| + | |
− | | + | |
− | | + | |
− | | + | |
− | **'''[[OOo_QA_Participation_Steps]]'''
| + | |
− | **'''[http://blogs.sun.com/byuan/entry/i18n_l10n_test_guide_line i18n_l10n_test_guide_line]'''
| + | |
− | **'''[http://l10n.openoffice.org/localization/L10n_testplan.html L10n_testplan]'''
| + | |
− | **'''[[Product_Release/builds_uploaded]]'''
| + | |
− | **'''[http://qa.openoffice.org/ooQAReloaded/TestcaseSpecifications/ TestcaseSpecifications] '''
| + | |
− | | + | |
− | *QA team
| + | |
− | **[http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html QA-Reloaded-HowToStart]
| + | |
− | **[[Actionlist_for_fixed_Issues]]
| + | |
− | **[[Qa/To-Dos]]
| + | |
− | | + | |
− | *Build
| + | |
− | **[http://wiki.services.openoffice.org/wiki/KeyID_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]]
| + | |
− | | + | |
− | | + | |
− | *Blog
| + | |
− | **[http://r.hatena.ne.jp/foral/OpenOffice.org%20QA/?okmsg=%e3%83%95%e3%82%a3%e3%83%bc%e3%83%89%e3%82%92%e8%bf%bd%e5%8a%a0%e3%81%97%e3%81%be%e3%81%97%e3%81%9f%e3%80%82 All The People]
| + | |
− | | + | |
− | *CJK
| + | |
− | **[[HSQLDB_Localization]]
| + | |
− | | + | |
− | *Book
| + | |
− | **[http://www.amazon.com/Testing-Computer-Software-Cem-Kaner/dp/0471358460 Testing Computer Software(amazon.com)] Cem Kaner/Jack Falk/Hung Quoc Nguyen
| + | |