Re: Writing manual tests

[Elfy]

On 24/07/14 04:16, Shrinivasan T wrote:

Friends.

This is Shrini from chennai.

I am exploring the manual test cases.

I have few queries.

1. There are tons of applications for ubuntu. Do we need to write test
cases for all?

or just for the applications reported here.
https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?field.tag=todo

Just for those that are reported as a bug.


2. For any desktop application, we can write hundreds of test case.
How many test cases we have to write?
Is it okey of we write for major features only?
Writing to cover major features is fine, if in future more is needed it 
can be added.

3. Why do we write manual test cases? Do we have people for doing these
written manual tests before every release? are we doing all the manual
tests for every release?
There are people who test against testcases specifically and there are 
people who run the dev version constantly who can do the same as they 
are workiing.


4. I am in ubuntu 12.04. Do I need to upgrade to latest development version
of ubuntu to write manual test cases?
The testcases are in general needed against the latest available version 
which does point to using the latest dev version, though you can do so 
with a virtual machine rather than upgrading your prod machine.

5. We add a number before each test case.

example: 1414_Deja-Dup

http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/files/head:/testcases/packages/

What are the numbers?
How to add a new number for a new test case?
You don't add the number - testcase admins will do that when we merge 
and sync your newly prepared testcase.




Thanks a lot.


Thanks for coming forward to help :)

Elfy

--
Ubuntu Forum Council Member
Xubuntu QA Lead


--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Writing manual tests

[Shrinivasan T]

Friends.

This is Shrini from chennai.

I am exploring the manual test cases.

I have few queries.

1. There are tons of applications for ubuntu. Do we need to write test
cases for all?

or just for the applications reported here.
https://bugs.launchpad.net/ubuntu-manual-tests/+bugs?field.tag=todo


2. For any desktop application, we can write hundreds of test case.
How many test cases we have to write?
Is it okey of we write for major features only?

3. Why do we write manual test cases? Do we have people for doing these
written manual tests before every release? are we doing all the manual
tests for every release?

4. I am in ubuntu 12.04. Do I need to upgrade to latest development version
of ubuntu to write manual test cases?

5. We add a number before each test case.

example: 1414_Deja-Dup

http://bazaar.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/trunk/files/head:/testcases/packages/

What are the numbers?
How to add a new number for a new test case?


Thanks a lot.

-- 
Regards,
T.Shrinivasan


My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com

Get CollabNet Subversion Edge : http://www.collab.net/svnedge
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Why not triaging confirmed bugs instead of new ones?

[Alberto Salvia Novella]

Brian Murray:
>  Given that the ability to set the importance of bug tasks is
>  restricted to a specific group of people I would first look at
>  importance and then at bug heat.

Alberto Salvia Novella:

Perhaps a good approach will be to set importances first for every
confirmed bug, then continue with the triaging; since this will warrant
to be spending every triaging piece of work in the most important things
first.


What comes out from these conversations is that it will be better to 
prototype and measure step by step rather than having a conversation 
about it without something palpable, specially being this process so 
interlaced that everyone will have a very different opinion about it.



Alberto Salvia Novella:
> If Launchpad could treat End Of Life bugs automatically I think it
> will be a great success.

I think this the exception from the above. It is just pretty clear, just 
by looking at:


 - The quantity of open bugs (http://tinyurl.com/25t3v6): 129308
 - The known quantity of bugs for the supported releases 
(http://tinyurl.com/l5dhlhc): 35333


The second is only the 27% of the first.

These numbers make evident that:

 - The quantity of open bugs (129308) is unmanageable for any team 
right now, even for discovering critical bugs.


 - The 73% of bugs have the potential of being End Of Life.

 - Automatizing the management of End Of Life bugs will make a huge 
difference in quality, even if the automation algorithm expires a few of 
them wrongly in the beginning.



Regards.


--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

ISO tracker URLs slightly messed up for trusty, be creative

[Adam Conrad]

As Nick pointed out[1], we're in the process of testing the 14.04.1
ISOs.  It's been noted that the tracker is producing broken URLs to
download those images.  If you just insert "trusty/" before the bit
with "daily" or "dvd", it should work fine.

For example:

http://cdimage.ubuntu.com/edubuntu/dvd/20140722.1/trusty-dvd-amd64.iso

Becomes:

http://cdimage.ubuntu.com/edubuntu/trusty/dvd/20140722.1/trusty-dvd-amd64.iso

Happy testing.

... Adam

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Trusty 14.04.1 Testing this week

[Jean-Baptiste Lallement]

Hi,

On 22/07/2014 17:55, Nicholas Skaggs wrote:

The first point release for trusty is releasing this week. This release
will be the default upgrade path for precise users. The upgrade path
from precise -> trusty is important. Help with testing the images as
well as upgrades is most appreciated.You will find builds appearing at
the link below shortly.

http://iso.qa.ubuntu.com/qatracker/milestones/318/builds


All the images are on the tracker now.
Note that all the flavors are LTS and need testing with a special 
attention to mythbuntu which missed the release last time.


Additionally the download links are currently wrong on the tracker, for 
LTS they should contain the name of the release.

For example, for ubuntu desktop amd64 the link on the tracker currently is:
http://cdimage.ubuntu.com/daily-live/20140722.2/trusty-desktop-amd64.iso
To get the right url insert trusty before /daily:
http://cdimage.ubuntu.com/trusty/daily-live/20140722.2/trusty-desktop-amd64.iso

Another example with lubuntu:
wrong: 
http://cdimage.ubuntu.com/lubuntu/daily-live/20140722.2/trusty-desktop-amd64.iso


correct: 
http://cdimage.ubuntu.com/lubuntu/trusty/daily-live/20140722.2/trusty-desktop-amd64.iso



JB.

--
Jean-Baptiste Lallement
irc: jibel

--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality