Views

Tester Guide

Contents

Role

Workspace of: Tester
Browse this workspace
Browse other Workspaces
Members Corner
Contacts
Contact us
Main Guides
Tester Guide
Active tickets (Trac)
Workspace's Tickets

The role of the tester is to find any remaining bug of the future release.

Context

  • Jajuk versioning scheme is : <major>.<minor>.<fix> like 1.5.4
  • RC means 'Release Candidate' and designates internal testing releases
  • This manual only concern RC releases, for already released versions, you're welcomed to report issues on production releases using the Jajuk ticket system

Testing new releases

How many time does it take ?

About 5 minutes per test case (there are currently from 40 to 50 test cases) : please choose a set of test cases that have not already been tested according the time you have

How to become Jajuk tester ?

Jajuk needs testers all the year but especially within the one-month qualification time frame before a major release and few weeks after in order to help finding distribution issues early.

  • You don't to subscribe anything to begin testing, just edit this wiki
  • (Recommended) Subscribe to jajuk-developers Mailing Lists to be aware of new release candidates

How to get last Jajuk release running ?

  • [Linux and Mac only] If under Linux or Mac OS, make sure to get mplayer 1.0 pre8 or later running on your system (nothing needed for Windows). Check out Category:Installation Guides if you need help to install.
  • Make sure to have a Java 6 runtime environment (JRE 1.6 or later). If needed, download and install JRE (for free).
  • Launch last Jajuk test release (this link never change, you can bookmark it). This will install and launch Jajuk in Java Web Start mode, next release will be upgraded automatically
  • Check the Jajuk release in the splashscreen or in the About view (you would continue to use previous release if your client cannot connect to Java Web Start server in a short time frame).

How to test ?

  • Go to 1.6 qualification page
  • Search for not already run test cases in the "manual tests" section
  • Perform manually in Jajuk application
  • Come back to the test page, edit it, set your name and "PASSED" or "FAILED" in title (like in the sample test case). If test failed, set "FAILED" and please open a ticket (see next section).

How to get support ?

The bug tracker system

  • Please report issues you found in Trac, against the trunk release
  • The best way to do it is from Jajuk using the Help -> "Report an issue" feature : it opens your Web browser, then paste your traces (Ctrl-V) in the ticket body and create the ticket.

Notes

  • RC releases use the '-test' flag so Jajuk data will be store in <HOME>/.jajuk_test_<version> directory and not <HOME>/.jajuk directory used by final releases. This way, you can continue to use stable jajuk and test releases concurrently
  • As a consequence, you'll have to rebuild your jajuk collection and to reapply your specific parameters when switching from a stable release to a test release. You can also copy all files and directories from <HOME>/.jajuk to <HOME>/.jajuk_test_<version> to get your collection right out of the box.

Qualification pages

See also

Retrieved from "http://www.jajuk.info/index.php/Tester_Guide"