Ubuntu Wiki

Introduction

The purpose of this page is to define a basic step by step process by which the regular language pack updates for stable releases can be tested before they are released.

Test the packages for your language following the instructions below, and update the following table to get your language pack released after testing.

For the language pack updates marked as "Full" please also take the extra steps decribed in the appropriate section below.

Test results Ubuntu 11.10 "Oneiric Ocelot"

• Signoff deadline: 30th of November 2011 1400 UTC

• Language pack version: 1:11.10+20111121

Test results Ubuntu 11.04 "Natty Narwhal"

• Signoff deadline: 4th of January 2012 1400 UTC

• Language pack version: 2011.11.29 or 2011.12.06

Workflow

1. Language Pack Creation - Language packs for stable releases are built and uploaded to the $RELEASE-proposed repository (e.g. lucid-proposed for Ubuntu Lucid Lynx (10.04)).

2. Call For Testing - An announcement is made on the ubuntu-translators mailing list. A one week period is given to testers to provide feedback for their language's language pack.

3. Community Testing - Testers follow the step-by-step tests for each application to check that the language packs do not contain errors or regressions.

4. Feedback and Sign-Off - After the testing has been done, testers provide feedback by filling in an entry to the table at the bottom of this document.

5. Language Pack Release - After the given period, the language packs having been tested and signed off (i.e. those on the list) are uploaded to -updates, where they will be made available to all users.

6. Release Announcement - An announcement of the upload is made in the ubuntu-translators list.

Requirements for testers

• Ubuntu Testers should have the -proposed repository enabled from Applications > Software Center > Edit > Software Sources... > Updates tab for the language pack of the particular release being tested. See Testing/EnableProposed for the details.

• Kubuntu Testers should have the -proposed repository enabled from...

Tests

We have currently no automated way of testing translations, neither to provide an exhaustive translation test coverage.

For this reason, the following simple test cases focus on making sure that you can still boot into a normal desktop and can upgrade to newer packages, so regressions in translations are not as fatal as completely ruining your system or precluding you from filing a bug or contacting someone for help.

1. Start the application and make sure it starts up normally.
2. Examine the main menus
   1. Are there regressions in the translations?
   2. Are the latest translations from Launchpad visible?
   3. Do you see unreadable characters?

Packages to test

Ubuntu Desktop

• Check all the Application/Places/System menu items

• Start the file browser (Places>Home Folder). Check your home folder location, the menu items and the side bar.

• Start Evolution, and check the menus and user interface
• Start the Web browser (Firefox): check out it starts, runs, its menus and help

• Start System -> Admin -> Software Updates: check out it runs and has sensible UI

(Note: see http://testcases.qa.ubuntu.com/Applications)

Kubuntu

Checking translations in Kubuntu and rationale why they should be tested

• Dolphin [tests KDE SC translations]
• Check "File" and "Edit" menus are translated [tests kde.po translations]
• Kontact [tests KDE PIM 4.4 backported translations]
• Rekonq [tests extragear translations]

• K-menu -> Applications [tests .desktop file translations]

• Systray->Message Indicator tooltip [tests ayatana translations]

• usb-creator-kde [tests Ubuntu pykde translations]

Extra tests for full updates

• To check translations of the ubuntu-docs package, start the application yelp using your language and browse the pages which appear.

  1. Are the latest translations from Launchpad visible?
  2. Do you see unreadable characters?

CategoryTranslations