Difference between revisions of "User:Foral/QA"
(→Translation) |
(→l10n Test) |
||
Line 80: | Line 80: | ||
we should seek out the issues on product for reduce the issues<br> | we should seek out the issues on product for reduce the issues<br> | ||
especially your language specific issues.<br> | especially your language specific issues.<br> | ||
− | |||
− | |||
− | |||
− | |||
*Point | *Point |
Revision as of 13:05, 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.
All the Time
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
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
Dev/Snapshot Version(Alpha Version)
Feature Freeze Testing
After the UI and Feature freeze we are going on to Feature Test. It is a first step for release.We will pass the infomation of new Feature and UI to translation/Documentation Team and the infomation of issues to developer for fix.developer try to fix the issues until Code_freeze and some of issues carry over to future release.
History
Development
Translation
we use tool and style guide.
l10n Test
After the translation and make a document we are going on l10n Test.
we should seek out the issues on product for reduce the issues
especially your language specific issues.
- Point
- It is not just translation ckeck.
- forcus user and product.
Manual Test with TCM
- Help Contens
ヘルプの内容、ヘルプシステム自体の正しさ、ヘルプシステム機能の正確さを確認する。
- Message
- Product
History
People
- ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM
Automation Test and Check
Programing:OpenOffice.org
Coding and working on child work space with EIS (Environment Information System).
- AutomationCAT-0 tests
- Performance Tests
- ConvWatch Tests
Instalation
Programing:OpenOffice.org Extension
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