openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robw...@apache.org
Subject svn commit: r1409253 - /incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext
Date Wed, 14 Nov 2012 16:57:53 GMT
Author: robweir
Date: Wed Nov 14 16:57:52 2012
New Revision: 1409253

URL: http://svn.apache.org/viewvc?rev=1409253&view=rev
Log:
CMS commit to openofficeorg by robweir

Modified:
    incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext

Modified: incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext?rev=1409253&r1=1409252&r2=1409253&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/orientation/intro-qa.mdtext Wed Nov 14
16:57:52 2012
@@ -16,17 +16,37 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-In this orientation module you will learn how a Quality Assurance (sometimes called Quality
Engineering or QA or QE)
-works in our community.   We will also learn about basic tasks that are easiest to do for
new QA Volunteers.
+##Introductions
+
+In this orientation module you will learn how Quality Assurance is done in our community.
You will also learn 
+about basic tasks that are easiest to do for new QA Volunteers.
+
+To complete this module, read through the material on this page, including the linked references.
 There will also
+be some start-up tasks for you to perform, such as signing up for an account in our defect
tracking database.
+
+Your first task is to subscribe to our QA mailing list and to introduce yourself to the other
QA volunteers.  You
+can subscribe by sending an email to [qa-subscribe@openoffice.apache.org](mailto:qa-subscribe@openoffice.apache.org).
 
