From: Thorsten Ziehm <[EMAIL PROTECTED]> Subject: Re: [qa-dev] Testtool & TCM Date: Fri, 05 Jan 2007 10:05:33 +0100
> Hi Lars, > > perhaps I am wrong, but currently the 'sanity scenario' isn't defined > for OOo releases. This must be an action item for the QA project to JA uses 'sanity scenario' for QA process; namely ooo_releasetest with qatesttool for 2.0.4 and 2.1. http://www.openoffice.org/issues/show_bug.cgi?id=71978 http://www.openoffice.org/issues/show_bug.cgi?id=70335 You will find a lot of *res files attached to these issues. also, http://www.openoffice.org/nonav/issues/showattachment.cgi/40179/QA-JA-204.ods http://www.openoffice.org/nonav/issues/showattachment.cgi/41843/QA-JA-21.ods for summary. > define a clear picture, what QA have to be done before and at special > milestones (feature freeze, code freeze, first Release Candidate etc.). > A minimal scenario should be defined. If a QA project can and will make > more testing, it's on them. > > My proposal is the same what James wrote. If you have the resources > run the ooo_releasetest test set. But if a version should be released, > which are provided by Sun, a smaller test scenario is needed. Because > the main automated testing is and will be done by the Sun QA team. > The results for OOo2.1 were announced here : > http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7227 > > The result page is here : > http://wiki.services.openoffice.org/wiki/OOoRelease1AutomationTestMatrix Hm, I'd like to see the raw data as well. How we define `pass' or not. We are extensively doing QA tests, however, systematically fails for some tests. I suspect the difference between SO/OO, however, I'm not sure. -- NAKATA, Maho ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
