Clytie Siddall wrote:
On 12/01/2007, at 2:14 AM, Lars D. Noodén wrote:
Please read http://blogs.sun.com/GullFOSS/entry/ooo_qa_reloaded1 if
you're interested into this.
It's interesting, I hope it results in something with a negligable
barrier for participation.
+1
I suggest, for the text (focus on actions):
___
Report Bugs
Submit new bugs, request new/enhanced features, or search for known
problems.
Manual Testing
Test your build and monitor your testing with our dedicated tools
Join QA Team
We need your ideas and experience! Come and help make OpenOffice.org
even better.
QA test cases for specific OpenOffice.org components:
Writer
create and modify text, rich text or html documents, including
formulæ (using Math)
Calc
layout spreadsheets, and output charts of many kinds (using Chart)
Graphics
manipulate images of all kinds with Draw, including presentations
(using Impress)
Database
organize, cross-reference and search for categorized information with
Base
Testing different aspects of OpenOffice.org
Framework
Work with the code structure, develop extensions and improve the API
Automation
Improve automatic processes, create better testing tools
Localization & Documentation
Translate and describe OpenOffice.org for your community
Special
If it doesn't fit in anywhere else, we're doing it! Come and find out
why.
Miscellaneous
General info, guidelines, statistics, mailing lists, all those handy
details
___
I had to guess the function of some of the sections, so sorry if I
got them wrong.
this part will contain the application dependent info for each section -
the concept is still in progress, but the principal structure is good
prooven for years in the sun qa team
It's also difficult to avoid repetition in the middle section,
because basically all four sub-sections are simply different angles
on the same thing.
yes, but i have maybe learned how to avoid the boring 'in this area -
here you can' :)
I suggest, for the text (focus on actions):
___
Report Bugs
Submit new bugs, request new/enhanced features, or search for known
problems.
Manual Testing
Test your build and monitor your testing with our dedicated tools
Join QA Team
We need your ideas and experience! Come and help make OpenOffice.org
even better.
QA test cases for specific OpenOffice.org components:
Writer
create and modify text, rich text or html documents, including formulæ
(using Math)
Calc
layout spreadsheets, and output charts of many kinds (using Chart)
Graphics
manipulate images of all kinds with Draw, including presentations
(using Impress)
Database
organize, cross-reference and search for categorized information with Base
Testing different aspects of OpenOffice.org
Framework
Work with the code structure, develop extensions and improve the API
Automation
Improve automatic processes, create better testing tools
Localization & Documentation
Translate and describe OpenOffice.org for your community
Special
If it doesn't fit in anywhere else, we're doing it! Come and find out why.
Miscellaneous
General info, guidelines, statistics, mailing lists, all those handy
details
___
in each section you get the qa relevant stuff for each application - so
the description should not be the commercial to use the single components
in principal it is a gate for similar things in divided projects, so
boring can also be good overviewable - your text is more interesting,
but i have to read more and at the end i am maybe confused or i realize
later that it is in principal the same - so in my boring version you get
the main info faster: 'similar content for different
applications/projects' and can faster go forward - maybe we need
anything in between?
So I suggest keeping that repeated text out of the sub-sections, as
I've done here, and specify only the differing information. That way,
someone wanting to specialize in one area of QA can choose their
component.
I hope this is useful. :)
yes, thank you
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm
Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
