New to Testing, Which is the best way to start contributing?

[Nicholas Skaggs]

I would also chip in, come say hi when you are trying to test!

http://webchat.freenode.net/?channels=ubuntu-quality

There are folks on IRC with good coverage for most timezones. Say hello 
and get realtime feedback and help on your testing efforts!

Nicholas

On 11/18/2013 11:16 AM, Nicholas Skaggs wrote:
> 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 :-)
>
> 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.
>
> http://iso.qa.ubuntu.com/
> and
> http://packages.qa.ubuntu.com/
>
> So for instance if you are running ubuntu, this is the page with the 
> list of package testcases for trusty:
> http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases
>
> Pick your favorite app, or simply something that hasn't yet been 
> tested. Let's say totem.
>
> http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55993/testcases/1429/results
>
> 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?
>
> 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.
>
> Nicholas
>
> On 11/16/2013 11:41 AM, Phill Whiteside wrote:
>> Hi,
>>
>> yes can be a bit overwhelming! Have a look at 
>> https://wiki.ubuntu.com/QATeam/FAQ which I think breaks things down 
>> into more bite-sized chunks that will not overload the brain!
>>
>> 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.
>>
>> Regards,
>>
>> Phill.
>>
>>
>> On 16 November 2013 16:33, Ryuken Iwaski <ryuken2 at outlook.com 
>> <mailto:ryuken2 at outlook.com>> wrote:
>>
>>     Hi,
>>
>>     I checked the page
>>     https://wiki.ubuntu.com/QATeam/Roles/Tester for the testing. I
>>     also checked Nicholas's video for the testing and learned few
>>     things.
>>
>>     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.
>>
>>     So to start small at first, I wanted to know which is the easiest
>>     task to start from to contribute?
>>
>>     e.g. Like writing test cases or like reporting bugs or using
>>     defect reporting tool.
>>
>>     Just not sure what to do and where to start.
>>
>>     I appreciate any pointers to get me out of information overload.
>>
>>
>>     Thanks
>>
>>
>>
>>     --
>>     Ubuntu-quality mailing list
>>     Ubuntu-quality at lists.ubuntu.com
>>     <mailto:Ubuntu-quality at lists.ubuntu.com>
>>     Modify settings or unsubscribe at:
>>     https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>>
>>
>>
>>
>> -- 
>> https://wiki.ubuntu.com/phillw
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-quality/attachments/20131118/c475da01/attachment.html>