<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/25/2014 12:42 PM, Elfy wrote:<br>
</div>
<blockquote cite="mid:5381C927.50909@btinternet.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi Everyone,<br>
<br>
So I started looking at the packages for the various metas and the
list of bugs already created for testcases.<br>
<br>
Now, the majority of the applications used for the metas don't
mean a great deal to me. I <i>think</i> I've got the bulk of them
using apt-cache show and synaptic ;) but I am in no doubt that
things will be missing, there that don't need to be. You get the
picture.<br>
<br>
What I'd really like is for people to check the wiki [1] I created
for a few things. <br>
<br>
1 - do apps with testcase bug missing NEED one - if so please
create a suitable bug ( a link to the right place is on the wiki)<br>
2 - if there is an app on the list - that DOESN'T need a testcase
- please remove it from the list<br>
3 - do apps that have a bug - NEED one - if they don't please mark
the bug INVALID - if you can't then let me know<br>
<br>
Next - we'll need to try and set some sort of priority for them
all. <br>
<br>
I can't do that.<br>
<br>
<b>Writing testcases</b><br>
<br>
This is the crux of the issue, we can create all the lists we
want, we can create the tracker - but without the testcases that
is all completely pointless.<br>
<br>
What I would like to know is who can help to write them, they
aren't particularly complicated to write - but they do need a
knowledge of the application - I could write a testcase for each
one in an hour or so - but all you'd be checking is does it start
- does it close :)<br>
<br>
So - if you'd like to get involved with pushing this forward -
and, like me have always wondered how you can contribute as you're
not a coder, then <b>now</b> is your chance.<br>
<br>
It will be a fair bit of work to get them written - but it can be
done. <br>
<br>
If that is <i>you, </i>reply to this mail and we can make a
start. <br>
<br>
If there is a need to do so I can run a quick IRC session on the
basics of what you'll need to know. <br>
<br>
Any questions feel free to ask.<br>
<br>
Regards<br>
<br>
Elfy<br>
<br>
[1] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://wiki.ubuntu.com/UbuntuStudio/TestingTeamPage/Testcases">https://wiki.ubuntu.com/UbuntuStudio/TestingTeamPage/Testcases</a><br>
<pre class="moz-signature" cols="72">--
Ubuntu Forum Council Member
Xubuntu QA Lead</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Hi Elfy,<br>
<br>
I hope I can be one of the helping hands here. But as I am pretty
new to doing music stuff with Linux, I hope to use the exercise of
doing test cases to get to know the Ubuntu Studio applications. This
will be combined with a bit of bug triaging, which also helps to
identify use cases that could be test cases (some bug reporters also
have unusual use cases which will be ignored for now ;-) ).<br>
<br>
As a first step I have added Audacious to the list of Test Cases. I
found a bug requesting a test case, which is "Fix Released", but it
does not appear in the qatracker yet. The bug pointed me to the
relevant lp branch for the test suite, and I was able to work
through it. I would like to expand the test suite with two more test
cases (playing a midi file & playing a CD).<br>
<br>
So I suppose I should submit a new bug against ubuntu-manual-tests
asking for the extra test cases, and then I could merge the existing
one to my own branch & begin working on it?<br>
<br>
Regards,<br>
<br>
Ross <br>
<br>
<br>
</body>
</html>