Ubuntu-qa Digest, Vol 37, Issue 3

Rakesh.R rakeshtvla at gmail.com
Tue Nov 23 18:20:15 UTC 2010


On 11/23/10, ubuntu-qa-request at lists.ubuntu.com
<ubuntu-qa-request at lists.ubuntu.com> wrote:
> Send Ubuntu-qa mailing list submissions to
> 	ubuntu-qa at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
> or, via email, send a message with subject or body 'help' to
> 	ubuntu-qa-request at lists.ubuntu.com
>
> You can reach the person managing the list at
> 	ubuntu-qa-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ubuntu-qa digest..."
>
>
> Today's Topics:
>
>    1. Recommendations in the Launchpad Results Tracker (Marc Tardif)
>    2. VFD display with Ubuntu (Khairul Aizat Kamarudzzaman)
>    3. Ubuntu QA Meeting tomorrow, 17th Nov. at 1700UTC
>       (Jean-Baptiste Lallement)
>    4. Re:  How to contribute to Ubuntu (Jean-Baptiste Lallement)
>    5. Re: Interpreting test results across test runs (Marc Tardif)
>    6. Packages to investigate (Brian Murray)
>    7. Natty Desktop Testing / Test cases automation
>       (Jean-Baptiste Lallement)
>    8. Introducing Products (Emmet Hikory)
>    9. Re: Introducing Products (Tim Gardner)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 10 Nov 2010 10:21:16 -0500
> From: Marc Tardif <marc at interunion.ca>
> Subject: Recommendations in the Launchpad Results Tracker
> To: ubuntu-qa at lists.ubuntu.com
> Message-ID: <20101110152116.GD5254 at jrrr.montreal>
> Content-Type: text/plain; charset=us-ascii
>
> Hi folks,
>
> In order to encourage the community to perform more testing with the advent
> of the Launchpad Results Tracker, I was thinking it might be useful to
> include the concept of recommendations as popularized by Amazon. So, when
> someone has submitted test results for one or more projects, the Tracker
> could recommend other projects which might be of interest based on other
> people's testing.
>
> One requirement would be to provide recommendations real time as opposed
> to processing the data periodically. So, as soon as a person submits test
> results, the recommendations would be updated immediately. The motivation
> is that people will be looking at their test results immediately after
> submitting them rather than the day after.
>
> Ultimately, the objective is to hold on to testers and keep them
> interested, so your comments and other ideas are most welcome!
>
> --
> Marc Tardif <marc.tardif at canonical.com>
> Freenode: cr3, Jabber: cr3 at jabber.org
> 1024D/72679CAD 09A9 D871 F7C4 A18F AC08 674D 2B73 740C 7267 9CAD
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 12 Nov 2010 15:31:08 +0800
> From: Khairul Aizat Kamarudzzaman <khairul at bis-asiapac.com>
> Subject: VFD display with Ubuntu
> To: <ubuntu-qa at lists.ubuntu.com>
> Message-ID: <C9030E3C.9113%khairul at bis-asiapac.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I've try to attach the VFD display to Ubuntu desktop but it doesn?t work.
> Could u please suggest to us what brand n model of VFD display is supported
> by Ubuntu. We using Ubuntu for our POS system. We manage to configure the
> touch screen display + cash drawer and receipt printer.
>
> It would be great if Canonical can recommend us the hardware suite for Point
> of Sales using Ubuntu.
>
> Could u please check for us either VFD 450e can work with Ubuntu using
> serial port since the driver provided is for Windows only?
>
>
> Regards,
>
> Khairul Aizat Kamarudzzaman
> Business Development Manager
> khairul at bis-asiapac.com
> +6016.205.9950
> www.bis-asiapac.com
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://lists.ubuntu.com/archives/ubuntu-qa/attachments/20101112/929cf425/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Tue, 16 Nov 2010 14:20:58 +0100
> From: Jean-Baptiste Lallement <jean-baptiste at ubuntu.com>
> Subject: Ubuntu QA Meeting tomorrow, 17th Nov. at 1700UTC
> To: ubuntu-qa at lists.ubuntu.com
> Message-ID: <4CE2853A.4030404 at ubuntu.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi All,
>
> Tomorrow, November 17th at 1700UTC, we have our regular quality meeting
> at #ubuntu-quality. The agenda will be:
>
>  * review previous action items (all)
>  * SRU Report -- jibel
>  * Bugday -- pedro_
>  * Blueprints review -- marjo
>  * Reconsider meeting times again -- jibel
>  * Update list of people who can edit the channel topic -- fader
>  * Selection of new chair -- jibel
>
> If you have more topics you'd like to talk about, add it to the agenda
> at https://wiki.ubuntu.com/QATeam/Meetings .
>
> Thanks and see you all tomorrow.
>
> --
> Jean-Baptiste
> irc: jibel
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 16 Nov 2010 15:55:23 +0100
> From: Jean-Baptiste Lallement <jean-baptiste at ubuntu.com>
> Subject: Re:  How to contribute to Ubuntu
> To: Hakim Sheriff <hakimsheriff at gmail.com>
> Cc: ubuntu-qa at lists.ubuntu.com
> Message-ID: <4CE29B5B.9040000 at ubuntu.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 11/13/2010 04:22 AM, Hakim Sheriff wrote:
>> Hi,
> Welcome Hakim,
>
>> I was was told I had to send a message with my goals and interests so
>> here they are:
>>
>> I want to help Ubuntu and help it develop because I think it is awesome
>> and it is awesome that it is free.
>> That's pretty much it.
> If not already done, you can read our website [1]. It contains a set of
> activities you can perform to help Ubuntu and become an active community
> member.
>
> If you're more interested in QA activities you can read our wiki page
> [2] and our website [3].
>
>
> [1] http://www.ubuntu.com/community/get-involved
> [2] https://wiki.ubuntu.com/Testing
> [3] http://qa.ubuntu.com/testing/
>
> --
> Jean-Baptiste
> irc: jibel
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 16 Nov 2010 15:01:23 -0500
> From: Marc Tardif <marc at interunion.ca>
> Subject: Re: Interpreting test results across test runs
> To: Zygmunt Krynicki <zygmunt.krynicki at canonical.com>
> Cc: ubuntu-qa at lists.ubuntu.com
> Message-ID: <20101116200123.GI2087 at jrrr.montreal>
> Content-Type: text/plain; charset=us-ascii
>
> * Zygmunt Krynicki <zygmunt.krynicki at canonical.com> [2010-11-12 00:02
> +0100]:
>> W dniu 03.11.2010 17:22, Marc Tardif pisze:
> [snip]
>> > My question is: can we make any reasonable assumptions about the tests
>> > that were not run? This can be a matter of opinion where one extreme
>> > might not make any assumptions at all, whereas another extreme might
>> > assume that test results remain the same until proven otherwise. So,
>> > I'm calling for your opinions on what you consider is reasonable.
>>
>> Unless you have reliable information on how to handle such condition in
>> the test case meta data *and* can sufficiently guarantee that the
>> meda-data is accurate and up-to-date then you should do very little more
>> than notify the user that the particular test was not run (or not
>> present in the test result data, I don't know how you handle that part).
>
> I'm not so much concerned about implementation details, so please disregard
> any "handling" part. My question is purely conceptual when interpreting
> test results across multiple test runs. I'm simply wondering what kind of
> assumptions are reasonable in order to represent this information in a way
> that matches user expectations.
>
> Chris Gregan and his team, Massimo in particular, are particularly prone
> to this use case where only running a single test should essentially
> inherit the results from the previous test run. This is probably a side
> effect of having to run manual tests because it's very resources intensive
> to run all the tests again.
>
> In additioni to this use case, I believe that this is actually quite common
> when running automated unit tests. For example, if I just run the tests for
> a particular module, I think it's perfectly reasonable to assume that all
> the other tests still have the same results until proven otherwise, ie
> until running the whole test suite again.
>
> Furthermore, I also think it's helpful to make this assumption that test
> results remain the same until proven otherwise when reporting test results.
> When I look at a project, I want to see the all the latest test results
> even though they might not have all run at the same time.
>
> --
> Marc Tardif <marc.tardif at canonical.com>
> Freenode: cr3, Jabber: cr3 at jabber.org
> 1024D/72679CAD 09A9 D871 F7C4 A18F AC08 674D 2B73 740C 7267 9CAD
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 22 Nov 2010 13:22:22 -0800
> From: Brian Murray <brian at ubuntu.com>
> Subject: Packages to investigate
> To: Ubuntu QA <ubuntu-qa at lists.ubuntu.com>,	Ubuntu BugSquad
> 	<ubuntu-bugsquad at lists.ubuntu.com>
> Message-ID: <20101122212222.GU7786 at murraytwins.com>
> Content-Type: text/plain; charset="us-ascii"
>
> As we all know there are a lot of packages and bugs to keep track of in
> Ubuntu.  One idea that occurred to me recently, to help identify
> packages in need of triage, was to calculate an average bug heat for the
> particular package.  I've made a first pass at this using all the
> packages in the ubuntu-desktop package set.  Here are the top 10
> packages:
>
> usb-modeswitch-data - median: 764, mode: 1448
> language-pack-gnome-fa-base - median: 408, mode: 408
> language-pack-gnome-pt - median: 318, mode: 318
> couchdb-glib - median: 210, mode: 210
> netbook-meta - median: 145, mode: 408
> pyopenssl - median: 136, mode: 259
> shotwell - median: 124, mode: 6
> appmenu-gtk - median: 122, mode: 408
> gnome-python-extras - median: 114, mode: 3
> telepathy-gabble - median: 104, mode: 49
>
> As I ran this last Friday there might be some variance in the numbers.
> I'm curious whether or not you think the bug reports for these packages
> really need reviewing.
>
> Thanks,
> --
> Brian Murray
> Ubuntu Bug Master
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: Digital signature
> Url :
> https://lists.ubuntu.com/archives/ubuntu-qa/attachments/20101122/ed32f2ed/attachment-0001.pgp
>
> ------------------------------
>
> Message: 7
> Date: Tue, 23 Nov 2010 14:36:52 +0100
> From: Jean-Baptiste Lallement <jean-baptiste at ubuntu.com>
> Subject: Natty Desktop Testing / Test cases automation
> To: ubuntu-qa at lists.ubuntu.com
> Message-ID: <4CEBC374.9010905 at ubuntu.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi all,
>
> One of the QA goal for Natty is to increase the number of automated test
> cases and find cases that are failing. The tests cover the  applications
> installed by default in Natty, the integration with Unity  and the
> fallback desktop environment.
>
> The list of applications installed by default in Natty is available at
> [1] We will start by covering applications with priority 1 (highest) but
> all the apps installed by default need to be covered. If you want to add
> an application that is not in the list and are committed to write a test
> case for it then add a new line to the list.
>
> The priority is also to find test cases which fails when it shouldn't.
> There is a set of test cases for the applications available at [2] If
> there is no candidate to automation in this list, then be creative and
> add one to [3]
>
> What you need to do:
> 1. Choose applications in [1] for which you'd like to write automated tests.
> 2. Checkout mago [4] and the associated helper tool magomatic [5].
> 3. Read the fine documentation [6]
> 4. When you have automated a test case, commit, push and ask for a
> review of your branch. Once reviewed, it will be added to the next run.
> 5. The results are published here:
> http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
>
> Don't hesitate to ping me on #ubuntu-testing if you need help with
> anything related to this topic.
>
> Thanks to all of you who have already provided automated tests.
>
> [1] https://wiki.ubuntu.com/QATeam/NattyTestPlan/AppList
> [2] http://people.canonical.com/~j-lallement/natty/testcases/
> [3] http://testcases.qa.ubuntu.com
> [4] lp:mago
> [5] lp:magomatic
> [6] http://mago.ubuntu.com/
>
>
> --
> Jean-Baptiste
> irc: jibel
>
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 23 Nov 2010 03:02:02 +0900
> From: Emmet Hikory <persia at ubuntu.com>
> Subject: Introducing Products
> To: Ubuntu Developer Announcements
> 	<ubuntu-devel-announce at lists.ubuntu.com>
> Cc: Ubuntu Quality Assurance <ubuntu-qa at lists.ubuntu.com>
> Message-ID:
> 	<AANLkTin0msg1mGKbPJ=e0xXk02rA3ik_03si=_RaEhnq at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
>     In the testing team, we've been using the concept of "product" for
> some time, to better identify the artifacts that capture our
> attention, but I am unsure that this concept has been shared with the
> wider development community.
>
> ? ?A product is an image containing some portion of Ubuntu software,
> targeted for some specific installation environment, and released
> following our release management processes. ?Some examples of our
> current products include:
>
> Ubuntu Desktop Live i386
> Ubuntu Server Alternate amd64
> Kubuntu Desktop Live powerpc
> Ubuntu Netbook Preinstalled armel+omap3
>
> ? ?In an attempt to better manage our products, and ensure that each
> product is well tested and well supported, a more formal means of
> tracking products is being established, so that each product must be
> deliberately selected by some team willing to commit to the validation
> and certification processes, consisting of those who have both the
> necessary hardware and familiarity with the software to provide
> effective testing; and each product must have a nominated product
> manager.
>
> ? ?Towards that end, each flavour team should consider which
> installation targets they wish to support, and identify a product
> manager who will be available as a contact for the release team to
> provide confirmation of the completion of milestone validations and
> release approval for each product. ?Depending on the internal
> organisation of any specific flavour team, these product managers
> might be part of the development team, part of the testing team, or
> part of a management team. ?In all cases, the nominated product
> managers should have access to the installation environment towards
> which their product is targeted.
>
> ? ?Those interested in following the specifics of the implementation
> are encouraged to subscribe to the relevant specification (1), which
> will be used for the tracking of the implementation.
>
> ? ?I will be contacting each flavour team in the near future to
> discuss the available installation targets and the set of products to
> be released with Ubuntu 11.04. ?Once complete, the set of images
> produced will be limited to only include those for which product
> managers have been nominated.
>
> 1:
> https://blueprints.launchpad.net/ubuntu/+spec/other-qa-n-testing-different-architectures
>
> --
> Emmet HIKORY
>
>
>
> ------------------------------
>
> Message: 9
> Date: Tue, 23 Nov 2010 11:23:04 -0500
> From: Tim Gardner <tim.gardner at canonical.com>
> Subject: Re: Introducing Products
> To: Emmet Hikory <persia at ubuntu.com>
> Cc: ubuntu-devel-discuss at lists.ubuntu.com,	Ubuntu Developer
> 	Announcements <ubuntu-devel-announce at lists.ubuntu.com>,	Ubuntu Quality
> 	Assurance <ubuntu-qa at lists.ubuntu.com>
> Message-ID: <4CEBEA68.8090705 at canonical.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 11/22/2010 01:02 PM, Emmet Hikory wrote:
>> In the testing team, we've been using the concept of "product" for
>> some time, to better identify the artifacts that capture our
>> attention, but I am unsure that this concept has been shared with
>> the wider development community.
>>
>> A product is an image containing some portion of Ubuntu software,
>> targeted for some specific installation environment, and released
>> following our release management processes.  Some examples of our
>> current products include:
>>
>> Ubuntu Desktop Live i386 Ubuntu Server Alternate amd64 Kubuntu
>> Desktop Live powerpc Ubuntu Netbook Preinstalled armel+omap3
>>
>> In an attempt to better manage our products, and ensure that each
>> product is well tested and well supported, a more formal means of
>> tracking products is being established, so that each product must be
>> deliberately selected by some team willing to commit to the
>> validation and certification processes, consisting of those who have
>> both the necessary hardware and familiarity with the software to
>> provide effective testing; and each product must have a nominated
>> product manager.
>>
>> Towards that end, each flavour team should consider which
>> installation targets they wish to support, and identify a product
>> manager who will be available as a contact for the release team to
>> provide confirmation of the completion of milestone validations and
>> release approval for each product.  Depending on the internal
>> organisation of any specific flavour team, these product managers
>> might be part of the development team, part of the testing team, or
>> part of a management team.  In all cases, the nominated product
>> managers should have access to the installation environment towards
>> which their product is targeted.
>>
>> Those interested in following the specifics of the implementation are
>> encouraged to subscribe to the relevant specification (1), which will
>> be used for the tracking of the implementation.
>>
>> I will be contacting each flavour team in the near future to discuss
>> the available installation targets and the set of products to be
>> released with Ubuntu 11.04.  Once complete, the set of images
>> produced will be limited to only include those for which product
>> managers have been nominated.
>>
>> 1:
>> https://blueprints.launchpad.net/ubuntu/+spec/other-qa-n-testing-different-architectures
>>
>>  -- Emmet HIKORY
>>
>
> I like your proposal. In the past, due to the somewhat chaotic ARM
> planning process, the kernel team has spent time and energy on ARM
> branches for platforms that nobody has actually used. We have since
> retired some ARM branches as obsolete and unmaintained.
>
> rtg
> --
> Tim Gardner tim.gardner at canonical.com
>
>
>
> ------------------------------
>
> --
> Ubuntu-qa mailing list
> Ubuntu-qa at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
>
>
> End of Ubuntu-qa Digest, Vol 37, Issue 3
> ****************************************
>

-- 
Sent from my mobile device

<a href='http://needasig.com'><img src='http://needasig.com/NBzyV.png'/></a>




More information about the Ubuntu-qa mailing list