Georges, Thanks for your contribution.
I have completed task 121402. Now you can find the test plan called "AOO 3.5 Milestone Regression". Please start this regression test. Thanks On Tue, Nov 27, 2012 at 4:57 PM, Georges Bolssens <[email protected]>wrote: > I added my name to the comment section of bug ID 121403. > > I can test on Win7 or MacOSX. From your experience I think you will have an > idea of where the most volunteers will want to test, so you can give me the > 10 test cases on the other platform for the best distribution of manpower. > > > On Tue, Nov 27, 2012 at 3:25 AM, Ji Yan <[email protected]> wrote: > > > There is only one milestone build which is AOO 3.5. So I think what QA > > volunteers can do is testing this milestone build. Once we start 4.0 > > feature developing, QA team will follow test plan to do relative test. > > > > > > On Tue, Nov 27, 2012 at 3:35 AM, Rob Weir <[email protected]> wrote: > > > > > On Mon, Nov 26, 2012 at 2:30 AM, Ji Yan <[email protected]> wrote: > > > > Hi all, > > > > > > > > AOO 3.5 milestone build is ready for awhile and now we have more > QA > > > > volunteer joined. It's time to form a regression test to ensure this > > > > milestone build quality. > > > > > > > > > > The most-recent discussions on Dev list talk about 4.0 being the next > > > major release, not 3.4. > > > > > > I assume your task will be the same either way, yes? We still need a > > > regression test suite. > > > > > > -Rob > > > > > > > I created a QA task [1] for test plan preparing in TestLink and > > another > > > > task[2] for regression test execution. > > > > > > > > I'm volunteer to take the first task[1]. Once the test plan ready, > > I'll > > > > let you know. > > > > > > > > If any volunteers wants help on this regression execution, please > add > > > > comments to task[2]. We need 10 volunteers for cases execution, > > everyone > > > > need to complete 10 cases. > > > > > > > > [1] https://issues.apache.org/ooo/show_bug.cgi?id=121402 > > > > [2] https://issues.apache.org/ooo/show_bug.cgi?id=121403 > > > > > > > > > > > > On Mon, Nov 26, 2012 at 2:07 PM, Ji Yan <[email protected]> wrote: > > > > > > > >> Li Feng, > > > >> > > > >> Thanks for your SVT report. According to your test result. I think > > we > > > >> can close following memory leak defects[1]. If no objection, I'll > > close > > > >> them. > > > >> > > > >> [1] > > > >> > > > > > > https://issues.apache.org/ooo/buglist.cgi?bug_id=120073%2C120050%2C120019%2C119997%2C120074%2C120021%2C120108%2C119992%2C120105%2C120079%2C120675%2C120040%2C116448%2C120106%2C113606%2C120028%2C120098%2C120038%2C120072%2C120077%2C119991&list_id=38828 > > > >> > > > >> > > > >> On Mon, Nov 26, 2012 at 1:19 PM, Li Feng Wang < > > [email protected] > > > >wrote: > > > >> > > > >>> Hi, all > > > >>> > > > >>> Last week, I run SVT cases on Windows 7 64bit with AOO3.5 > > > >>> r1400866（r1400866 is the first dev snapshot build on AOO3.5) > > > >>> > > > >>> Build: > > > >>> > > > >>> > > > > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds > > > >>> > > > >>> SVT introduction and scenario description: > > > >>> http://wiki.openoffice.org/wiki/QA/SVT > > > >>> 100 iterations, 41 Scenarios, run 24hours. > > > >>> > > > >>> SVT Report on r1400866: > > > >>> There is no obvious upgrade and downgrade compare with r1397404. > Just > > > one > > > >>> problem still exist > > > https://issues.apache.org/ooo/show_bug.cgi?id=121401. > > > >>> Report detail: > > > >>> http://wiki.openoffice.org/wiki/QA/SVTReport/r1400866VSr1397404 > > > >>> > > > >>> ps: > > > >>> http://wiki.openoffice.org/wiki/QA/SVTReport is the link to > collect > > > all > > > >>> SVT > > > >>> report. > > > >>> > > > >>> Welcome comments! > > > >>> > > > >>> > > > >>> -- > > > >>> Best Wishes, LiFeng Wang > > > >>> > > > >> > > > >> > > > >> > > > >> -- > > > >> > > > >> > > > >> Thanks & Best Regards, Yan Ji > > > >> > > > >> > > > > > > > > > > > > -- > > > > > > > > > > > > Thanks & Best Regards, Yan Ji > > > > > > > > > > > -- > > > > > > Thanks & Best Regards, Yan Ji > > > -- Thanks & Best Regards, Yan Ji
