やっと見付けました。 "OOo release sanity" とはAndreはここで定義してます。
http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=6519 I'v created a new scenario in TCM, called "OOo release sanity". I'd like to use this as the absolut minimum of tests, that a build needs to pass to be approved for release. This should help in situations like we have with 2.0.3: - a series of RC's has already been tested - a small amount of stoppers needs to be fixed - running the full tests again would take a lot of time - running no tests at all would break our QA policy I'm not shure, what test cases should be put to the scenario. The current set is my first attemt .. and as always, at the one hand it seems not enough to be shure we have no bugs .. at the other it seem to be to many tests to be able to go through the scenario quickly. Comments are welcome (no problem, if they would take some time, I know, native lang teams are still busy with 2.0.3 testing). これについて少し勉強します。 -- NAKATA, Maho ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]