Difference between revisions of "User:Foral/QA"

From Apache OpenOffice Wiki
Jump to: navigation, search
(→‎Dev/Snapshot Version(Alpha Version))
(→‎Developing OpenOffice.org)
Line 28: Line 28:
 
**http://blogs.sun.com/GullFOSS/entry/tests_on_eis
 
**http://blogs.sun.com/GullFOSS/entry/tests_on_eis
  
−
==Translation==
+
==Dev/Snapshot Version(Alpha Version)==
 +
we provide Developer Version every two week(?)
 +
you can try on it soon.
 +
 
 +
 
 +
=Translation=
 
After UI and [[Feature_freeze|Feature]] freeze we are going on  
 
After UI and [[Feature_freeze|Feature]] freeze we are going on  
 
translation phase and then Feature and L10N Test.
 
translation phase and then Feature and L10N Test.

Revision as of 13:40, 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.


Translation

After UI and Feature freeze we are going on translation phase and then Feature and L10N Test.

It is a first step for release.

  1. Developer Team will pass the information of new Feature/UI to QA/Documents Team,traslation files to translation team(we call "translation handover").
  2. Translation Team translate until "translation delivery deadline" and pass back to Developer.

QA Team make a feature freezing test documents.

we use tool and style guide.

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

History

People

  • feature freezing test:
  • l10n tcm test:ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM

Automation Test and Check

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

  • Build
    • KeyID_Build it is helpfull for fix the translation mistake.
Retrieved from "https://wiki.openoffice.org/w/index.php?title=User:Foral/QA&oldid=131559"
Personal tools