<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> During this new 6 month cycle we are hoping to ramp up testing of applications - separate from testing ISO's. So if you want to get involved with something that you can pick up, put down and which isn't too onerous this could be for you. Before we can set up testing of applications ( it's tracked on a Ubuntu QA tracker and they call it package testing) we need to make sure the tests we do have are up to date. You will need a few things: <ol> <li>an up to date iso to boot - you can run the test from a USB, a virtual machine </li> <li>something to write on</li> <li>a web browser</li> <li>an e-mail client </li> <li>patience - we've not checked them for at a year </li> </ol> You can grab the iso from <a class="moz-txt-link-freetext" href="http://cdimage.ubuntu.com/xubuntu/daily-live/current">http://cdimage.ubuntu.com/xubuntu/daily-live/current</a> - this url is always the latest. Open your browser at <a class="moz-txt-link-freetext" href="http://packages.qa.ubuntu.com/qatracker/milestones/377/builds/146768/testcases">http://packages.qa.ubuntu.com/qatracker/milestones/377/builds/146768/testcases</a> You'll see a list of applications and packages there. <ol> <li>Pick something you fancy checking - Reply All to this mail telling other people what you intend to test (we'd not want everyone to be checking the same testcase)</li> <li>Open your chosen testcase, then click the Detailed information on the testcase button and make a note of the Testcase ID </li> <li>Follow the testcase exactly as it tells you </li> <li>Make notes where something isn't working as the testcase expects - this is a bug, a testcase bug. If necessary continue to the next step as best you can ignoring the instruction if the application no longer works as written </li> <li>When you have completed checking your testcase and assuming that you found no errors with it - let us know on the mailing list.</li> </ol> That's a lot of words which basically mean - read the testcase, follow it and note down where something is different. If you did find an issue with the testcase - report it to Launchpad. This could be as simple as the testcase calls for a button called Next but it's now called Continue, it could even be that the testcase covers something the application does but isn't tested. <ol> <li>Open your browser at <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu-manual-tests/+filebug">https://bugs.launchpad.net/ubuntu-manual-tests/+filebug</a></li> <li>In the Summary box - please report it with something like this syntax Testcase 1559 Catfish Fails To Open From Whiskermenu, 1559 being the ID you previously noted </li> <li>Click Next - then regardless of any previous bugs it prompts you with - Click No, I need to report a new bug</li> <li>Using the notes you made while checking the testcase fill in your further information</li> <li>You can now if you wish tell us the bug number - but it's not necessary as I am subscribed to Testcase Bugs</li> </ol> If you have needed to report a bug - the Testcase ID is important - there are 1700 different ID numbers - and the majority refer to live testcases. If the list of applications on the package tracker doesn't include something you use that you think should be tested - and is something that we have by default - you can report this to the same url above - just say Testcase need for 'you fave application we don't test' If I need further information I will comment on your bug report so please keep an eye out for that. If you found that easy to do - how about doing another one ;) Cheers Kev for the Xubuntu Developers and QA Teams </body> </html>