<!DOCTYPE html><html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style>
</head>
<body text="#000000" bgcolor="#FFFFFF">On Mon, 24 Sep 2012 17:36:48 +0200, Micah Gersten <micahg@ubuntu.com> wrote:<br><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex">
<div class="moz-cite-prefix">On 09/24/2012 10:06 AM, Kaj Ailomaa
wrote:<br>
</div>
<blockquote cite="mid:op.wk5awxg72rg3it@melete" type="cite">
<style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style>
On Thu, 20 Sep 2012 09:36:20 +0200, Ho Wan Chan
<a class="moz-txt-link-rfc2396E" href="mailto:smartboyhw@gmail.com"><smartboyhw@gmail.com></a> wrote:<br>
<div><br>
</div>
<div><br>
</div>
<div><snip> <br>
</div>
<blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px
solid; padding-left: 1ex">
<div><br>
</div>
<div>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 <a moz-do-not-send="true" href="https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase">https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase</a> to
let you all edit it.</div>
<div><br>
</div>
<div>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...</div>
<div><br>
</div>
<div>You may have a look at <a moz-do-not-send="true" href="http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1434/results">http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1434/results</a> and <a moz-do-not-send="true" href="http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1433/results">http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/23726/testcases/1433/results</a> and
look at the examples.</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
<div><snip></div>
<div><br>
</div>
<div>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.<br>
</div>
<div>We should keep our testcase economic, and mostly focused on
the multimedia aspects.</div>
<div>With whatever customization we do to the desktop, that should
be tested too, of course.</div>
<div><br>
</div>
<div>As I am not that involved in the desktop customization, I
would gladly just focus on the multimedia test cases.<br>
</div>
<div>Perhaps someone could look through the page and try to filter
out anything that we don't need to test (for reasons stated
above)?</div>
<br>
</blockquote>
<br>
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.<br>
<br>
Thanks,<br>
Micah<br>
</blockquote><div><br></div><div>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.</div><div>At least manual testing should not require testing things that are identical on other platforms.</div><div>Especially since we are quite undermanned, which is something I hope could change in the future.</div><div><br></div><div>I made some editing to https://wiki.ubuntu.com/QATeam/QuantalTestcaseUpdates/UbuntuStudioTestcase , but it's still very much under construction. </div></body></html>