[Meego-qa] BoF MeeGo QA in SF conference - Meeting minutes

[Anssi.Takku at nokia.com]

Hi,

we had a MeeGo QA BoF at San Francisco conference: 
http://sf2011.meego.com/program/sessions/bof-meego-qa

There was 20-30 participants in the session. Time for the session was really short (40min). So, it was known that we can't do any miracles in that time but instead we can network and raise problem areas in current community QA activies.

We made a introduction round where every participant introduced him/herself, how he/she was related to MeeGo QA activities and what issues he/she finds currently problematic in community QA.

Here's a list of raised issues:

- public MeeGo 1.3 release QA activities are quite a mess at the moment 
- lack of communication => things don't seem to  happen
- lack of direction
- how to increse test automation with continuous integration
- not many participants in Bug Triages (developers missing)
- only one person focusing on security QA issues
- bug statuses aren't up-to-date (e.g. some developer might be fixing a bug but bug status haven't been changed => others won't know that the bug is under fixing)
- all QA processes are not understood by other development areas
- bugs found in test automation aren't fixed (stay open for months)
- automation team needs to build their own packages (takes a lot of extra time)
- releasing isn't doing any smoke testing (sometimes images that aren't even booting are passed to QA)
	* "When more and more devices are supported it will be hard to check that all are working"
	* automation should be used for this problem
- for a new comer from community it's hard to participate in QA. How to help?
	* check slides from conference presentation by Milosz and Martin:
	http://sf2011.meego.com/program/sessions/how-unleash-community-testers
- for UX components there exists no automated test sets like for core
- many bugzilla sw components don't have proper developers linked to them => bugs remain long open

If I got something wrong please correct me or if something is missing please add those.

Now we have a good list of problematic areas in QA which we can as a community start to solve.

Thanks for all participants!

~Anssi (zotte)