You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2012/02/29 15:18:21 UTC
Calling all volunteers: It is time to test
As we approach the first Release Candidate for Apache OpenOffice 3.4,
it would be wonderful if we could have some more volunteers testing
the latest dev snapshots builds. Following is some information on what
this requires, and how you can help.
First, if you have never tested a pre-release product before, know
that bugs are expected. That is the purpose of testing, to find bugs
so they can be fixed. Bugs could range from UI glitches, to incorrect
formatting to crashes or even data corruption. So you probably don't
want to use a test build for mission-critical tasks. Of course, I
assume you have already backed up your important documents. You do
have backups, right? Ideally you can do your testing on a separate
machine from your main work machine, so if something goes wrong you
will not interfere with your other work.
The above are all sensible precautions when testing any pre-release
software product.
If you are ready to test, you can download the latest developer
snapshot build from this page:
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
We could use help verifying the install in all real-world scenarios,
on clean OS installs, as upgrades to previous versions of OOo and as
installs on machines where LibreOffice or Symphony are already
installed.
Once you have installed, launch OpenOffice and look at the Help/About
box. If the revision shown there matches the build you installed
(e..g, "r1293550") then the install was a success. Please send a short
note to the ooo-dev@incubator.apache.org telling us what platform and
scenario you installed (fresh install, upgrade, install next to
LibreOffice, etc.). This will help us understand what scenarios have
already been attempted and which have not.
After you have installed, there are three approaches to testing, of
increasing degrees of formality:
1) Just use the dev snapshot for your ordinary work, doing your
ordinary tasks. When you observe a bug, submit a report on this to
Bugzilla.
2) Self-directed testing. Pick an area of the product that you
understand well, like printing or text formatting, or slide show
transitions. Spend an hour or two trying to exercise that feature in
all its variations. If there is a dialog box, try manipulating all of
its values. If it is a formatting option, create a document that uses
all variations. Try to break it. Try to think like a bug.
A special area that could use attention is version compatibility.
Take all of your OpenOffice.org 3.3 documents and open them up on AOO
3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
for opening Microsoft Office documents. Are there any regressions,
e.g., things that worked in 3.3 but now break in 3.4? Try it in the
other direction as well. If you create a document in AOO 3.4, can it
be read correctly in OOo 3.3? Did we do anything that breaks
backwards compatibility?
Another special area is to verify the translations. Install a
multi-language install or a language pack and check the translation
for completeness and accuracy. If it looks good, please send a note
to the list, so we know it has already been verified. If there are
bugs, please enter into Bugzilla.
3) Cover test cases from the test plan
A 3.4 test plan is on the wiki here:
http://wiki.services.openoffice.org/wiki/QA/TestCases/
Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
Look for an area that has not been tested, test it, and upload your results.
In all cases, if you find bugs, report them in Bugzilla:
https://issues.apache.org/ooo/
We can also use help re-testing bugs that have been marked as fixed,
and confirming/reproducing newly reported bugs. If you want to help
in Bugzilla, sign up for an account and respond to this note and ask
for your ID to be put in the "qa-team" group, so you will have
expanded permissions to edit issues.
Regards,
-Rob
Re: Calling all volunteers: It is time to test
Posted by Detlef Nannen <de...@googlemail.com>.
Hi all,
I am looking for this "test run" for OpenOffice.org (go there, do this,
write the result in column xxx, etc.).
Is there a German-speaking community, which is coordinating this for the
local version?
Currently I have installed version 3.3 on an old Thinkpad with Lubuntu,
and try the 3.4-dev version on a Windows Vista-based PC.
-
Sincerely,
Detlef Nannen
Am 29.02.2012 15:18, schrieb Rob Weir:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by Kay Schenk <ka...@gmail.com>.
On Wed, Feb 29, 2012 at 6:18 AM, Rob Weir <ro...@apache.org> wrote:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your
> results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
>
Installed the 32-bit Linux last week and all good!
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell
Re: Calling all volunteers: It is time to test
Posted by Maho NAKATA <ma...@apache.org>.
Hi Rob
Is it also possible to paste it to the blog?
just paste ... nothing more effort than rewriting, or is it a marketing matter?
thanks
Nakata Maho
From: Rob Weir <ro...@apache.org>
Subject: Calling all volunteers: It is time to test
Date: Wed, 29 Feb 2012 09:18:21 -0500
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
>
Re: Calling all volunteers: It is time to test
Posted by "Robert K. Tompsett N8JUQ" <n8...@arrl.net>.
On 2/29/2012 10:15, Robert K. Tompsett N8JUQ wrote:
> On 2/29/2012 09:18, Rob Weir wrote:
>> As we approach the first Release Candidate for Apache OpenOffice 3.4,
>> it would be wonderful if we could have some more volunteers testing
>> the latest dev snapshots builds. Following is some information on what
>> this requires, and how you can help.
>>
>> First, if you have never tested a pre-release product before, know
>> that bugs are expected. That is the purpose of testing, to find bugs
>> so they can be fixed. Bugs could range from UI glitches, to incorrect
>> formatting to crashes or even data corruption. So you probably don't
>> want to use a test build for mission-critical tasks. Of course, I
>> assume you have already backed up your important documents. You do
>> have backups, right? Ideally you can do your testing on a separate
>> machine from your main work machine, so if something goes wrong you
>> will not interfere with your other work.
>>
>> The above are all sensible precautions when testing any pre-release
>> software product.
>>
>> If you are ready to test, you can download the latest developer
>> snapshot build from this page:
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>>
>> We could use help verifying the install in all real-world scenarios,
>> on clean OS installs, as upgrades to previous versions of OOo and as
>> installs on machines where LibreOffice or Symphony are already
>> installed.
>>
>> Once you have installed, launch OpenOffice and look at the Help/About
>> box. If the revision shown there matches the build you installed
>> (e..g, "r1293550") then the install was a success. Please send a short
>> note to theooo-dev@incubator.apache.org telling us what platform and
>> scenario you installed (fresh install, upgrade, install next to
>> LibreOffice, etc.). This will help us understand what scenarios have
>> already been attempted and which have not.
>>
>> After you have installed, there are three approaches to testing, of
>> increasing degrees of formality:
>>
>> 1) Just use the dev snapshot for your ordinary work, doing your
>> ordinary tasks. When you observe a bug, submit a report on this to
>> Bugzilla.
>>
>> 2) Self-directed testing. Pick an area of the product that you
>> understand well, like printing or text formatting, or slide show
>> transitions. Spend an hour or two trying to exercise that feature in
>> all its variations. If there is a dialog box, try manipulating all of
>> its values. If it is a formatting option, create a document that uses
>> all variations. Try to break it. Try to think like a bug.
>>
>> A special area that could use attention is version compatibility.
>> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
>> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
>> for opening Microsoft Office documents. Are there any regressions,
>> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
>> other direction as well. If you create a document in AOO 3.4, can it
>> be read correctly in OOo 3.3? Did we do anything that breaks
>> backwards compatibility?
>>
>> Another special area is to verify the translations. Install a
>> multi-language install or a language pack and check the translation
>> for completeness and accuracy. If it looks good, please send a note
>> to the list, so we know it has already been verified. If there are
>> bugs, please enter into Bugzilla.
>>
>> 3) Cover test cases from the test plan
>>
>> A 3.4 test plan is on the wiki here:
>> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>>
>> Results are here:http://wiki.services.openoffice.org/wiki/QA/TestResults
>>
>> Look for an area that has not been tested, test it, and upload your results.
>>
>> In all cases, if you find bugs, report them in Bugzilla:
>>
>> https://issues.apache.org/ooo/
>>
>> We can also use help re-testing bugs that have been marked as fixed,
>> and confirming/reproducing newly reported bugs. If you want to help
>> in Bugzilla, sign up for an account and respond to this note and ask
>> for your ID to be put in the "qa-team" group, so you will have
>> expanded permissions to edit issues.
>>
>> Regards,
>>
>> -Rob
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:ooo-users-unsubscribe@incubator.apache.org
>> For additional commands, e-mail:ooo-users-help@incubator.apache.org
>>
> Whatever you do, don't screw it up! Ooo has to be 99.999999999%
> comparable, and compatible to that Microsoft Office thing.
>
> --
>
>
> *Robert K. Tompsett N8JUQ*
>
> SSgt. USAF/ MIANG, TACP ROMAD (Ret.)
>
> ICBM 42°14'03"N, 085°53'30"W - Grid EN72bf
>
> "It's inaccurate to say that I hate everything. I am strongly in favor
> of common sense, common honesty, and common decency. This makes me
> forever ineligible for any public office."
>
> Click for Paw Paw, Michigan Forecast
> <http://www.wunderground.com/cgi-bin/findweather/getForecast?query=zmw:49079.1.99999&bannertypeclick=wu_bluestripes>
>
When might you change the logo from Oracle to Apache on the quick start?
--
*Robert K. Tompsett N8JUQ*
SSgt. USAF/ MIANG, TACP ROMAD (Ret.)
ICBM 42°14'03"N, 085°53'30"W - Grid EN72bf
"It's inaccurate to say that I hate everything. I am strongly in favor
of common sense, common honesty, and common decency. This makes me
forever ineligible for any public office."
Click for Paw Paw, Michigan Forecast
<http://www.wunderground.com/cgi-bin/findweather/getForecast?query=zmw:49079.1.99999&bannertypeclick=wu_bluestripes>
Re: Calling all volunteers: It is time to test
Posted by "Robert K. Tompsett N8JUQ" <n8...@arrl.net>.
On 2/29/2012 09:18, Rob Weir wrote:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
> For additional commands, e-mail: ooo-users-help@incubator.apache.org
>
Whatever you do, don't screw it up! Ooo has to be 99.999999999%
comparable, and compatible to that Microsoft Office thing.
--
*Robert K. Tompsett N8JUQ*
SSgt. USAF/ MIANG, TACP ROMAD (Ret.)
ICBM 42°14'03"N, 085°53'30"W - Grid EN72bf
"It's inaccurate to say that I hate everything. I am strongly in favor
of common sense, common honesty, and common decency. This makes me
forever ineligible for any public office."
Click for Paw Paw, Michigan Forecast
<http://www.wunderground.com/cgi-bin/findweather/getForecast?query=zmw:49079.1.99999&bannertypeclick=wu_bluestripes>
Re: Calling all volunteers: It is time to test
Posted by NoOp <gl...@sbcglobal.net>.
On 02/29/2012 11:49 AM, drew jensen wrote:
...
>
> Installed on Ubuntu 11.04 alongside LibO 3.5 (64bit), OpenJDK 1.6 - no
> problems.
Drew, can you test something for me (your linux version):
Open top:
$ top
and observe the cpu usage.
Now open AOO 3.4.0 to the standard menu screen
(/opt/ooo-dev3/program/soffice or /opt/openoffice3/program/soffice
depending on which version of r1293550 you downloaded) and open a small
database .odt (I just used my SeaMonkey Address Book - works very well
BTW). Now close the database using 'File|Close'. Once back at the
standard menu screen check 'top' and see what your soffice.bin cpu usage
is. Mine shows 40-45% (both versions), and continues that way as long as
AOO is open.
Note: tested both AOO 3.4.0 versions (see my other posts in this
thread), and tested on two different machines w/11.04 and 10.10 - 32bit.
...
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by drew jensen <dr...@gmail.com>.
On Wed, 2012-02-29 at 09:18 -0500, Rob Weir wrote:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
Installed on Ubuntu 11.04 alongside LibO 3.5 (64bit), OpenJDK 1.6 - no
problems.
Installed a few extensions - mixed results
- Report Builder - install good, a couple of quick reports, good.
- a couple of addon, custom spell checkers - all good
- PostgreSQL SDB extension - failure to load, missing file.
- Template Changer - hangs AOO during install (twice)
- MySQL - no reason to try (that is a huge hit guys)
Will go ahead and do this all on Vista (32Bit) w/ existing 3.3 later
today.
So - looking at the test page I guess the Bases test are mine to
add..and I'll start when I have the Vista VM running.. :-/ how ironic
for that to be the case today.. (sorry comment not likely to be
understood by many here, but a few may)
Otherwise - I suppose bugzilla will also be in order here and there.
Good job by the way...
//drew
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
Re: Calling all volunteers: It is time to test
Posted by Josef Latt <Jo...@gmx.net>.
Hi,
Am 29.02.2012 21:49, schrieb NoOp:
> On 02/29/2012 11:43 AM, NoOp wrote:
> ...
>> Which version are you looking for feedback/testing on?
>>
>> http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo-Dev_OOO340m1_Linux_x86_install-deb_en-US.tar.gz
>> or
>> http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo_3.4.0_Linux_x86_install-deb_en-US.tar.gz
No language packs for OOo_3.4.0.
Greetings
--
PGP Schlüssel: 311D1055
http://keyserver.pgp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by NoOp <gl...@sbcglobal.net>.
On 02/29/2012 11:43 AM, NoOp wrote:
...
> Which version are you looking for feedback/testing on?
>
> http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo-Dev_OOO340m1_Linux_x86_install-deb_en-US.tar.gz
> or
> http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo_3.4.0_Linux_x86_install-deb_en-US.tar.gz
>
> I see the "The r***** links provides full normal install sets instead of
> development builds to test upgrades and system integration." However I
> suspect that some will download one, and some will download the other.
> So I think it helpful if you clarify as to which one you want
> feedback/testing on - particularly since they are ~138MB each.
Just to add to that:
$ md5sum OOo_3.4.0_Linux_x86_install-deb_en-US.tar.gz
421f9ea3b95217a15bae9bbb7ccaa4a7
OOo_3.4.0_Linux_x86_install-deb_en-US.tar.gz
Size: 144872066
Help|About OpenOffice.org - identifies as:
OpenOffice.org 3.4.0
OOO340m1 (Build:9586)
2012-02-27 07:43:04 (Mon, 27 Feb 2012) - Rev. 1293550
Installs in: /opt/openoffice.org3/
$ md5sum OOo-Dev_OOO340m1_Linux_x86_install-deb_en-US.tar.gz
d194d29cc03f238a6572601f757c6407
OOo-Dev_OOO340m1_Linux_x86_install-deb_en-US.tar.gz
Size: 144375254
Help|About OOo-dev - identifies as:
OpenOffice.org 3.4.0
OOO340m1 (Build:9586)
2012-02-27 07:43:04 (Mon, 27 Feb 2012) - Rev. 1293550
Installs in: /opt/ooo-dev3/
So they are different files (size & md5sum), but they both identify as
the exact same build on the Help|About screen. Which means that
'testers' will be reporting that they have the same versions installed
regardless of which one they actually downloaded and installed. The only
difference in the versionrc files are the UpdateID's (respectively):
UpdateID=OpenOffice.org_3_en-US
UpdateID=OOo-dev_3_en-US
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by NoOp <gl...@sbcglobal.net>.
On 02/29/2012 06:18 AM, Rob Weir wrote:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
...
Which version are you looking for feedback/testing on?
http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo-Dev_OOO340m1_Linux_x86_install-deb_en-US.tar.gz
or
http://people.apache.org/~arielch/packages/r1293550/linux_x86/OOo_3.4.0_Linux_x86_install-deb_en-US.tar.gz
I see the "The r***** links provides full normal install sets instead of
development builds to test upgrades and system integration." However I
suspect that some will download one, and some will download the other.
So I think it helpful if you clarify as to which one you want
feedback/testing on - particularly since they are ~138MB each.
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by RGB ES <rg...@gmail.com>.
2012/3/1 Pedro Giffuni <pf...@apache.org>:
> Hi;
>
> On 02/29/12 18:12, RGB ES wrote:
>>
>> ...
>>
>> On Linux 64 bits, loaded a ~150 page Writer document with ~50
>> pictures, 40 of them captioned, ~100 Math objects, all with Linux
>> Libertine G and Linux Biolinum G fonts with lots of Graphite font
>> features enabled. No problem.
>>
>> Then opened a 3 MiB, 320 page Writer document with ~80 captioned
>> pictures, tons of cross references, smart font features enabled, five
>> page styles... no problem!
>>
>> Looking at the Spanish translation, the new strings are not translated
>> ("Math baseline alignment", the new ColorPicker...) but that's
>> obvious. I can see the following problem (already mentioned on another
>> thread):
>>
>> It seems there is a naming problem on the icon sets for Spanish
>> localization, were I have
>>
>> Galaxia
>> Alto contraste
>> Industrial
>> Cristal<---- The problem
>> Tango
>>
>> If I switch to English UI, I have
>>
>> Galaxy
>> High Contrast
>> Industrial
>> Tango
>> Classic
>>
>> On the Spanish localization, "Cristal" displays Tango icons while
>> "Tango" displays Classic icons.
>
>
> Using OpenGrok I couldn't find "Cristal" anywhere. If your can
> find it anywhere it's just a matter of removing it ;-).
>
> Can you please confirm if the industrial icons work?
>
> Pedro.
>
No problem with Industrial, Hight Contrast nor Galaxy.
Re: Calling all volunteers: It is time to test
Posted by Pedro Giffuni <pf...@apache.org>.
Hi;
On 02/29/12 18:12, RGB ES wrote:
> ...
> On Linux 64 bits, loaded a ~150 page Writer document with ~50
> pictures, 40 of them captioned, ~100 Math objects, all with Linux
> Libertine G and Linux Biolinum G fonts with lots of Graphite font
> features enabled. No problem.
>
> Then opened a 3 MiB, 320 page Writer document with ~80 captioned
> pictures, tons of cross references, smart font features enabled, five
> page styles... no problem!
>
> Looking at the Spanish translation, the new strings are not translated
> ("Math baseline alignment", the new ColorPicker...) but that's
> obvious. I can see the following problem (already mentioned on another
> thread):
>
> It seems there is a naming problem on the icon sets for Spanish
> localization, were I have
>
> Galaxia
> Alto contraste
> Industrial
> Cristal<---- The problem
> Tango
>
> If I switch to English UI, I have
>
> Galaxy
> High Contrast
> Industrial
> Tango
> Classic
>
> On the Spanish localization, "Cristal" displays Tango icons while
> "Tango" displays Classic icons.
Using OpenGrok I couldn't find "Cristal" anywhere. If your can
find it anywhere it's just a matter of removing it ;-).
Can you please confirm if the industrial icons work?
Pedro.
Re: Calling all volunteers: It is time to test
Posted by RGB ES <rg...@gmail.com>.
2012/2/29 Rob Weir <ro...@apache.org>:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
On Linux 64 bits, loaded a ~150 page Writer document with ~50
pictures, 40 of them captioned, ~100 Math objects, all with Linux
Libertine G and Linux Biolinum G fonts with lots of Graphite font
features enabled. No problem.
Then opened a 3 MiB, 320 page Writer document with ~80 captioned
pictures, tons of cross references, smart font features enabled, five
page styles... no problem!
Looking at the Spanish translation, the new strings are not translated
("Math baseline alignment", the new ColorPicker...) but that's
obvious. I can see the following problem (already mentioned on another
thread):
It seems there is a naming problem on the icon sets for Spanish
localization, were I have
Galaxia
Alto contraste
Industrial
Cristal <---- The problem
Tango
If I switch to English UI, I have
Galaxy
High Contrast
Industrial
Tango
Classic
On the Spanish localization, "Cristal" displays Tango icons while
"Tango" displays Classic icons.
Finally, two old translation problems persists: issues 112063 and 118660
Ricardo
Re: Calling all volunteers: It is time to test
Posted by drew jensen <dr...@gmail.com>.
On Wed, 2012-02-29 at 09:18 -0500, Rob Weir wrote:
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
Installed on Ubuntu 11.04 alongside LibO 3.5 (64bit), OpenJDK 1.6 - no
problems.
Installed a few extensions - mixed results
- Report Builder - install good, a couple of quick reports, good.
- a couple of addon, custom spell checkers - all good
- PostgreSQL SDB extension - failure to load, missing file.
- Template Changer - hangs AOO during install (twice)
- MySQL - no reason to try (that is a huge hit guys)
Will go ahead and do this all on Vista (32Bit) w/ existing 3.3 later
today.
So - looking at the test page I guess the Bases test are mine to
add..and I'll start when I have the Vista VM running.. :-/ how ironic
for that to be the case today.. (sorry comment not likely to be
understood by many here, but a few may)
Otherwise - I suppose bugzilla will also be in order here and there.
Good job by the way...
//drew
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org
Re: Calling all volunteers: It is time to test
Posted by Maho NAKATA <ma...@apache.org>.
Hi Rob
Is it also possible to paste it to the blog?
just paste ... nothing more effort than rewriting, or is it a marketing matter?
thanks
Nakata Maho
From: Rob Weir <ro...@apache.org>
Subject: Calling all volunteers: It is time to test
Date: Wed, 29 Feb 2012 09:18:21 -0500
> As we approach the first Release Candidate for Apache OpenOffice 3.4,
> it would be wonderful if we could have some more volunteers testing
> the latest dev snapshots builds. Following is some information on what
> this requires, and how you can help.
>
> First, if you have never tested a pre-release product before, know
> that bugs are expected. That is the purpose of testing, to find bugs
> so they can be fixed. Bugs could range from UI glitches, to incorrect
> formatting to crashes or even data corruption. So you probably don't
> want to use a test build for mission-critical tasks. Of course, I
> assume you have already backed up your important documents. You do
> have backups, right? Ideally you can do your testing on a separate
> machine from your main work machine, so if something goes wrong you
> will not interfere with your other work.
>
> The above are all sensible precautions when testing any pre-release
> software product.
>
> If you are ready to test, you can download the latest developer
> snapshot build from this page:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4+Unofficial+Developer+Snapshots
>
> We could use help verifying the install in all real-world scenarios,
> on clean OS installs, as upgrades to previous versions of OOo and as
> installs on machines where LibreOffice or Symphony are already
> installed.
>
> Once you have installed, launch OpenOffice and look at the Help/About
> box. If the revision shown there matches the build you installed
> (e..g, "r1293550") then the install was a success. Please send a short
> note to the ooo-dev@incubator.apache.org telling us what platform and
> scenario you installed (fresh install, upgrade, install next to
> LibreOffice, etc.). This will help us understand what scenarios have
> already been attempted and which have not.
>
> After you have installed, there are three approaches to testing, of
> increasing degrees of formality:
>
> 1) Just use the dev snapshot for your ordinary work, doing your
> ordinary tasks. When you observe a bug, submit a report on this to
> Bugzilla.
>
> 2) Self-directed testing. Pick an area of the product that you
> understand well, like printing or text formatting, or slide show
> transitions. Spend an hour or two trying to exercise that feature in
> all its variations. If there is a dialog box, try manipulating all of
> its values. If it is a formatting option, create a document that uses
> all variations. Try to break it. Try to think like a bug.
>
> A special area that could use attention is version compatibility.
> Take all of your OpenOffice.org 3.3 documents and open them up on AOO
> 3.4. Any errors? Formatting issues? Crashes? Missing data? Ditto
> for opening Microsoft Office documents. Are there any regressions,
> e.g., things that worked in 3.3 but now break in 3.4? Try it in the
> other direction as well. If you create a document in AOO 3.4, can it
> be read correctly in OOo 3.3? Did we do anything that breaks
> backwards compatibility?
>
> Another special area is to verify the translations. Install a
> multi-language install or a language pack and check the translation
> for completeness and accuracy. If it looks good, please send a note
> to the list, so we know it has already been verified. If there are
> bugs, please enter into Bugzilla.
>
> 3) Cover test cases from the test plan
>
> A 3.4 test plan is on the wiki here:
> http://wiki.services.openoffice.org/wiki/QA/TestCases/
>
> Results are here: http://wiki.services.openoffice.org/wiki/QA/TestResults
>
> Look for an area that has not been tested, test it, and upload your results.
>
> In all cases, if you find bugs, report them in Bugzilla:
>
> https://issues.apache.org/ooo/
>
> We can also use help re-testing bugs that have been marked as fixed,
> and confirming/reproducing newly reported bugs. If you want to help
> in Bugzilla, sign up for an account and respond to this note and ask
> for your ID to be put in the "qa-team" group, so you will have
> expanded permissions to edit issues.
>
> Regards,
>
> -Rob
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ooo-users-unsubscribe@incubator.apache.org
For additional commands, e-mail: ooo-users-help@incubator.apache.org