Mac OS X (X11) Quality Assurance

From Apache OpenOffice Wiki
Revision as of 08:34, 23 May 2007 by KAMiKAZOW (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Mac OS X Quality Assurance



Maho Nakata posts builds to a File Transfer Protocol (ftp) at

QA (Testing)

James McKenzie , Alexis Pigeon, Shaun McDonald, Joerg Sievers (Automation), Martin Srebotnjak (Slovenian) ... [FIXME] : complete the list

QA for 2.2

Description of the process: Testing of is to reproduce actions taken by the ordinary user, either manually (not preferred) or automatically (preferred) test sequences. The localization project (L10N) also checks all menus and other written items for proper wording for the available languages.

- How can I help QA OpenOffice on the Mac?
  First, the product is volunteer.  So, you are asked to add your efforts to those of hundreds if not thousands of
  others who volunteer for coding, testing and production.  Please join the developer's mailing list
  and post a message explaining your experience and the language you would like to test.  Reminder:  en_GB is different from
- How current tests are processed
  The current process for QA of Mac OS X is explained at the TCM site and involves conducting a series of manual tests as well as     
  automated tests.  If a new release candidate is produced with no changes to the Mac OS X version, we conduct a shortened series
  of tests called sanity testing to insure no new problems or the recurrence of old problems.
- clear rules about QA on Mac OS X.
  All QA tests should be conducted per instructions on the TCM web site.  All final results are to be entered on the QA Tracker
  system.  The QA Tracker system allows you to check out a release by language, operating system and platform.  You then
  may either accept or reject the release candidate.  Release candidates should be rejected if a problem is encountered that
  cannot be worked around and would cause a user to abandon use of IN A PRODUCTION work environment.  This means
  if Writer suddenly aborts, you must reject the release.  If fonts appear strange on the page, but print ok, this would not
  result in a reject, but an issue should still be created.
  This system is also used to track QA testing in process with the name of the person conducting the tests.  Any problems
  encountered WILL have an Issue opened for them, if new, or updated, if existing, in the Issue Tracker system.  Please input as
  much information as possible in the Issue Tracker.  At a minimum, you should input the steps needed to replicate the problem
  you encountered and which release you were using of, Mac OS X and X11.  Any additional information you feel
  that will help a developer fix the problem can be included, such as crash logs, which are found using the Console application
  and opening the local user Library/logs file and looking for soffice.bin.crash logs.   Please do not post your logs to NoPaste
  and then enter a link in the Issue, but rather upload the log and add it to the Issue.
- links for external information.
- recent *all concerned  locales* , with current status     
  Due to issues with other platforms, the current release candidate rc3 was not approved by Sun as a final release.  However, no
  issues were found in this candidate that have not been found in prior releases.  

All builds are obtained from a site maintained by Maho Nakata, Files are located in the pub/ directory. Files are named OOo_2.2rc3_20070306_MacOSX<Platform, Intel or PPC>_<iso language code>.dmg.


QA for the 2.2 version is underway.  Testing for this version is scheduled to close on March 31, 2007, 
but we would like to test it quickly to find fixable problems.
This date is subject to change as problems are encountered and resolved.

Mac port Links

This work is part of

Personal tools