Table of Contents
This chapter introduces translation tests which are based on the use of the
Glossary. The aim of those tests is to check that all terms from the glossary
are translated and that they are also well translated.
This paragraph introduces the tools which are needed to perform the Glossary
tests. Glossary tests are based on reports which can be generated by the glossary:
English glossary terms report is helpful for all the glossary tests. It
can be displayed or printed here:
You will need a user and login, as defined in the document How to Translate
[RD]. When you are
on this page, type "en" in the language field to filter the list and display
only the English terms of the glossary.
Local glossary terms report is helpful to test the local translation of the
glossary. It can be displayed or printed here:
When you are on this page, type the abbreviation of your local language in the
language field to filter the list and display only the local language terms of
the glossary. For instance, if you want to see only French terms, type "fr" in
the language field.
The glossary tests are designed to check the quality and the completeness of
the glossary. This paragraph introduces the 3 tests that will be helpful to test
This first test will help detecting duplicate glossary entries (ie. same
reference, same business field, different Title). This test is partly automated:
This test is considered as passed whenever there are no duplicate entries.
This second tests helps choosing precise terms in each business field. This test
is performed by people who are skilled in the business field.
The third Glossary test helps translating all terms in a local language. It is
the first test which requires to compare English original entries with translated
entries. This test must be performed by a person in the business field and in
the local language. Passing this test proves that both English and local
(ex. French) Glossaries are good enough.
This chapter introduces tests which are related to the ERP5 application itself.
Application tests in a given business field must be performed after passing
Glossary tests in the same business field. A translation of an ERP5 application
is considered as “good” once all application tests for all involved business
fields are passed.
In order to perform the Application tests, some tools will be needed. This
paragraph consists in a list of those tools. You will need two different tools
that are a PO File and ERP5 Test Cases.
PO File gathers all the terms of the User Interface, and will be generated by
the server whenever needed. This file is used in the Completion Test. In order
to understand how to generate a PO File, refer to How to Translate
ERP5 Test Cases: Those test cases are reachable from the Test Case
module of Nexedi ERP5. You will find a Test Case for each ERP5 Express module
to be tested, under the name "QA for the translation of ERP5 xxx module".
This paragraph introduces the 3 application tests which must be performed at
the level of the application itself:
The Application Completeness Test checks that all the terms of the PO File
are translated. Once this test has been passed successfully, we are sure that
all GUI messages are translated, and thanks to the previous Glossary Tests,
that they are translated properly as long as the translator who translated the
.po file followed the choices made in the glossary.
The Application Internal Test helps developers of an application to check that
the translation is usable, that there are no bad translations due to lack of
context/bad context, and that everything is translated. This test must be
performed before releasing the application to the client or to the public.
This test is really important because it is the only way to make sure that
all terms embedded in the content PO file are all translated, and all terms
are properly translated in their context.
This test must be performed on a module per module basis. This test requires
an ERP5 test instance which can be provided by on demand by requesting it at
This test also requires access to Test Cases in ERP5 KM1.
The Application Internal Test helps users or clients provided their views on the
translation and increase its usability before it is released at large. This test
must be performed only once all the previous tests are successful. Consider a
period of 2 weeks at least to conduct such a test.
This chapter explains how to report translation errors after testing translation
with each of the 5 tests.
Until a better solution is available, the current reporting procedure consists
of using the erp5-dev mailing list to report translation errors.
The current reporting procedure does not provide scalability and must be replaced
by a more manageable one.
The future reporting procedure is based on the "Bug", "Test Case" and "Test Report"
modules present in ERP5 KM, in erp5_forge and erp5_consulting. The preferred
reporting procedure is the use of the "Test Case" and
"Test Report" modules. By using those test modules, it is possible to track
the evolution of the quality of the translation over time. It is also possible
to distribute tests and track their progress over a team of translators and users.
If you wish to participate to the beta-testing of both modules, please request
an account via the
For minor errors in the translation procedure, it is acceptable to report them
through the "Bug Module" as a "Translation Error". Such reports are useful, yet
less useful than performing full Test Reports.