Hi Andre and Sophie, I looked at smoke tests and at a basic set of tests required for QA release of localized builds.
This is how I would approach both release testing and QA metrics for stability of build. This may have already been discussed or covered elsewhere. However, I rather repeat something if it may help me or the team learn, then continue working on this project with wrong assumptions. 1. Develop a matrix of standardized test files and standardized tests 1.1 To keep things simple, for each test file, I would have 3 levels of complexity: Simple, Complex, Very Complex. 1.1.1 For example, to test Writer, we could have the following test files: 1.1.1.1 Simple: A 10 page document where each page is written in a different language and has a simple database, html code, a small picture, basic page and document formatting. 1.1.1.1.1 The document can be set-up in such a way the any differences in format display are very noticable. The testers would have a set of actions to perform. For example: Open and save document, import it back. check to see that document has not changed, save in different format, etc. Build stability rating could then be assigned based on success of each test. The benefit of this approach is that it allows an objective evaluation of the build. There are different ways to calculate a stability rating. Before I get into that and other details, I would like to get comments on this suggestion. Best Regards Simon Rybalov > Hi Andre, all, > Andre Schnabel wrote: > > > Hi sophie, > > > > > >> > >> Not sure if it's feasible, but may be we could form a international QA > >> team with all languages mixed when we are testing a release for the > >> 3rd time, roughly : > > > > > > as we have to wait for rc3 for windows anyway .. and it makes no sense > > to release windows with i52869 fixed, but other platforms not ... we > > should share the work. > > Ok, a Solaris 10 bug has been corrected too, I've no testers on this > platform but it's i52936 > [...] > > > So > > > > - platform tests would be done for the english build, using testtool and > > full smoketests. > > +1 > > We would need volunteers to do those tests. Not everybody needs to run > > all the tests we can share the work. I'll try to invite people to > > participate in another mail (but not before sunday), we first should > > "collect" people from other lists (but we have enough volunteers here at > > the list) > > great ! > > > > - to approve a localized build, only a reduced set of the tests need to > > be passed > > I'd give this (as usual) to the hands of the native lang teams. But we > > should give a hint, what this "reduced set" would mean. Sophie: do you > > have such reduced test cases at hand? If not, I'll go over the > > smoketests within the next few days. > > No, I don't have that kind of test at hand, but I think that we should > keep a part of File Actions tests for localized build for example. > > > > Hope, this would help to ease the work and get more active people at the > > same time. > > +1 :) > > Kind regards > Sophie > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.338 / Virus Database: 267.10.1/64 - Release Date: 04/08/2005 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
