BTW the next thing I am going to do is an upgrade testcase. If you look at the ISO QA Tracker we don't actually HAVE a upgrade testcase. So I think we can make one for that:P
2012/9/29 Ho Wan Chan <[email protected]> > Thanks Kaj. > > I have already changed it to testcase format in > http://packages.qa.dev.stgraber.org/qatracker/milestones/225/builds/16300/testcases/1336/results. > Click on the testcase tab to actually see the testcase (you can't hand in > results:P) > > The final date of editing the testcase wiki page is 10/10/2012. Any final > changes will be made and I will import the testcase to the main ISO QA > Tracker before the RC testing begins. So then we can actually make sure the > test can be used in 12.10 cycle for testing. > > As in the wiki we need someone to continue write contents about graphics, > video and monitor setup. If anyone is interested just edit the wiki in > https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase > > Thank you all on the support. > > Regards, > Howard Chan (smartboyhw) > > > 2012/9/29 Kaj Ailomaa <[email protected]> > >> ** >> On Mon, 24 Sep 2012 17:36:48 +0200, Micah Gersten <[email protected]> >> wrote: >> >> On 09/24/2012 10:06 AM, Kaj Ailomaa wrote: >> >> On Thu, 20 Sep 2012 09:36:20 +0200, Ho Wan Chan >> <[email protected]><[email protected]>wrote: >> >> >> <snip> >> >> >> I think it will be a better idea to just let people who want to help >> with the testcase to edit the testcase in a wiki. So I created a wiki page >> https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase to >> let you all edit it. >> >> Actually it is the steps after installation is more important, so you >> can think about what we can add, e.g. audio testing, hardware testing... >> >> You may have a look at >> http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1434/results >> and >> http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1433/results >> and >> look at the examples. >> >> >> <snip> >> >> I think we should focus as little as possible on Ubuntu and Xubuntu >> specific test cases, i.e. things that we share with those two distros, as >> those are things that will be corrected without our help. >> We should keep our testcase economic, and mostly focused on the >> multimedia aspects. >> With whatever customization we do to the desktop, that should be tested >> too, of course. >> >> As I am not that involved in the desktop customization, I would gladly >> just focus on the multimedia test cases. >> Perhaps someone could look through the page and try to filter out >> anything that we don't need to test (for reasons stated above)? >> >> >> I would tend to disagree here; as Xubuntu has seen bad interaction >> between various programs in the past (that don't necessarily affect >> Ubuntu). It would be good for Studio to run (not create) the relevant >> Ubuntu and Xubuntu test cases to make sure that the shared functionality >> functions properly with the Studio set of apps. Of course, testers are >> free to test what they wish. >> >> Thanks, >> Micah >> >> >> I feel it is a goal for Ubuntu Studio to keep customization of the >> desktop and the system at a minimum, and only customize that which will >> somehow enhance multimedia production. >> At least manual testing should not require testing things that are >> identical on other platforms. >> Especially since we are quite undermanned, which is something I hope >> could change in the future. >> >> I made some editing to >> https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase, >> but it's still very much under construction. >> >> -- >> Ubuntu-Studio-devel mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel >> >> >
-- Ubuntu-Studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
