Thank you, Chris and Aaron for the clarification! Will be happy to help Guilherme Nolasco
-----Original Message----- From: Chris Guiver <[email protected]> Sent: Friday, November 17, 2023 12:08 AM To: Guilherme Nolasco <[email protected]> Cc: [email protected] Subject: Re: Instructions for newbie - QA procedures Reply to Guilherme re: checklist The ISO QA site for noble (24.04) can currently be found here - https://iso.qa.ubuntu.com/qatracker/milestones/450/builds If you scroll down to find Ubuntu Studio, you'll be offered a link to a page, which currently is - https://iso.qa.ubuntu.com/qatracker/milestones/450/builds/289884/testcases Do NOTE however that [second] link will change (the page will no longer allow new tests to be entered) the moment a new 'daily' is created, as the 289884 part of the URL will alter to represent the new daily; thus it's best to enter from my first provided URL (450 is noble daily and can be used the entire cycle; though in time we'll have another number for beta, final etc - but the daily URL will still work) Using that link will provide a few testcases, being - Install (auto-resize) - Install (entire disk) - Install (manual partitioning) - Live Session - Ubuntu Studio PipeWire Post-Install though those items may change during the cycle too. Clicking on them will reveal details. The ISO QA site is for reporting results of testing, and has fields for linking bugs encountered & reported as Aaron already outlined. The bug reports will get linked to QA with use of this site, allowing for better tracking. The checklists are mostly geared for install testing, with the 'live' test itself where you can check each application starts & operates. For normal testing (ie. just using the product, as I'm using my current Lubuntu noble (24.04)) no reporting on iso.qa.ubuntu.com is necessary. Chris g. On 11/16/23, Guilherme Nolasco <[email protected]> wrote: > Hi, everyone! > > I’ve just joined the QA-test team for Edubuntu 24.04 and would like > some instructions on how to behave, please. > > How am I to report bugs and crashes? Using the built-in crash report? > Is there a checklist for testing or should I just use the system and > report issues? > Should I focus on specific features? > Are there any procedures or scripts to be followed? > > Thanks in advance. > Looking forward to hearing from you! > > Guilherme Nolasco > [email protected] > -- > Ubuntu-quality mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality > -- Ubuntu-quality mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
