SL/Sanity Check Of L10n Builds

Ta stran vsebuje kratek nabor navodil, kako izvedemo preizkus zdrave pameti lokaliziranih gradenj.

Kaj je preizkus zdrave pameti?

Preizkus zdrave pameti (angl. sanity check) je hiter preizkus gradnje.

Zakaj je potrebno izvesti preizkus zdrave pameti

A sanity check is necessary to make sure that there were no errors in the building process. It is not supposed to go deep into the application functionality. Instead, it should focus on possible problems that are caused by errors in the building process and integration of translation into the builds.

Katera področja naj pokriva preizkus zdrave pameti

This depends on how much time there is for the sanity check. As the usual period for the sanity check is quite short, the area that a sanity check can cover is quite limited. However, the following areas should be tested in every sanity check:

1. Namestite pisarniški paket

   Namestitev je mogoče uspešno izvesti.

2. Zaženite module

   Vsi programi paketa se pravilno zaženejo (Writer, Calc, Impress, Draw, Base)

3. Preverite menije in pogovorna okna

   Go through the menu structure and make sure that all menu items are localized. Open several random dialogs and make sure that they are localized as well.

4. Odprite obstoječe datoteke, jih uredite in shranite

   Use files containing localized characters. Try to edit them and then save them in various formats (ODF, MS Office, OOo 1.x) and reopen them to make sure everything is displayed correctly.

5. Vnesite lokalizirano besedilo in ga oblikujte

   There should be no problems when working with localized text. Try to create a short document containing localized text and some basic formatting settings (headings, tables, hyperlinks, ...).

6. Preverite vsebino pomoči

   Open the Help, check the Table of Contents, the Index and make sure that searching works. Try to search for a localized string. Open several random Help pages and make sure that links in the Help pages work correctly.

7. Odstranite pisarniški paket

   Odstranitev je mogoče izvesti uspešno.

Release Sanity scenario in TCM vs. Sanity check described here

There is also a scenario in TCM (http://www.sunvirtuallab.com) that can be used for sanity testing. That one is more time-demanding than the steps described above - currently it contains 28 testcases. The TCM scenario is more suitable for testing Release Candidate builds, the steps described here are to be used for example for a quick check of interim L10n builds created between two translation handoffs (to make sure that strings from the first handoff were correctly imported into the builds).