Qa/Types of Test
Introduction
To provide users with our products at good quality, the OpenOffice.org community has been conducting several types of tests through the development process of our products. The schedule is tighten. There is no extra time to cover entire products. We focus on the certain items so that the products will be delivered into the market on time.
Types of test
The tests that will be accomplished during development process can be basically classified into three ones: Functional test, Localization test, and Release test. The following table shows differences among them.
| Aims | Targets | Criteria | Period | Requisites | |
|---|---|---|---|---|---|
| Functional test | Ensuring that functions work | Functions that have been added or modified | The functions should work with local languages. | N/A (*1) | Information on the functions, such as specifications |
| Localization test | Achieving translation quality sufficient | Translated texts that have been added or revised. | The translations should be appropriate in the context. | One or two weeks | Information on how to get the dialogs with the translations, how to get their relevant on-line help pages |
| Release test | Releasing builds at good quality ASAP | Each installation package (*2) | No show-stopper; Good for casual, daily use | A week (*3) | Knowledge of target languages |
(*1) This is continuous work.
(*2) No need to keep Sun and community builds apart
(*3) In fact we have some days (current release schedule says that an RC will become final after a week, if no stoppers are found)
Note that functional test does not mainly focus on l10n testing but we need to identify functionality that depends on localization.
Another type of test
This type of test should be done on a daily basis with released and/or under-development builds, which covers entire products including local language specific functionalities and translations.
