Committed. Thanks for the patch. I'll review more later today. -Rob
On Thu, Nov 1, 2012 at 3:34 AM, Yan Ji <anonym...@apache.org> wrote: > Clone URL (Committers only): > https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openofficeorg.apache.org/openofficeorg%2Forientation%2Fintro-qa.mdtext > > Yan Ji > > Index: trunk/content/openofficeorg/orientation/intro-qa.mdtext > =================================================================== > --- trunk/content/openofficeorg/orientation/intro-qa.mdtext (revision > 1404425) > +++ trunk/content/openofficeorg/orientation/intro-qa.mdtext (working copy) > @@ -1,26 +1,89 @@ > -Title: Introduction to QA > -Notice: Licensed to the Apache Software Foundation (ASF) under one > - or more contributor license agreements. See the NOTICE file > - distributed with this work for additional information > - regarding copyright ownership. The ASF licenses this file > - to you under the Apache License, Version 2.0 (the > - "License"); you may not use this file except in compliance > - with the License. You may obtain a copy of the License at > - . > - http://www.apache.org/licenses/LICENSE-2.0 > - . > - Unless required by applicable law or agreed to in writing, > - software distributed under the License is distributed on an > - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > - KIND, either express or implied. See the License for the > - specific language governing permissions and limitations > - under the License. > - > -1. Please send an email to > [ooo...@incubator.apache.org](mailto:ooo...@incubator.apache.org?subject=Starting > Introduction to QA) to let us know you are working on this module. > - > -1. Understanding the defect workflow > - > - > -1. Congratulations! You have completed this Level. Please send a note to > [ooo...@incubator.apache.org](mailto:ooo...@incubator.apache.org?subject=Completed > Introduction to QA) so > -we all know you have completed this level. This is also a good opportunity > to send along any feedback or questions you might have on this Orientation > Module. > - > +Title: Introduction to QA > +Notice: Licensed to the Apache Software Foundation (ASF) under one > + or more contributor license agreements. See the NOTICE file > + distributed with this work for additional information > + regarding copyright ownership. The ASF licenses this file > + to you under the Apache License, Version 2.0 (the > + "License"); you may not use this file except in compliance > + with the License. You may obtain a copy of the License at > + . > + http://www.apache.org/licenses/LICENSE-2.0 > + . > + Unless required by applicable law or agreed to in writing, > + software distributed under the License is distributed on an > + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > + KIND, either express or implied. See the License for the > + specific language governing permissions and limitations > + under the License. > + > +LEVEL 1: INTRODUCTION TO QA<br> > +In this orientation module you will know how a QA works in community.<br> > +To get involved into QA work, firstly you need subscribe mail list: > + > +***QA Mailing List*** > + > +The list is for bug reports, quality assurance for release, beta tests, > manual test, automated tests, etc. > + > +Subscribe: > [ooo-qa-subscr...@incubator.apache.org](mailto:ooo-qa-subscr...@incubator.apache.org)<br> > +Post (after subscription): > [ooo...@incubator.apache.org](mailto:ooo...@incubator.apache.org)<br> > +Unsubscribe: > [ooo-qa-unsubscr...@incubator.apache.org](ooo-qa-unsubscr...@incubator.apache.org) > + > +Archives: > + > + - [Markmail](http://markmail.org/search/+list:org.apache.incubator.ooo-qa) > + - [Apache](http://mail-archives.apache.org/mod_mbox/incubator-ooo-qa/) > + > +Post mail using special tag to identify QA activities: > + > + * [QA REPORT] - topic related with status report > + * [QA AUTOMATION] - topic related with automation tools, scripts and scope > + * [QA BUG] - topic related with bug discussion > + * [QA CRITICAL] - important information related with QE > + * [QA CALLFORREVIEW] - topic with some review > + * [QA CALLFORVOLUNTEER] - if you want to call for volunteer for testing > some features > + * [QA] default if others don't fit. > + > +After you subscribe QA mail list then you can post your topic in the mail > group. > + > +***Bug Handling***: > + > +Apache Bugzilla: > + > + * [http://issues.apache.org/ooo](http://issues.apache.org/ooo) > + > +Bugzilla related documents: > + > + * Bug lifecycle introduction [Issue > Lifecycle](http://wiki.openoffice.org/wiki/Issue_lifecycle)<br> > + * A guide for opening bug: [How to file > bug](http://wiki.openoffice.org/wiki/QA/HowToFileIssue) > + > +To open a new bug, you need register your bugzilla account firstly. [Account > Request](https://issues.apache.org/ooo/createaccount.cgi) > + > +Now you can work as a QA role, starting from verifying fixed bugs to get > familiar with AOO product. > + > +To verify fixed defect, you need to get latest build. AOO nightly build are > available at build bot: [AOO > buildbot](http://ci.apache.org/projects/openoffice/index.html) > + > +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: > + > + 1. First you need to understand which fault does the bug is referring to. > + 1. Install the latest build. > + 1. Follow the reproduce steps to check if the defect has been fixed. > + 1. Add additional comments to the bug with your test result. e.g. build > revision number, platform you have been tested etc. > + 1. Change defect status to "Verified"(this action requires "CanEdit" > privilege" in Bugzilla system, if you cannot do that then send mail to > mailing list and ask other QA do this for you.) > + > + > + > +***Manual Testing*** > + > +To get more familiar with AOO, now you can try to perform some manual test > cases. > + > +Browse test management tool, > [Testlink](http://aootesting.adfinis-sygroup.org) to find available test > cases.<br> > +Read this guide if you are not familiar with Testlink tool. [Testlink usage > guide](http://wiki.openoffice.org/wiki/QA/Testlink ) > + > +After some practices on test case execution, now you can start writing new > test cases. > + > +Useful guide for writing manual test cases: > + > + * [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) >
