[Meego-qa] who is in charge of http://qa-reports.meego.com/1.2/Core/Hourly%20-%20Automated
ville.p.ilvonen at nokia.com
Tue Mar 29 00:00:04 PDT 2011
On 03/29/2011 09:49 AM, ext Yongbo.Wu at elektrobit.com wrote:
> thanks Timo.
> I tried that ks file to build image to boot n900, when trying "hci
> dev", it failed to detect any bluetooth device and return nothing.
> But test result of hourly-testing show that case "Core-Bluetooth
> scan" PASS.
We really haven't looked at MCTS internals but you can check execution
If you want to check how MCTS tests do it - please check
I don't know if they use hci dev or something else.
Lauri Pöyhönen (lapoyhon) and Sergey Timofeev (setimofe) promised to
start looking at MCTS tests at #meego-qa to get them more reliable and
those with bugs fixed.
> any special steps needed before executing the case ?
As said, not that Timo or me know. We provide tools for N900 hourly
automated testing. Let's see if we need to put our hands to tests as well :)
> -----Original Message----- From: Timo Härkönen
> [mailto:timo.harkonen at digia.com] Sent: 29 March 2011 13:45 To: Wu
> Yongbo Cc: meego-qa at lists.meego.com Subject: Re: [Meego-qa] who is in
> charge of
> On Tue, 2011-03-29 at 06:33 +0300, Yongbo.Wu at elektrobit.com wrote:
>> Hi all,
>> I wanna know how image is build for this hourly-testing ? exactlly,
>> I mean the ks file used for building.
>> I am using ks file like : pastebin.com/eMdJh8N2 with localy build
>> image to boot N900, BT driver failed to load. But "Hourly testing"
>> come with BT related result "PASS".
>> So I have to check how "Hourly testing" team build image ?
> The hourly testing is done by QA tools team. The setup still needs
> some fine tuning and there's some problems with the tests (mcts guys
> are fixing those).
> _______________________________________________ MeeGo-qa mailing
> list MeeGo-qa at lists.meego.com
More information about the MeeGo-qa