Difference between revisions of "User:Foral/QA"
(→RC Version(Release Test)) |
(→First Step) |
||
| Line 13: | Line 13: | ||
**build and mirror by joost | **build and mirror by joost | ||
==First Step== | ==First Step== | ||
| − | 開始判定テスト/リリース・テスト工程受入れテスト | + | 開始判定テスト/リリース・テスト工程受入れテスト<br> |
テストに耐えうるだけ安定しているかチェックするためのテスト。 | テストに耐えうるだけ安定しているかチェックするためのテスト。 | ||
| − | + | ||
| − | + | ||
===VCLTestTool Release Test=== | ===VCLTestTool Release Test=== | ||
Release tests are those which must run . These tests should finish without any failure. | Release tests are those which must run . These tests should finish without any failure. | ||
but foutunetry it should be done for english/german version by release englinialing team. | but foutunetry it should be done for english/german version by release englinialing team. | ||
| − | but we should do on own lang for the | + | but we should do on own lang for the |
| + | |||
==Second Step== | ==Second Step== | ||
===Automation test with VCL Test Tool === | ===Automation test with VCL Test Tool === | ||
Revision as of 06:11, 3 May 2009
For Native Lang Project
Contents
What is QA?
What should we do?
let us hanting issues.
General
RC Version(Release Test)
Aim of Release testing.
- release enginialing
- build and mirror by joost
First Step
開始判定テスト/リリース・テスト工程受入れテスト
テストに耐えうるだけ安定しているかチェックするためのテスト。
VCLTestTool Release Test
Release tests are those which must run . These tests should finish without any failure.
but foutunetry it should be done for english/german version by release englinialing team. but we should do on own lang for the
Second Step
Automation test with VCL Test Tool
Manual test with TestCaseManagement
l10n Test
seek out the issues and reduce the issues until release
especially your language specific issues.
Manual Test with TCM
ISHIMURA Naoyuki: Naoyuki.Ishimura at Sun.COM
Automation Test and Check
Automation Test
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
Dev Build(Alpha Version)
General
The second step ("Manual testing") is meant for participants with more skills. You are able to do manual testing on your own. You can execute and write Test-Case-Specifications (TCS) and submit issues found when dealing with Test-Case-Specifications. The page contains all information needed to contribute to the second participation step.
Feature Freeze Testing
- Feature Freeze Testing 2.0.4
- Feature Freeze Testing 2.1
- Feature Freeze Testing 2.2
- Feature Freeze Testing 2.3
- Feature Freeze Testing 2.4
- Feature Freeze Testing 3.0
- Feature Freeze Testing 3.1
Development
Translation
Programing:OpenOffice.org
- Coding
Instalation
Programing: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
- QA team
- 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
