openoffice-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r967998 - in /websites/staging/openoffice/trunk/content: ./ orientation/intro-qa.html
Date Tue, 06 Oct 2015 21:13:15 GMT
Author: buildbot
Date: Tue Oct  6 21:13:15 2015
New Revision: 967998

Staging update by buildbot for openoffice

    websites/staging/openoffice/trunk/content/   (props changed)

Propchange: websites/staging/openoffice/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Tue Oct  6 21:13:15 2015
@@ -1 +1 @@

Modified: websites/staging/openoffice/trunk/content/orientation/intro-qa.html
--- websites/staging/openoffice/trunk/content/orientation/intro-qa.html (original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-qa.html Tue Oct  6 21:13:15
@@ -49,7 +49,18 @@
   <div id="clear"></div>
   <div id="sidenav">
-    <h1 id="general">General</h1>
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<h1 id="general">General<a class="headerlink" href="#general" title="Permanent link">&para;</a></h1>
 <li><a href="/index.html">About</a></li>
 <li><a href="/downloads.html">Downloads</a></li>
@@ -58,7 +69,7 @@
 <li><a href="/press.html">Press</a></li>
 <li><a href=""> website</a></li>
-<h1 id="community">Community</h1>
+<h1 id="community">Community<a class="headerlink" href="#community" title="Permanent
 <li><a href="/get-involved.html">Get Involved</a></li>
 <li><a href="/orientation/index.html">Orientation</a></li>
@@ -71,7 +82,7 @@
 <li><a href="/people.html">People</a></li>
 <li><a href="/community-faqs.html">Community FAQs</a></li>
-<h1 id="development">Development</h1>
+<h1 id="development">Development<a class="headerlink" href="#development" title="Permanent
 <li><a href="/source.html">Source Code</a></li>
 <li><a href="/bug-tracking.html">Bug Tracking</a></li>
@@ -82,12 +93,12 @@
 <li><a href="/contributing-code.html">Contributing Code</a> </li>
 <li><a href="/developer-faqs.html">Developer FAQs</a></li>
-<h1 id="project-management-pmc">Project Management PMC</h1>
+<h1 id="project-management-pmc">Project Management PMC<a class="headerlink" href="#project-management-pmc"
title="Permanent link">&para;</a></h1>
 <li><a href="">Project Blog</a></li>
 <li><a href="/pmc-faqs.html">PMC FAQs</a>  </li>
-<h1 id="the-apache-software-foundation">The Apache Software Foundation</h1>
+<h1 id="the-apache-software-foundation">The Apache Software Foundation<a class="headerlink"
href="#the-apache-software-foundation" title="Permanent link">&para;</a></h1>
 <li><a href="">Website</a></li>
 <li><a href="">Donations</a></li>
@@ -98,14 +109,25 @@
   <div id="contenta">
     <h1 class="title">Introduction to QA</h1>
-    <h2 id="introductions">Introductions</h2>
+    <style type="text/css">
+/* The following code is added by
+   It was originally lifted from */
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
+<h2 id="introductions">Introductions<a class="headerlink" href="#introductions"
title="Permanent link">&para;</a></h2>
 <p>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.</p>
 <p>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.</p>
 <p>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 <a href=""></a>.
-<p>Then you can introduce yourself by <a href="">sending
an email to the list</a>.
+<p>Then you can introduce yourself by <a href="
QA Volunteer">sending an email to the list</a>.
 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.</p>
@@ -113,7 +135,7 @@ this same list.</p>
 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.</p>
 <p>Now with the introductions out of the way, let's get started with the QA!</p>
-<h2 id="the-purpose-of-qa">The Purpose of QA</h2>
+<h2 id="the-purpose-of-qa">The Purpose of QA<a class="headerlink" href="#the-purpose-of-qa"
title="Permanent link">&para;</a></h2>
 <p>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 
@@ -125,7 +147,7 @@ report, prioritize them, and verify the
 Although professional QA practitioners are welcome in this project, we are also happy to
welcome those with no
 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.</p>
-<h2 id="why-help-with-qa">Why Help with QA?</h2>
+<h2 id="why-help-with-qa">Why Help with QA?<a class="headerlink" href="#why-help-with-qa"
title="Permanent link">&para;</a></h2>
 <p>As a volunteer why would you want to help with OpenOffice QA?  A few things to consider:</p>
 <li>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.</li>
@@ -135,7 +157,7 @@ of improving the Apache OpenOffice produ
 <li>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.</li>
 <li>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.</li>
-<h2 id="qa-activities">QA Activities</h2>
+<h2 id="qa-activities">QA Activities<a class="headerlink" href="#qa-activities"
title="Permanent link">&para;</a></h2>
 <p>QA activities within the Apache OpenOffice project include:    </p>
 <li>Reviewing incoming bug reports from users to see if the reported issues can be
@@ -148,7 +170,7 @@ of improving the Apache OpenOffice produ
 <li>Reporting summary defect data and recommending whether a give build of OpenOffice
has reached a sufficient quality level for release.</li>
 <li>Making recommendations for improving product quality and testing effectiveness.</li>
-<h2 id="skills-wanted">Skills Wanted</h2>
+<h2 id="skills-wanted">Skills Wanted<a class="headerlink" href="#skills-wanted"
title="Permanent link">&para;</a></h2>
 <p>The skills we need on the QA team include:</p>
 <li>Familiarity with OpenOffice as a user.</li>
@@ -160,7 +182,7 @@ of improving the Apache OpenOffice produ
 <p>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.</p>
-<h2 id="mailing-list">Mailing List</h2>
+<h2 id="mailing-list">Mailing List<a class="headerlink" href="#mailing-list" title="Permanent
 <p>As mentioned above, QA volunteers need to subscribe to our dedicated QA mail list.</p>
 <p>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.</p>
@@ -183,7 +205,7 @@ Unsubscribe: <a href="qa-unsubscribe@ope
 <li>[QA] default if others don't fit. </li>
 <p>After you subscribe QA mail list then you can post your topic in the mail group.</p>
-<h2 id="apache-openoffice-test-builds">Apache OpenOffice Test Builds</h2>
+<h2 id="apache-openoffice-test-builds">Apache OpenOffice Test Builds<a class="headerlink"
href="#apache-openoffice-test-builds" title="Permanent link">&para;</a></h2>
 <p>Since our job is to find bugs in OpenOffice, we must run pre-release builds that
contain many bugs.  These bugs 
 could be major or minor.  They could include document corruption bugs, crashes, even (in
rare cases) bugs that 
 could make your system unstable.    So QA volunteers generally try to separate their QA work
from their normal
@@ -197,10 +219,10 @@ which can work quite well.  <a href="htt
 <li><a href="">AOO nightly
build</a> are built each night and are our "rawest"
 builds, with many possibilities for finding new bugs.</li>
-<li><a href="">Snapshot
builds</a>, are made
-generally every few weeks, are built in multiple languages and platforms.</li>
+<li><a href="">Snapshot builds</a>,
(tagged with the word "Snapshot") are made
+weekly against a code branch that is being considered for a release candidate.</li>
-<h2 id="bug-handling">Bug Handling</h2>
+<h2 id="bug-handling">Bug Handling<a class="headerlink" href="#bug-handling" title="Permanent
 <p>Apache Bugzilla is where we track defects:</p>
 <li><a href=""></a></li>
@@ -217,7 +239,7 @@ generally every few weeks, are built in
 <p>Everyone in QA needs a Bugzilla account, which you can get <a href="">here</a>.
 you have a Bugzilla account, you should send a note to the QA list asking to be added to
the "qa-team" group in 
 Bugzilla.  This will give you some additional permissions in Bugzilla.  Include your Bugzilla
login ID in your request.</p>
-<h2 id="easy-qa-task-confirm-new-defect-reports">Easy QA Task: Confirm New Defect Reports</h2>
+<h2 id="easy-qa-task-confirm-new-defect-reports">Easy QA Task: Confirm New Defect Reports<a
class="headerlink" href="#easy-qa-task-confirm-new-defect-reports" title="Permanent link">&para;</a></h2>
 <p>Most new volunteers start by reviewing incoming defect reports and attempting to
"confirm" them.   The defect reports are 
 often from users and are often not very clearly written.  You learn to "read between the
lines" and ask the user clarifying questions
 in order to turn the raw report into a reproducible defect that the developers can debug
and fix.</p>
@@ -259,7 +281,7 @@ the details and we can reopen the report
 sorting through them, eliminating the ones that do not report new bugs, and then passing
on the good ones to the programmers.  So anything you can do to improve the quality
 of the incoming defect reports will help.  This includes clarifying the steps needed to reproduce
the problem, attaching sample documents that you might create to reproduce the
 problem, improving report titles to make them more accurate/relevant to the real issue, correcting
classifications and adjusting defect priorities.</p>
-<h2 id="easy-qa-task-verifying-fixed-defects">Easy QA Task: Verifying Fixed Defects</h2>
+<h2 id="easy-qa-task-verifying-fixed-defects">Easy QA Task: Verifying Fixed Defects<a
class="headerlink" href="#easy-qa-task-verifying-fixed-defects" title="Permanent link">&para;</a></h2>
 <p>Verifying bug fixes (re-testing a bug report after a developer has fixed it) is
also very important, since some bug fixes either fail to fix the bug, or cause
 a new bug.</p>
 <p>You can get a list of fixed bugs from this query: <a href=";remaction=run&amp;namedcmd=Fixed_After_340&amp;sharer_id=248432">All
fixed bugs after AOO 3.4 release</a></p>
@@ -273,7 +295,7 @@ a new bug.</p>
 this as you learn to "think like a bug".</li>
 <li>Change defect status to "Verified" </li>
-<h2 id="easy-qa-task-manual-testing">Easy QA Task: Manual Testing</h2>
+<h2 id="easy-qa-task-manual-testing">Easy QA Task: Manual Testing<a class="headerlink"
href="#easy-qa-task-manual-testing" title="Permanent link">&para;</a></h2>
 <p>Manual testing gains you further familiarity with QA process, by executing pre-defined
test cases and
 writing up defect reports for any new defects found</p>
 <p>To get more familiar with AOO, now you can try to perform some manual test cases.</p>
@@ -281,7 +303,7 @@ writing up defect reports for any new de
 <li>Browse test management tool, <a href="">Testlink</a>
to find available test cases.<br></li>
 <li>Read this guide if you are not familiar with Testlink tool. <a href="">Testlink
usage guide</a></li>
-<h2 id="easy-qa-task-test-case-authoring">: Easy QA Task: Test Case Authoring</h2>
+<h2 id="easy-qa-task-test-case-authoring">: Easy QA Task: Test Case Authoring<a
class="headerlink" href="#easy-qa-task-test-case-authoring" title="Permanent link">&para;</a></h2>
 <p>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.</p>
 <p>After some practice on test case execution, now you can start writing new test cases.</p>
 <p>Useful guide for writing manual test cases:</p>
@@ -289,10 +311,10 @@ writing up defect reports for any new de
 <li><a href="">A
guide for writing test case</a></li>
 <li><a href="">A simple test
case sample</a></li>
-<h2 id="module-completion">Module Completion</h2>
+<h2 id="module-completion">Module Completion<a class="headerlink" href="#module-completion"
title="Permanent link">&para;</a></h2>
 <p>Once you have done the above, go to our our <a href="">Directory
of Volunteers</a> wiki page and add or update your 
 information.  Also, add an entry for yourself to the <a href="">QA
Testing Preferences</a> page. Congratulations!<br />
-Please send a note to <a href=""></a>
so we know.</p>
+Please send a note to <a href=" Introduction
to QA"></a> so we know.</p>
   <div id="footera">

View raw message