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.

Hitek Computer School is owned and operated by Iriol Software Ltd.

Participants of the project.

There are 2 groups

Group 1

• Oleg Rodov

Group 2:

• Natalia Polyudova

New HitekSchool project participants can start their 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 you.
   • 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.

Step 3:

1. Install office developer version and try different applications: http://download.openoffice.org/680/index.html
2. Issue tracker:
   • make familiar with the tooling
   • have a look at Quality Assurance - Report Bugs
   • have a look on some issues in real and how they are handled
   • write a test issue

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.