User:Foral/QA
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.
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
Feature Freeze Test(English)
After 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 translation 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.
- Tool
- Guide
- additional information.
History
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.
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
History
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.
開始判定テスト/リリース・テスト工程受入れテスト
テストに耐えうるだけ安定しているかチェックするためのテスト。
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
Other QA
WebSite
Link
- QA
- 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
- Book
- Testing Computer Software(amazon.com) Cem Kaner/Jack Falk/Hung Quoc Nguyen