Hi Sophie,
sophie wrote:
Thorsten Ziehm wrote:
Hi Sophie,
sophie wrote:
Hi Thorsten, all
Thorsten Ziehm wrote:
[...]
Yes but in several cases we have seen that issues appears differently
depending on your local environement and/or the local you use in OOo.
And if we want to attract more testers on developer releases, we need to
have a clear process and know what tool to use. If we abandon the TCM,
ok, but the tests on the QA site are unusable for us.
The test case specifications are for testing the full functionality of
one feature. This can be done by everybody in the community. I do not
want to have this organized by the L10N teams. This should be organized
by the OOo QA Teamleads [1}. When each application team has enough
volunteers from different languages, you will have a better testing of a
feature as now. This is the plan/vision behind the restructure of the QA
project and sides on OOo.
From my experience, you will meet a lot of difficulties to attract
people on an English only site/list. This is also why we failed to find
testers on snapshots, the team is only 5 when it could be 30 for a RC
which is localized.
When I have one person from the French team, which is integrated in the
Writer QA team. He/she will learn many things, because he/she is in
direct contact with QA member at Sun and the developer. He/she could be
a multiplier in the French team to bring the knowledge he learned into
the team. To work with the developers and other QA members in the world
means to talk one language, here at this project - Englisch. This is the
philosophy of the QA application teams. To train some, which will be
multiplier.
The L10N teams should still concentrate on the language specific items
and these are the test cases which are in TCM. But the borderline
between L10N testing and general functionality testing will blur.
I do not want to change processes in the L10N-teams. But I think, it
is a point which should be discussed in the L10N project and now we
have a QA Lead for this, Jaqueline Rahemipour.
There is two different process that NLC are running : one for L10n,
another one for functionalities on a lot of different platforms. For
both, here are my questions :
Why different platforms? Isn't this a part of general functionality
testing? I know, there are perhaps specialties for one language on one
platform. But then it should be part of a TCM test case.
Volunteers use their own material :)
If you talk about releasing your language on different platforms, then
you are right. This has to be done still by the L10N team.
- what tests will we run for the TCM l10n testing for 2.3 ?
- what tests will we run the 2.3 rcx ?
I couldn't answer/decide this. _My opinion_ is, that sanity checks
should be enough for testing the build (now 2.3). When you will run test
cases on each RCs you should minimize the effort again. Perhaps run 2
automated test cases (first.bas / topten.bas) on the installations or
define a short test case which show you, that all applications are
installed correctly and not many more.
I understand but it seems that opinions differs a lot here.
If you want to do more, it is the choice of the L10N teams.
For me currently no tests are available for both, because none exists
for l10n, and none are translated (localized) for functionalities (sorry
if this effort does exist in the reloaded site, I didn't take the time
to dig in it).
The functionality tests should be translated. They are for members of
should => should be shouldn't !
the applications QA teams or for everybody who is interested in making
QA on OOo. As I wrote, this testing shouldn't be organized by the L10N
teams. The QA team leads are/will be responsible for this.
So we stop the testing of functionalities in our communities. Who will
give a go to the releases then ? the QA team leads ?
Does I say that the L10N teams should stop functionality testing? That
wasn't what I want to say. For releasing a product, you should
concentrate on the release. The testing on functionality has to be done
continuously on the developer snapshots or when a new feature is
integrated. If you start testing of new features, when all translation
is in, you have only 2-4 weeks until the release, this is too short for
such a big product like OOo.
I know, that we do not have such continuously work outside Sun. But this
should be a goal to maximize the quality of the community effort.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
