- test openSUSE 11.3 or 11.2? - test 11.2 as long as buggy
- happy testing
- structuring testing: TestTopia
- next meeting
-  questions of any kind by team members
  
  
 1.)
 ...
 bmwiedemann: or we talk amongst ourselves a little. I have been reading the Testopia manual and found mention of a "Testers" group defining test-cases and assigning testers.
 bmwiedemann: that would probably the Testing Core Team (us)
 MrKane: Regarding xorg, how iss this functioning without an xorg.conf file?
 bmwiedemann: it creates xorg.conf on-the-fly
 elm: yes they have promised me to keep xorg.confs supported
 MrKane: SaX isn't hidden. It's just out of Yast.
 
 Holgi: hi
 bmwiedemann: good evening Holgi
 Holgi: right: my question with this topic is: do we want/are we able to do some structured testing with 11.2
 Holgi: bmwiedemann: like having a testplan
 badshah: but we have not really the time to do that for 11.2 do we
 Holgi: purpose of my question is: it's quite late to test 11.2 - so maybe it does not make sense
 Holgi: we are releasing
 elm: there should always be a way to resolve really annoying bugs
 Holgi: elm: no doubt
 badshah: Holgi: we have subteams, so maybe if we can up with plans for each subteams we can rapidly test accordingly during the next few days before rc2 is out
 elm: I don`t think we should stop testing 11.2 as long as we find important bugs.
 ReferenceSeete: I agree with elm.
 ReferenceSeete: We should test 11.2 through to GM
 
 2.)
 ReferenceSeete: MP3 playback is fine assuming one uses the normal routes (Packman or VLC repos)
 LWFinger: MrKane: I use Amarok for mp3 pplayback. Once I git the xinecodec installed, it works
 badshah: MrKane: I tested out the vlc, works for me
 [20:32] ReferenceSeete: Video is fine given what I have watched. (Xvid, Theora, WMV)
 Holgi: so conclusion: happy testing + have some experience with testopia?!
 MrKane: Anyone tested with proprietary GFX drivers?
 elm: the fglrx does not work yet
 elm: ... have posted that but as it seems amd still won`t care about RCx & perhaps even not about kernel updates
 MrKane: elm: then we need to get it in to the release notes. Many people need prop. drivers for games ++
 
 MrKane: holgi: is it an idea that you get http://bugzilla.opensuse.org to redirect correctly?
 bmwiedemann: http://bugs.opensuse.org/ works
 
 Holgi: LWFinger: how to deplay the testopia on a bugzilla system?
 Holgi: LWFinger: I have never done this - but the link is http://www.mozilla.org/projects/testopia/
 
 3.)
 MrKane: holgi: is the openSuse 11.2 Feature and openSUSE 11.2 Application Tests plans the only used for testing internally ?
 Holgi: MrKane: https://bugzilla.novell.com/tr_show_plan.cgi?plan_id=2355
 Holgi: MrKane: select the tab "Test Runs"
 Holgi: what is necessary to understand with testopia:
 Holgi: a testplan does contain a number of testcases
 Holgi: but results can just be entered within test runs
 Holgi: such a testrun either contains all testcases or a subset of testcases from the test plan
 Holgi: in case of the features we created testruns for every milestone/r
 badshah: Holgi: but we are not able to create new plans right yet?
 badshah: Holgi: ok, so we should just ask you for creating test plans for us, as soon as we have a plan right?
 Holgi: badshah: if there is a need for - so far I consider all testcases as part of the application tests
 Holgi: badshah: but for installation as an example, another plan would be good
 Holgi: badshah: keep in mind - you can create testruns with just a subset of testcases from a testplan
 badshah: Holgi: ok, thanks for the info
 MrKane: Can I have: "Testing zypper features" on Environment=X and another "Testing zypper features" on Environment=Y or must the runs have separate naming?
 Holgi: MrKane: they may have the same name, but a name mentioning the differences would be better
 MrKane: I think Insallation can be an area that is good to start on with Testopis. It's an important area for 11.3 early on and we all like our HW to work.
 jradzuweit: we could use a plan for each team
 Holgi: jradzuweit: I'm not sure if that is necessary, but yes I can create those
 badshah: jradzuweit: as you will see most of these plans might be already covered under application tests
 Holgi: but if that would help someone I'm willing to create those plans
 MrKane: Hmm.. I would like to create plans my self. Any reason we should not be allowed to do that?
 bmwiedemann: MrKane: you can create new test-Cases which is what is really needed
 jradzuweit: MrKane: agreed, HW is not really covered so far
 MrKane: Can a crated test case be usedd in any plan or is it "hardlinked" to one plan?
 badshah: bmwiedemann: you can add test-case to existing plans
 bmwiedemann: even attached to test-runs
 Holgi: badshah: and existing runs
 bmwiedemann: might be worthwhile... I heard, even microsoft polished usability with its latest release
 MrKane: Can a created test case be used in any plan or is it "hardlinked" to one plan?
 Holgi: MrKane: you can copy plans and also copy testcases to other plans
 Holgi: MrKane: and you can link test cases to plan
 Holgi: MrKane: linked testcase in testcase 2 will also be changed if you change it in testplan 1
 Holgi: MrKane: copied will not not change in testplan 2
 
 4.)
 bmwiedemann: I was thinking, that there should possibly be a very different meeting date/time for those who never could attend thursday evening meetings
 --- perhaps you could suggest another meeting date on the mailing list if you find it hard to attend meetings as they have been scheduled up to now ---
 elm: one week after RC2.
 bmwiedemann: yes, weekend would be cool.
 next meeting: 2009-10-31 1600 UTC
 
 5.)
 LWFinger: A separate question - What is gnome-do and what does it do?
 ReferenceSeete: LWFInger: gnome-do is essentially an application laucher
 ReferenceSeete: No, more like KRunner
 ReferenceSeete: If you know what app you'd like to run you can just pull up Gnome-Do and start typing the app's name
 badshah: LWFinger: you can also enable aditional plugins in do, and use it to browse, move, copy your files or take screenshots and lots of things.
 bugbot: openSUSE bug 540518 in openSUSE 11.2 (GNOME) "gnome-do uses all cpu time on my system" [Normal,Reopened] https://bugzilla.novell.com/540518
 LWFinger: badshah: Thanks - you saved me a Bugzilla search - they usually fail for me anyway.
 badshah: LWFinger: you're welcome. bugzilla search with the advanced searching works for me mostly, but the simple one usually does not
 
 
 
 
 
