Server Community QA

There are many things you can do to help out with the Chandler Server project in the QA department and not all of them require being able to code. There are both technical and non-technical aspects of it. Here's an overview of the different ways you can help:

1. Get an account in bugzilla

To be able to help out with any of the QA activities, you first need to create an account in bugzilla.

2. Reporting bugs by running the manual tests

You can help by executing the manual testcases against Chandler. You can start out by downloading the nightly builds from our builds server. Linux testers are particularly welcome. The use case scenarios are listed in the various specs here: Test Specifications. Before submitting a bug report, search bugzilla for the open bugs to make sure the bug has not already been reported. If it has, then feel free to add any extra details you can. Read the bug writing guidelines before submitting a new bug.

3. Finding regressions by running the acceptance tests

If you have only a few hours to spare, you can help by running the Acceptance tests on the latest nightly build. This would help us catch any regressions introduced in the new builds.

4. Reporting bugs by running the automated functional tests

You can also help by running the automated functional tests on the frontend. All the information for checking out the test scripts and executing them is available from the Running Server Frontend Automaed Tests page. For the testcases that fail, you can create a bug report in bugzilla after searching the open bugs list.

5. Developing additional functional tests

If you are a java script developer, you can help by developing additional testscripts for web UI using our Windmill test framework. You can find further details on how to write and execute the tests on the Writing Web UI tests page.

6. Verifying Resolved bugs

We have lots of bugs that are in Resolved but unVerified state. You can help by going over the list of Resolved bugs, verifying if they have indeed been resolved and marking them Verified Fixed or Reopening them. Here are the bugs that have been fixed but not yet been verified.

7. Resolving duplicate bugs

Scanning through the list of open bugs and marking duplicate bugs.

8. Running cross-browser tests

A number of bugs reported on Server Web UI have reproduced on a single browser. We need volunteers who can verify the behaviour on the other platforms and browsers.

9. Join Bug Fests on IRC

Join us for our weekly bug fests on IRC at 11:00 AM PDT on Wednesdays in the #osaf-qa channel. We download the latest builds and collaboratlvely test and file bugs and exchange useability feedback. More information on how to join the channels.

10. Use our tools and contribute

QA tools are stored in our qa svn repository.

svn checkout http://svn.osafoundation.org/qa/ qatools

or

svn checkout http://svn.osafoundation.org/qa/trunk qatrunk

If you wish to contribute you can come in to irc.freenode.net in #osaf-qa to find out what we need done and/or who to send a diff to.

-- AparnaKadakia - 06 Apr 2007