> One of them is, when can I say "GO" for OOo on platform that I am doing > localized QA on? > Is "OOo release sanity" test enough for this? As it says in its > description: "This scenario collects those test cases that need to be > passed before a release by a given build. This should be a absolute minimum > of test cases." Regards > Robert Ludvik
Hi Robert I can tell you how I work (danish qa), but that is just an opinion (and depends how many people can help with the test) I have the builds tested with the automation tool (not all of them, but some) to track errors. Then before release we make a 100% test of a build (all scenarios in the TCM-tool except release sanity) around the time for the first RC (that means right now for 2.1) And when we have a final release candidate we make the release sanity test. OK, what then if there are errors?? well, I have no clear answer. big bugs should be found before, and small bugs we solve with the documentation. we have some install packages to direct download (100% tested and only minor problems), and some "under development". /thomas roswall danish QA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
