I promised to create summary on the topics discussed today in MeeGo QA Meeting 
under the topic of Takeaways from Dublin

What I did is that I grouped the discussion under the topics and added some 
"How to go forward" Proposals.

Architecture and QA Co-Operation
>From the logs:
07:13:05 <Toropainen> One item is that architect does not know about QA 
activities in detailed level.
07:13:55 <V-PV> Toropainen: Yes, I agree with this. Any proposals how to make 
the situation better?
07:14:08 <vilvo> also n900 hw adaptation team (Marko Saukko) initiated 
discussion to create core OS images, already on Friday
07:15:08 <Toropainen> QA awarness and different activities in QA should be 
brought to architects attentions. One possible way to do this is to arrange 
some sort of roadshow targetted to architects, sales slides (brief descriptions 
about different QA activities)
07:15:45 <May> Good ideas. Tommi.
07:15:54 <Mukesh> how about them becomming a part of these meetings
07:16:08 <tahvo> maybe test plan walk-through with program people - including 
architects?
07:16:50 <V-PV> These all sound good things to be done from my perspective.
07:17:01 <V-PV> Do architects have weekly IRC meetings?
07:17:14 <May> We used to review test plan with PM and engineering managers, 
but architects are seldom involved in those meetings.
07:17:21 <Toropainen> I dont know Mukesh, Basically good idea but these 
meetings are more or less practicalities and very specific items. Dont know if 
architects are interested on these and our message is not heard most probably.
07:17:34 <nitingarg> test plan walk thru with architects is a good idea
07:18:05 <Toropainen> I agree with nitingarg.
07:18:32 <V-PV> #idea Test Plans should be walked through with architects in 
future as a addition to PMs
07:18:57 <V-PV> I think atleast that we could start doing
How to go forward:
-       Let's talk with Architects how they should be involved in Test Plan 
reviews and hear their ideas
-       It would be great Vilvo and others from Core QA Team to continue 
discussion with N900 adaptation team to get testable Core Image done. This 
learning could be then utilized in other HWs as well (assumption)
-       IDEA: Should we actually have open "walkthough" sessions for test plans 
arranged?


Tools Further Development
>From the logs:
07:13:12 <vilvo> yes, lots of work to do. at least on tools area.
07:14:13 <May> Yes. A big gap about test case management tool.
07:14:33 <V-PV> vilvo: We definetly run out of time during the un-conference 
sesions in this area.
07:14:59 <tahvo> Unconference item for test management raised small debate and 
good discussion - and due to that we run out of time like vilvo said.
How to go forward:
-       May could publish the slide n:o 2 from your test management slides that 
you showed in Dublin so that we could start the discussion about tools 
landscape based on that.
-       The rest of tool issues were pretty "business as usual" and I think we 
can proceed on those in bugs.meego.com / mails / IRC


Test Automation tools needs to be available for Community (== Public OTS)
>From the logs:
07:20:03 <Mukesh> MeeGo UX auotmation and tools should be made availabe to 
community as soon as we can..
07:20:11 <Mukesh> the scripts are alerday there in public OBS
07:20:22 <Mukesh> we need th epublic OTS part up and running
07:20:23 <vilvo> Mukesh: would you please be a bit more specific on that?
07:21:12 <Mukesh> vilvo: we have publsihed the scripts in the public GIT and 
the RPM's to public OBS..
07:21:34 <Dimpy__> We published the rpms at 
http://download.meego.com/live/home:/dadhikar/Trunk_Testing
07:21:49 <Dimpy__> both for 1.1 and 1.2 releases.
How to go forward:
-       I think that definetly public OTS would be great service to be offered. 
Including support for QEMU testing and real HW testing, so that you can make 
your own build and run the tests you want.
-       Let's agree on intent first, if you see it another way that I just 
wrote, please comment.
-       For continuation, I see this something that I can not contribute, vilvo?

Did I missed some items?

V-PV
---
 Veli-Pekka Vatula
 MeeGo QA Lead



_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa

Reply via email to