HitekSchool

[HitekSchool] is a Vancouver (Canada) based computer institution which teaches its students all necessary techniques, methodologies and tools they need to know to build a successful career as a Software Tester. Those students who make an internship program in OO.o QA, are corresponding to the free and open mentoring program of OO [1] and publish in this way their experience and outcomes to share it with the OO community.

Participants of the project.

There are 2 groups

Group 1

• Oleg Rodov

Group 2:

• Natalia Polyudova

New HitekSchool project participants can download and install free OpenOffice.org version 3.0 for their system from Download Page
and make familiar with an application. You can start your acquaintance with the OOo QA project from the following Initial Steps:

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

if you do not came further with anything, you can ask us any time, but always try the 'wiki - OO info sites - mailing list ' first .. If you have still a question, several people probably will have the same problem, too ..

Please, send your hints or comments which can help next students to Natalia Polyudova or Oleg Rodov to have them integrated into this check-list.

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.

Autors: 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.