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. > > 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. > >> 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 > 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 ? > >> BTW, there is an encoding issue for me in this page : >> http://tinyurl.com/yrxl36 > > I send a mail to Helge, and set the list on CC. thanks. Kind regards Sophie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
