Difference between revisions of "OOo QA Participation Steps"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 1: Line 1:
−
TestDoc
+
==Initial Steps==
  
 +
'''Step 1:'''
  
−
== Step 1: ==
+
# <!--1-->Get a general overview over the OO QA project and how it works [http://qa.openoffice.org/ Quality Assurance] and [http://wiki.services.openoffice.org/wiki/QA_reloaded OOo QA Strategic Concept Papers]
 +
# <!--2-->Make familiar with reporting bugs, especially issue handling: [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance Report Bugs]
  
−
# Get a general overview over the OO QA project and how it works [http://qa.openoffice.org/ Quality Assurance] and [http://wiki.services.openoffice.org/wiki/QA_reloaded OOo QA Strategic Concept Papers]
 
−
# Make familiar with reporting bugs, especially issue handling: [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance Report Bugs]
 
  
  
 +
'''Step 2:'''
  
−
== Step 2: ==
+
# <!--3-->Register at OOo as ''firstname-HitekSchool@openoffice.org''
−
 
+
# <!--4-->Try mailing list dev@qa.openoffice.org from [http://qa.openoffice.org/servlets/ProjectMailingListList QA Mailing lists]. You can find Introduction to General & Project Mailing Lists [http://www.openoffice.org/mail_list.html here].
−
# Register at OOo as ''firstname-HitekSchool@openoffice.org ???''
+
−
# Try mailing list dev@qa.openoffice.org from [http://qa.openoffice.org/servlets/ProjectMailingListList QA Mailing lists]. You can find Introduction to General & Project Mailing Lists [http://www.openoffice.org/mail_list.html here].
+
 
#* Just say hello if you do not have any tasks/questions.
 
#* Just say hello if you do not have any tasks/questions.
−
#* '' How to do it from inside the OOo.???''
+
<!--#* '' How to do it from inside the OOo.???'' -->
−
# Try IRC channel: please find and install an IRC client that suits you.  
+
# <!--5-->Try IRC channel: please find and install an IRC client that suits for you (there are a lot of free tools in the Internet. You can take a look into this [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients list of IRC clients] and pick up one which is most convenient for you. Basically, Opera chat tool works pretty well).  
 
#* The IRC channel on the Freenode server irc://irc.freenode.net/  for this QA project is #qa.openoffice.org
 
#* The IRC channel on the Freenode server irc://irc.freenode.net/  for this QA project is #qa.openoffice.org
 
#* OpenOffice.org's localization community hangs out at channel #ooonlc
 
#* OpenOffice.org's localization community hangs out at channel #ooonlc
 
#** You can say "Hi" and Bye" and disappear very quickly, if you like.
 
#** You can say "Hi" and Bye" and disappear very quickly, if you like.
−
# Try OO wiki (create a simple XXX page and send the link). Find instructions on wiki help.
+
# <!--6-->Try OO wiki (create a simple XXX page and send the link). Find instructions on wiki help.  
 +
#*Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.
 +
# Create a 'calling card' in oo wiki like: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool User:Oleg-HitekSchool]  and connect it with earlier created page
 +
#* You should include your OOo email address there
 +
 
 +
 
 +
 
 +
 
 +
 
 +
'''Step 3:'''
 +
 
 +
<!--please redirect you page that a visitor will automaticly land on 'XXX' page, add your name as author and connect with your calling card -->
 +
 
 +
# <!--7-->Install office developer version and try different applications: http://download.openoffice.org/680/index.html
 +
#* Find out what you need for your system and install office developer version at your computer.
 +
#* You can try to work with it and reveal issues. For reporting them you need to use Issue Tracker.
 +
# <!--8-->Issue tracker:
 +
#* make familiar with the tooling
 +
#** basic rules you should know before sending Issues,
 +
#** bug lifecycle,
 +
#** the way to query issue and to track it
 +
#* have a look at [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance - Report Bugs]
 +
#** make familiar with Issue Handling, Issue Enter
 +
#* have a look on some issues in real and how they are handled - status changing from unconfirmed to closed
 +
#* write a test issue (and send its number to your team lead)
 +
#** check whether similar issue is alreagy described (including duplicate and closed)
 +
#** pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
 +
# <!--9-->confirm 10 issues
 +
#* each team site from [http://qa.openoffice.org/ Quality Assurance] has a link called 'open issues'. Have a look inside several issues and try to reproduce them on your system (try different application); write in the issue: "I can reproduce that on system .. with version .. etc. (check how others handles such things) and send the collected issue numbers to your team leader. You need to log in for doing this.
 +
