Hi Thorsten, Thorsten Ziehm wrote: > Hi Sophie, > > sorry, when I was so misunderstanding. I do not want to stop testing in > the NLC. I never wrote this, I hope :-) Therefore I do not understand > your summary.
I think that there is something that you do not get in the community and I'll try again to explain it. > > Currently the test cases in TCM has a different part of quality > assurance on the product as the test cases, which you can find at the > applications areas on qa.openoffice.org. This doesn't mean, that your > testing isn't needed. It is important for the localized builds. We need > the testing on localization and translation by native speakers. Rafaella > explained TCM in more details. Yes but as you said, testing over and over the same GUI or OLH parts is useless, hence my first message to propose new test cases based on the new functionalities we have localized over the last weeks. The list you have provided on the wiki is helping, but it's not enough (imho) because we need to know what to display (menu, help, errors message, etc...) during our tests without wasting our resources. > > My Vision is, that we have OOo QA teams (independent where he is located > or if he is from Sun or not) which do functional testing more than now. > Testing bug fixes on CWS/Master, testing new feature on CWS/Master, > close verify issues on Master etc. So the general QA work should be done > more than now outside the Sun QA team. This is needed because of the > mass of new implementations. It increased the last years. Ok, I completely agree. With the new release model/process, an effort has to be done to advertise more widely dev snapshots and get feedback much earlier than on the past years. > The NLC are still needed and they are important for assure the quality > of the localization. They are also very welcome in the application > teams, to check the functionality early in different languages and to > find out, where a TCM test is needed for all other localization teams. > But in this teams to write and read English is important to work in an > international group. This is where you misunderstand our role, and I'll try to explain myself better. The NLC is a very very large part of the community. Inside you'll find users, contributors and developers. For the first of them, they don't need to speak English at all, but for the last, speaking English (and sometime German to read code comments ;) is mandatory. But contributors are in between, may be they are not the more numerous part compared to the users, but they are there and it is our force. Would you miss their contributions because they have to speak English and are not able to do so ? My opinion here is that if you put an interface (might be an ALI ;-) between your project and the NLC which is able to speak to both and advertise your needs, you will find a lot of hands to help you. NLC leads and their contributors who are able to speak English are here to bring this interface. It will give some extra efforts or work, but at the end, your testers will be multiplied by 3, 6, 10 or... What is your choice ? Mine is to give it a try and find the good way to bring the information and the process to both and not only put the things in English on a site and wait for those who are able to contribute in the good language. Anytime you will ignore the NLC, any time you will deny your project of great resources. And be sure that we are aware of the increase of the QA needs, when there is 4, 6 or 7 RCs, we all know that something wrong is going on and we feel concerned too. > > So again, I do not want to stop testing in the L10N teams. I do not want > to stop testing with TCM test cases. And I hope you would like us to work together on a solution that will bring more contributors to your teams. Most of them are able to test an English release and will understand the work needed but won't be able to report a bug or express them self in English, at least at the beginning. Kind regards Sophie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
