<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Ryuken, thanks for the feedback. It can
feel overwhelming, but please any suggestions you may have as you
move through the knowledge transfer process please let us know :-)<br>
<br>
As far as your questions, I think the best and easiest way to
start is to run some testcases. You can choose to do image or
package tests. The package trackers have tests for every image and
all the default desktop packages for ubuntu and most flavors.<br>
<br>
<a class="moz-txt-link-freetext" href="http://iso.qa.ubuntu.com/">http://iso.qa.ubuntu.com/</a><br>
and<br>
<a class="moz-txt-link-freetext" href="http://packages.qa.ubuntu.com/">http://packages.qa.ubuntu.com/</a><br>
<br>
So for instance if you are running ubuntu, this is the page with
the list of package testcases for trusty:<br>
<a class="moz-txt-link-freetext" href="http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases">http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases</a><br>
<br>
Pick your favorite app, or simply something that hasn't yet been
tested. Let's say totem.<br>
<br>
<a class="moz-txt-link-freetext" href="http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases/1429/results">http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases/1429/results</a><br>
<br>
Read the testcase, execute it and report your results. If you find
a bug, report it :-) By helping with testing, try and plan on
running through these testcases a few times over the course of the
cycle and foaster any bugs you might find until they are fixed.
Does this make sense?<br>
<br>
After you've gone through the listed testcases, you can choose to
help by writing a test we don't currently have (look at the test
write role for that), or doing exploratory testing to look for
bugs (or anything else on the page :-) ). Exploratory testing
means you don't have a specific script to follow. Instead you are
looking at specific applications and trying to find bugs. It's
like a puzzle :-) Try and break the software. You'll find you get
better at it over time.<br>
<br>
Nicholas<br>
<br>
On 11/16/2013 11:41 AM, Phill Whiteside wrote:<br>
</div>
<blockquote
cite="mid:CAD5cqVh0MWOvjRaO77vF19n4r-iY-E8YGXr+6QyHnPp9zuy88Q@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>yes can be a bit overwhelming! Have a look at <a
moz-do-not-send="true"
href="https://wiki.ubuntu.com/QATeam/FAQ">https://wiki.ubuntu.com/QATeam/FAQ</a> which
I think breaks things down into more bite-sized chunks that
will not overload the brain!</div>
<div><br>
</div>
<div>If you have any suggestions as to how to make that area
better; you are the person best able to suggest things as you
seeking information and the idea behind that page is to be
able to answer your questions.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Phill.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 16 November 2013 16:33, Ryuken
Iwaski <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ryuken2@outlook.com" target="_blank">ryuken2@outlook.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="ltr">Hi,
<div><br>
</div>
<div>I checked the page <a moz-do-not-send="true"
href="https://wiki.ubuntu.com/QATeam/Roles/Tester"
style="font-size:12pt" target="_blank">https://wiki.ubuntu.com/QATeam/Roles/Tester</a> for
the testing. I also checked Nicholas's video for the
testing and learned few things. </div>
<div><br>
</div>
<div>However, being new to the testing activities makes
me a bit overwhelmed. So I read up on the software
testing lifecycle information from the wikipedia and
other sources. </div>
<div><br>
</div>
<div>So to start small at first, I wanted to know which
is the easiest task to start from to contribute? </div>
<div><br>
</div>
<div>e.g. Like writing test cases or like reporting bugs
or using defect reporting tool. </div>
<div><br>
</div>
<div>Just not sure what to do and where to start. </div>
<div><br>
</div>
<div>I appreciate any pointers to get me out of
information overload. </div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
--<br>
Ubuntu-quality mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ubuntu-quality@lists.ubuntu.com">Ubuntu-quality@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a
moz-do-not-send="true"
href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality"
target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<a moz-do-not-send="true" href="https://wiki.ubuntu.com/phillw"
target="_blank">https://wiki.ubuntu.com/phillw</a>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>