Difference between revisions of "User:Foral/QA"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Step 1)
(Step 3)
Line 138: Line 138:
  
 
==Step 3==
 
==Step 3==
1) update the test status on QATrack
+
# update the test status on QATrack
2) set the status as APPROVED in qatrack
+
# set the status as APPROVED in qatrack
3) get an approved build distributed to the mirror network
+
# get an approved build distributed to the mirror network
  
 
* [[Testing_my_translation]]
 
* [[Testing_my_translation]]
 
* [[Release_Action_List_for_QA]]
 
* [[Release_Action_List_for_QA]]
 +
*pick from [http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=10219 this mail]
  
 
=Support=
 
=Support=

Revision as of 14:06, 12 June 2009

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.

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.

  1. Developer Team pass the information of new Feature/UI to QA/Documents Team
  2. 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.

  1. L10N project lead may be planed and show you that plan.
  2. Developer Team pass traslation files to translation team(we call "translation handover").
  3. we translate on online with pootle or offline.
  4. Translation Team translate until "translation delivery deadline"
  5. 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.

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.

  • 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

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

  1. update the test status on QATrack
  2. set the status as APPROVED in qatrack
  3. get an approved build distributed to the mirror network

Support

WebSite

Link

  • Build
    • KeyID_Build it is helpfull for fix the translation mistake.
Personal tools