# <!--10-->Make familiar with the [http://wiki.services.openoffice.org/wiki/EIS EIS] tool.
 +
# <!--11-->Close 10 'verified issues'
 +
#* site [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-Sitemap.html Sitemap of the Quality Assurance Pages] has a link called 'Integrated Issues'. Check if the bug is fixed in a master version (must be already integrated, therefore check in the [http://wiki.services.openoffice.org/wiki/EIS EIS] tool). If yes - write in the issue something like: "verified in XY master version - can be closed" (you don't have canconfirm rights to close it by yourselves for now) and send the collected issue numbers to your team leader.
 +
#<!--12-->Join an [http://wiki.services.openoffice.org/wiki/issue_hunting_party#Issue_hunting_party_13th_of_January_2009 Issue Hunting Party].
 +
 
 +
 
 +
''Authors: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov], [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polyudova]. 28 December 2008''
 +
 
 +
''Mentor of the Intership program: [http://wiki.services.openoffice.org/wiki/User:Clu Christoph Lukasiak]''
 +
 
 +
''Please do not change the logical content of this site without
 +
acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads].''
 +
[[Category:Quality Assurance]]

Revision as of 05:28, 23 January 2009

Initial Steps

Step 1:

  1. Get a general overview over the OO QA project and how it works Quality Assurance and OOo QA Strategic Concept Papers
  2. Make familiar with reporting bugs, especially issue handling: Quality Assurance Report Bugs


Step 2:

  1. Register at OOo as firstname-HitekSchool@openoffice.org
  2. Try mailing list dev@qa.openoffice.org from QA Mailing lists. You can find Introduction to General & Project Mailing Lists here.
    • Just say hello if you do not have any tasks/questions.
  3. Try IRC channel: please find and install an IRC client that suits for you (there are a lot of free tools in the Internet. You can take a look into this list of IRC clients and pick up one which is most convenient for you. Basically, Opera chat tool works pretty well).
    • The IRC channel on the Freenode server irc://irc.freenode.net/ for this QA project is #qa.openoffice.org
    • OpenOffice.org's localization community hangs out at channel #ooonlc
      • You can say "Hi" and Bye" and disappear very quickly, if you like.
  4. Try OO wiki (create a simple XXX page and send the link). Find instructions on wiki help.
    • Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.
  5. Create a 'calling card' in oo wiki like: User:Oleg-HitekSchool and connect it with earlier created page
    • You should include your OOo email address there



Step 3:


  1. Install office developer version and try different applications: http://download.openoffice.org/680/index.html
    • Find out what you need for your system and install office developer version at your computer.
    • You can try to work with it and reveal issues. For reporting them you need to use Issue Tracker.
  2. Issue tracker:
    • make familiar with the tooling
      • basic rules you should know before sending Issues,
      • bug lifecycle,
      • the way to query issue and to track it
    • have a look at Quality Assurance - Report Bugs
      • make familiar with Issue Handling, Issue Enter
    • have a look on some issues in real and how they are handled - status changing from unconfirmed to closed
    • write a test issue (and send its number to your team lead)
      • check whether similar issue is alreagy described (including duplicate and closed)
      • pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
  3. confirm 10 issues
    • each team site from Quality Assurance has a link called 'open issues'. Have a look inside several issues and try to reproduce them on your system (try different application); write in the issue: "I can reproduce that on system .. with version .. etc. (check how others handles such things) and send the collected issue numbers to your team leader. You need to log in for doing this.
  4. Make familiar with the EIS tool.
  5. Close 10 'verified issues'
    • site Sitemap of the Quality Assurance Pages has a link called 'Integrated Issues'. Check if the bug is fixed in a master version (must be already integrated, therefore check in the EIS tool). If yes - write in the issue something like: "verified in XY master version - can be closed" (you don't have canconfirm rights to close it by yourselves for now) and send the collected issue numbers to your team leader.
  6. Join an Issue Hunting Party.


Authors: Oleg Rodov, Natalia Polyudova. 28 December 2008

Mentor of the Intership program: Christoph Lukasiak

Please do not change the logical content of this site without acknowledge of the author or the OOo QA Project Lead/Co-Leads.

Retrieved from "https://wiki.openoffice.org/w/index.php?title=OOo_QA_Participation_Steps&oldid=108806"
Personal tools