Caio Tiago Oliveira wrote: > >>the OpenOffice.org QA project has things like QATrack, > >>QUASTe, and TCM - but I wonder which of those pass the test of "we > >>really need it > > > >I actually believe that these are fundamental tools to assess quality of > >a build, and that insufficient testing could mean that LibreOffice is > >doomed to be "the nicer but more buggy brother of OOo" forever in the > >public opinion. > > Most of my friends already say OOo is too buggy. That is mainly due > to the longstanding bugs of the past and some old crashes, even > though we still with some annoying longstanding bugs. > > That said, I strongly agreed with you here, that we should avoid > shipping with severe bugs. > > VLC TestTool is a great tool to assure the quality of the branches > and releases. It helps avoiding regressions and makes the repetitive > tasks for us. > Hi Caio, all,
yeah, I think you nicely sum it up - so the tools mentioned are no silver bullets, they don't per se give you a quality release. That's why I asked what we'd _really_ need - it means striking a balance between effort to set things up, or even recode them, providing QA volunteers coming from OOo an effective work environment (there's a certain amount of "but we're used to that tool!" mentality to cater for) - and, I think that's the great opportunity - the chance to honestly look at the process, make it lean, effective - and fun to work with. > As far as I know, setting up QATrack for us is easy and Per said he > only needs a server. That's useful and easy to set up and use, so > it's a must. > Cool - so I had folks from France and Brazil offering hardware, let me see if we can connect you. Cheers, -- Thorsten -- To unsubscribe, send an empty e-mail to [email protected] All messages you send to this list will be publicly archived and cannot be deleted. List archives are available at http://www.documentfoundation.org/lists/discuss/
