[Meego-qa] MeeGo-qa Digest, Vol 6, Issue 23

Wed Mar 23 01:45:42 PDT 2011

Hi!

Where can I download test cases to testplanner for handset acceptance N900?

Thank you!!

On Wed, Mar 23, 2011 at 8:28 AM, <meego-qa-request at lists.meego.com> wrote:

> Send MeeGo-qa mailing list submissions to
>        meego-qa at lists.meego.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.meego.com/listinfo/meego-qa
> or, via email, send a message with subject or body 'help' to
>        meego-qa-request at lists.meego.com
>
> You can reach the person managing the list at
>        meego-qa-owner at lists.meego.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MeeGo-qa digest..."
>
>
> Today's Topics:
>
>   1. Re: Meego testing (jukka.eklund at nokia.com)
>   2. hci device failed to register with built image
>      (Yongbo.Wu at elektrobit.com)
>   3. Re: hci device failed to register with built image (Zhang, Jingke)
>   4. How about add to some test case in mrt-sanity-n900-test ?
>      (Yongbo.Wu at elektrobit.com)
>   5. Re: hci device failed to register with built image
>      (Yongbo.Wu at elektrobit.com)
>   6. Re: Meego testing (jake.kunnari at nokia.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Mar 2011 21:41:45 +0000
> From: <jukka.eklund at nokia.com>
> To: <sara.galisteo at qualitio.com>, <jake.kunnari at nokia.com>
> Cc: meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] Meego testing
> Message-ID:
>        <
> 74A1555BB1B84F4C9DBD5E9A3EF47111E48AF7 at 008-AM1MPN1-007.mgdnok.nokia.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests ?
>
> Thanks for your help, btw :)
>
> Jukka
>
> ________________________________
> From: meego-qa-bounces at lists.meego.com [meego-qa-bounces at lists.meego.com]
> on behalf of ext Sara Galisteo [sara.galisteo at qualitio.com]
> Sent: 22 March 2011 17:20
> To: Kunnari Jake (Nokia-MS/Helsinki)
> Cc: meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] Meego testing
>
> Hi!!
>
> I have already visit those links and I have the test environment prepared
> to start running the test cases. Could you provide me a git link which leads
> to N900 acceptance test cases?
>
> Thank you for your fast answer ;)
>
> On Tue, Mar 22, 2011 at 12:26 PM, <jake.kunnari at nokia.com<mailto:
> jake.kunnari at nokia.com>> wrote:
> Hi,
>
> About testing tools, please check this wiki-page:
> http://wiki.meego.com/Quality
>
> -jake-
>
> From: meego-qa-bounces at lists.meego.com<mailto:
> meego-qa-bounces at lists.meego.com> [mailto:meego-qa-bounces at lists.meego.com
> <mailto:meego-qa-bounces at lists.meego.com>] On Behalf Of ext
> Marko.T.Rajala at nokia.com<mailto:Marko.T.Rajala at nokia.com>
> Sent: 22 March, 2011 13:19
> To: sara.galisteo at qualitio.com<mailto:sara.galisteo at qualitio.com>;
> meego-qa at lists.meego.com<mailto:meego-qa at lists.meego.com>
> Subject: Re: [Meego-qa] Meego testing
>
> Hi!
>
> Great that you and your company are interested in testing meego .
>
> Current plans concerning DE 1.2 N900 can be found from this wiki:
> http://wiki.meego.com/ARM/N900/DeveloperEdition
>
> >From there you can see the most important use cases that we need to get
> working in 1.2 timeframe.
>
> Test results and already found/reported bugs you can check here:
> http://qa-reports.meego.com/1.2/Handset
> https://bugs.meego.com/
>
> For testing tools related questions I hope someone who knows those better
> providing answers. Can you be more specifig about what tools you mean?
>
> Regards,
> -Marko
>
>
> From: meego-qa-bounces at lists.meego.com<mailto:
> meego-qa-bounces at lists.meego.com> [mailto:meego-qa-bounces at lists.meego.com
> <mailto:meego-qa-bounces at lists.meego.com>] On Behalf Of ext Sara Galisteo
> Sent: 22 March, 2011 12:50
> To: meego-qa at lists.meego.com<mailto:meego-qa at lists.meego.com>
> Subject: [Meego-qa] Meego testing
>
> Who may concern,
>
> I am test engineer who is working for a testing company as internship. We
> would like to contribute to improve Meego applications and for this aim I
> have to my disposal a Nokia N900 device to test the Meego Handset features.
>
> First of all I would like to know what is the best way to help you, I would
> be very glad if you could tell me which part is the most interesting to test
> and if you could provide me information about the specifications of the
> features to test.
>
> About the testing tools, are you open to allow me to use your own tools?
> and in affirmative case, what should be the first time tester setup of those
> tools?
>
> I can be at your disposal to work with this issues from Monday to Friday
> during 7 hours a day, so to sum up please let me know what would be the best
> way to help you. If you have any question just ask me.
> Thank you very much for your attention.
>
> Yours faithfully,
>
> Sara Galisteo Mesa.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.meego.com/pipermail/meego-qa/attachments/20110322/74670ba3/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 23 Mar 2011 07:41:49 +0200
> From: <Yongbo.Wu at elektrobit.com>
> To: <meego-qa at lists.meego.com>
> Subject: [Meego-qa] hci device failed to register with built image
> Message-ID:
>        <
> 60EDCC9A759D6B40BAB87DD2EBA1727A0376BB8F at fioues07.ebgroup.elektrobit.com>
>
> Content-Type: text/plain;       charset="us-ascii"
>
>
> Hi all,
>
> I built an image with MIC and daily released ks file for N900.
>
> After booting up, it failed to detect hci device with "hcitool dev".
>
> more information:
>
> #hcitool dev
> Devices:
>
> #dmesg | grep hci
> [   11.199584] hci_h4p hci_h4p: Registering HCI H4P device
> [   23.655548] hci_h4p hci_h4p: Valid bluetooth address not found.
> [   23.655609] hci_h4p hci_h4p: FW error
> [   23.655639] hci_h4p hci_h4p: Sending firmware failed.
>
>
> any idea ? or is this a bug ?
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 23 Mar 2011 13:48:15 +0800
> From: "Zhang, Jingke" <jingke.zhang at intel.com>
> To: "Yongbo.Wu at elektrobit.com" <Yongbo.Wu at elektrobit.com>
> Cc: "meego-qa at lists.meego.com" <meego-qa at lists.meego.com>
> Subject: Re: [Meego-qa] hci device failed to register with built image
> Message-ID:
>        <
> F26D193E20BBDC42A43B611D1BDEDE71268C68C35A at shsmsx502.ccr.corp.intel.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hello, is your finding same as bug#12363?
> https://bugs.meego.com/show_bug.cgi?id=12363
>
>
> -----Original Message-----
> From: meego-qa-bounces at lists.meego.com [mailto:
> meego-qa-bounces at lists.meego.com] On Behalf Of Yongbo.Wu at elektrobit.com
> Sent: Wednesday, March 23, 2011 1:42 PM
> To: meego-qa at lists.meego.com
> Subject: [Meego-qa] hci device failed to register with built image
>
>
> Hi all,
>
> I built an image with MIC and daily released ks file for N900.
>
> After booting up, it failed to detect hci device with "hcitool dev".
>
> more information:
>
> #hcitool dev
> Devices:
>
> #dmesg | grep hci
> [   11.199584] hci_h4p hci_h4p: Registering HCI H4P device
> [   23.655548] hci_h4p hci_h4p: Valid bluetooth address not found.
> [   23.655609] hci_h4p hci_h4p: FW error
> [   23.655639] hci_h4p hci_h4p: Sending firmware failed.
>
>
> any idea ? or is this a bug ?
> _______________________________________________
> MeeGo-qa mailing list
> MeeGo-qa at lists.meego.com
> http://lists.meego.com/listinfo/meego-qa
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 23 Mar 2011 07:54:37 +0200
> From: <Yongbo.Wu at elektrobit.com>
> To: <meego-qa at lists.meego.com>
> Subject: [Meego-qa] How about add to some test case in
>        mrt-sanity-n900-test ?
> Message-ID:
>        <
> 60EDCC9A759D6B40BAB87DD2EBA1727A0376BB92 at fioues07.ebgroup.elektrobit.com>
>
> Content-Type: text/plain;       charset="us-ascii"
>
>
> Hi all,
>
> Curently there are only 37 test case in mrt-sanity-n900-test.
> But mannualy sanity testing result comes with 45, say
> http://qa-reports.meego.com/1.2/Core/Sanity/N900/1579.
>
> The gap is there for some cases are not suitable for auto testing, like
> "system bootup and shutdown".
>
> We are trying to remove the gap.
> so my idea is that complete the test cases in mrt-sanity-n900-test to 45
> with leaving some of them with no execute step and result N/A.
>
> By that we can have a more good view of auto test result, what OTS can
> do and what doesnt, and trying to fill the gap.
>
> Yongbo Wu
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 23 Mar 2011 07:58:40 +0200
> From: <Yongbo.Wu at elektrobit.com>
> To: <jingke.zhang at intel.com>
> Cc: meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] hci device failed to register with built image
> Message-ID:
>        <
> 60EDCC9A759D6B40BAB87DD2EBA1727A0376BB95 at fioues07.ebgroup.elektrobit.com>
>
> Content-Type: text/plain;       charset="us-ascii"
>
>
> yes, like that.
>
> More information: this bug is not produced with released image.
> my image is build with MIC2.
>
>
> Yongbo Wu
> MeeGo Core QA, META Technical Lead
>
> SW Engineer, MTS SW
> >EB - Discover the Experience
> Guo Sheng Sci-Tech Park, No.1 Kang Ding Street,
> BDA, Beijing, China 100176
> Tel +86 13911393395
> >www.elektrobit.com
>
> -----Original Message-----
> From: Zhang, Jingke [mailto:jingke.zhang at intel.com]
> Sent: 23 March 2011 13:48
> To: Wu Yongbo
> Cc: meego-qa at lists.meego.com
> Subject: RE: hci device failed to register with built image
>
> Hello, is your finding same as bug#12363?
> https://bugs.meego.com/show_bug.cgi?id=12363
>
>
> -----Original Message-----
> From: meego-qa-bounces at lists.meego.com
> [mailto:meego-qa-bounces at lists.meego.com] On Behalf Of
> Yongbo.Wu at elektrobit.com
> Sent: Wednesday, March 23, 2011 1:42 PM
> To: meego-qa at lists.meego.com
> Subject: [Meego-qa] hci device failed to register with built image
>
>
> Hi all,
>
> I built an image with MIC and daily released ks file for N900.
>
> After booting up, it failed to detect hci device with "hcitool dev".
>
> more information:
>
> #hcitool dev
> Devices:
>
> #dmesg | grep hci
> [   11.199584] hci_h4p hci_h4p: Registering HCI H4P device
> [   23.655548] hci_h4p hci_h4p: Valid bluetooth address not found.
> [   23.655609] hci_h4p hci_h4p: FW error
> [   23.655639] hci_h4p hci_h4p: Sending firmware failed.
>
>
> any idea ? or is this a bug ?
> _______________________________________________
> MeeGo-qa mailing list
> MeeGo-qa at lists.meego.com
> http://lists.meego.com/listinfo/meego-qa
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 23 Mar 2011 07:27:30 +0000
> From: <jake.kunnari at nokia.com>
> To: <sara.galisteo at qualitio.com>
> Cc: meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] Meego testing
> Message-ID:
>        <
> 9648F6626C45C24484DE3F463BC5B4A0035D1FD8 at 008-AM1MPN1-031.mgdnok.nokia.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Sara,
>
> Please take a look at this page: http://qa-reports.meego.com/1.2 it
> contains results of our test execution and from there you can find
> acceptance tests for different verticals.
>
> Br
> Jake
>
>
> From: ext Sara Galisteo [mailto:sara.galisteo at qualitio.com]
> Sent: 22 March, 2011 17:20
> To: Kunnari Jake (Nokia-MS/Helsinki)
> Cc: Rajala Marko.T (Nokia-MS/Tampere); meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] Meego testing
>
> Hi!!
>
> I have already visit those links and I have the test environment prepared
> to start running the test cases. Could you provide me a git link which leads
> to N900 acceptance test cases?
>
> Thank you for your fast answer ;)
> On Tue, Mar 22, 2011 at 12:26 PM, <jake.kunnari at nokia.com<mailto:
> jake.kunnari at nokia.com>> wrote:
> Hi,
>
> About testing tools, please check this wiki-page:
> http://wiki.meego.com/Quality
>
> -jake-
>
> From: meego-qa-bounces at lists.meego.com<mailto:
> meego-qa-bounces at lists.meego.com> [mailto:meego-qa-bounces at lists.meego.com
> <mailto:meego-qa-bounces at lists.meego.com>] On Behalf Of ext
> Marko.T.Rajala at nokia.com<mailto:Marko.T.Rajala at nokia.com>
> Sent: 22 March, 2011 13:19
> To: sara.galisteo at qualitio.com<mailto:sara.galisteo at qualitio.com>;
> meego-qa at lists.meego.com<mailto:meego-qa at lists.meego.com>
> Subject: Re: [Meego-qa] Meego testing
>
> Hi!
>
> Great that you and your company are interested in testing meego .
>
> Current plans concerning DE 1.2 N900 can be found from this wiki:
> http://wiki.meego.com/ARM/N900/DeveloperEdition
>
> >From there you can see the most important use cases that we need to get
> working in 1.2 timeframe.
>
> Test results and already found/reported bugs you can check here:
> http://qa-reports.meego.com/1.2/Handset
> https://bugs.meego.com/
>
> For testing tools related questions I hope someone who knows those better
> providing answers. Can you be more specifig about what tools you mean?
>
> Regards,
> -Marko
>
>
> From: meego-qa-bounces at lists.meego.com<mailto:
> meego-qa-bounces at lists.meego.com> [mailto:meego-qa-bounces at lists.meego.com
> <mailto:meego-qa-bounces at lists.meego.com>] On Behalf Of ext Sara Galisteo
> Sent: 22 March, 2011 12:50
> To: meego-qa at lists.meego.com<mailto:meego-qa at lists.meego.com>
> Subject: [Meego-qa] Meego testing
>
> Who may concern,
>
> I am test engineer who is working for a testing company as internship. We
> would like to contribute to improve Meego applications and for this aim I
> have to my disposal a Nokia N900 device to test the Meego Handset features.
>
> First of all I would like to know what is the best way to help you, I would
> be very glad if you could tell me which part is the most interesting to test
> and if you could provide me information about the specifications of the
> features to test.
>
> About the testing tools, are you open to allow me to use your own tools?
> and in affirmative case, what should be the first time tester setup of those
> tools?
>
> I can be at your disposal to work with this issues from Monday to Friday
> during 7 hours a day, so to sum up please let me know what would be the best
> way to help you. If you have any question just ask me.
> Thank you very much for your attention.
>
> Yours faithfully,
>
> Sara Galisteo Mesa.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.meego.com/pipermail/meego-qa/attachments/20110323/03ef285f/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> MeeGo-qa mailing list
> MeeGo-qa at lists.meego.com
> http://lists.meego.com/listinfo/meego-qa
>
>
> End of MeeGo-qa Digest, Vol 6, Issue 23
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-qa/attachments/20110323/f7a343c3/attachment-0001.html>