+
+Then you can introduce yourself by [sending an email to the list](mailto:qa@openoffice.apache.org?subject=New
QA Volunteer).
+We'd love to hear who you are, where you are from, what your background is, etc.   Also as
you work through the 
+items on this page, if you have questions or problems, please feel free to ask for help by
sending a note to 
+this same list.
+
+Note:  In parallel with the QA-specific items on this page, you may want to first review
the [Level 1 and Level 2 Orientation Modules](http://incubator.apache.org/openofficeorg/orientation/index.html)
+as well.  They have useful background information on The Apache Way, mailing list etiquette,
decision making in the
+project, etc.  A quick review is a good idea, especially if you are new to working in Apache-style
open source projects.
+
+Now with the introductions out of the way, let's get started with the QA!
 
 ##The Purpose of QA
 
-Our goal is to find defects in the Apache OpenOffice product before it is released to the
general public.  We do
-this by a combination of manual and automated tests that we perform on pre-release builds
of OpenOffice.  We also
-review and try to reproduce defects reported by end-users and submitted to us.
+Our goal is to maintain and improve the quality of Apache OpenOffice.  We primarily accomplish
this by finding defects (bugs) in
+the product before it is released to the general public.  The defects are found by a combination
of manual and 
+automated tests that we perform on pre-release builds of OpenOffice.  We also review and
try to reproduce 
+defects reported by end-users and submitted to us.
 
 Since OpenOffice is a core software application for millions of users, the role of QA is
critical.  Although our
-programmers are wonderful, talented and very experienced, mistakes do happen.  Our task is
to find these mistakes,
+programmers are wonderful, talented and very experienced, they do make mistakes.  Our task
is to find these mistakes,
 report, prioritize them, and verify the fixes when they are made.
 
 QA is a discipline with many best-practices related to process and methodology, tools, techniques
and theory.  
@@ -34,9 +54,51 @@ Although professional QA practitioners a
 prior experience, or those who are learning about QA, perhaps as a possible career.  Aside
from the satisfaction 
 of improving the Apache OpenOffice product, you can learn or practice new skills.
 
-##QA Mailing List
+##Why Help with QA?
+
+As a volunteer why would you want to help with OpenOffice QA?  A few things to consider:
+
+  - We're a fun, international group of testers, of a range of skills and experience, dedicated
to free software and making OpenOffice a high quality choice for users.
+  - This is a good way to learn about QA and get some practical experience.  This is useful,
for example, if you are thinking about Software Quality Engineering (SQE) as a possible career
choice.
+  - Helping as a tester is a good way to "give back" to the open source community in a way
that makes a direct difference in the product, but doesn't require programming skills.
+  - It is a good way to raise the visibility of bugs in your particular interest area.  For
example, maybe you personally are concerned about bugs that cause problems on the Mac, or
bugs that impact color blind users, or bugs related to bidirectional text.  Participating
on the QA team is a good way to ensure that areas of personal interest are adequately tested.
+  - We have tasks for volunteers with a range of skills.  From novices who can help with
manual testing and fix verifications, to experts who can help with our test automation framework,
we have a full range of QA activities.
+  - As an extremely popular open source product, with many millions of users, there are opportunities
here to do some new and exciting things on the QA front, including possibilities of crowd
sourcing some kinds of testing.
+
+
+##QA Activities
+
+QA activities within the Apache OpenOffice project include:    
+
+  - Reviewing incoming bug reports from users to see if the reported issues can be reproduced
+  - Verifying bugs that the developers say they have fixed, to confirm that they actually
have been fixed
+  - Testing new builds of OpenOffice against a functional test plan
+  - Defining new test cases
+  - Running automated regression tests
+  - Specialized tests in areas such as performance, accessibility, localization, security,
etc.
+  - Analyzing defect reports to gauge how we are doing, in terms of quality level, defect
find and fix rates, etc.
+  - Reporting summary defect data and recommending whether a give build of OpenOffice has
reached a sufficient quality level for release.
+  - Making recommendations for improving product quality and testing effectiveness.
+
 
-To get involved as QA volunteer, you first need to subscribe to our dedicated QA mail list.
+##Skills Wanted
+
+The skills we need on the QA team include:
+
+   - Familiarity with OpenOffice as a user.
+   - Attention to detail.  In QA we find the bugs that the developers missed.  And our developers
are pretty good.
+   - Access to a Windows, Mac or Linux machine for testing
+   - Good written communications
+   - Interest, enthusiasm and teamwork.
+   - Ability to volunteer at least 2 hours/week, on average.
+
+QA is as much an attitude as it is a skill set.  A tester likes solving puzzles, likes a
methodical
+approach, likes the challenge of finding an elegant way to reproducibly break software.
+
+
+##Mailing List
+
+As mentioned above, QA volunteers need to subscribe to our dedicated QA mail list.
 
 The mailing list is for bug reports, quality assurance for release, beta tests, manual test,
automated tests, 
 etc.  This is where the QA community coordinates its activities.
@@ -62,6 +124,7 @@ We use the following special subject tag
 
 After you subscribe QA mail list then you can post your topic in the mail group.
 
+
 ##Apache OpenOffice Test Builds
 
 Since our job is to find bugs in OpenOffice, we must run pre-release builds that contain
many bugs.  These bugs 
@@ -96,7 +159,9 @@ Bugzilla related documents:
  * Bug lifecycle introduction [Issue Lifecycle](http://wiki.openoffice.org/wiki/Issue_lifecycle)<br>
  * A guide for reporting a new bug: [How to file bug](http://wiki.openoffice.org/wiki/QA/HowToFileIssue)
 
-To open a new bug, you need to register your Bugzilla account first. [Account Request](https://issues.apache.org/ooo/createaccount.cgi)
+Everyone in QA needs a Bugzilla account, which you can get [here](https://issues.apache.org/ooo/createaccount.cgi).
 Once 
+you have a Bugzilla account, you should send a note to the QA list asking to be added to
the QA role in 
+Bugzilla.  This will give you some additional permissions in Bugzilla.  Include your Bugzilla
login ID in your request.
 
 
 ##Easy QA Tasks
@@ -104,16 +169,15 @@ To open a new bug, you need to register 
 The two easiest tasks for a new QA Volunteer are:
 
   - Verify bug fixes.  This helps you gain familiarity with the OpenOffice product, and our
process.  This 
-verification is also very important, since a good percentage of bug fixes either fail to
fix the bug, or cause
+verification is also very important, since some bug fixes either fail to fix the bug, or
cause
 a new bug.
   - Manual testing.  This gains you further familiarity with QA process, by executing pre-defined
test cases and
 writing up defect reports for any new defects found
- - Writing new test cases.  This is a more advanced topic, but after mastery of the above
two steps, and learning
+  - Writing new test cases.  This is a more advanced topic, but after mastery of the above
two steps, and learning
 to "think like a bug", you will be ready for this.
 
 ### Verifying Fixed Defects
 
-
 You can get resolved bug list from this query: [All fixed bugs after AOO 3.4 release](https://issues.apache.org/ooo/buglist.cgi?cmdtype=runnamed&namedcmd=Fixed_After_340&list_id=36979)
 
 Select the bug you want to verify:
@@ -140,3 +204,12 @@ Useful guide for writing manual test cas
 
  * [A guide for writing test case](http://wiki.openoffice.org/wiki/QA/Testcase/How_to_write_test_case)
  * [A simple test case sample](http://wiki.openoffice.org/wiki/QA/Testcase/Sample)
+
+
+## Module Completion
+
+Once you have done the above, go to our our [Directory of Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers)
wiki page and add or update your 
+information.  Congratulations!  Please send a note to [qa@openoffice.apache.org](mailto:qa@openoffice.apache.org?subject=Completed
Introduction to QA) 
+so we know.
+
+



Mime
View raw message