Hi Vojtěch, I think for now the following steps are useful - subscribe to opensuse-factory to follow the discussion of the dev-team, if you haven't done already. - just try to run the tests from the testtopia, just follow them word-by-word to see if they would work or if there is something missing or if they are untestable. All the stuff holgi supplied so far is to give the core testing team a starting point. I think we all don't know where the journey of core testing will take us. Jürgen Am Mittwoch, 16. September 2009 19:03:59 schrieb Vojtěch Zeisek:

Hello, few days ago Holger asked for some discussion of future work of openSUSE Core Testing Team, but I have not received any message regarding this topic. Well, I'm not professional software tester, so I would appreciate some introduction or short how to from someone more skilled. According to Holger's first mail, where he welcomed us in the team he mentioned "What I personally do expect from the new openSUSE Testing Core is not mainly executing test cases. From my point of view the team is responsible to decide what to test and how to test. This can be done by creating test plans containing test cases either developed by the developers itself or members with good knowledge in that specific area. Good contact to the development teams would for sure support that." It sounds good, but it does not say to me, where and how to start. I'm afraid because of great time shift between Europe and America we are not able to meet in #opensuse-testing IRC channel. I'm not absolutely sure what is difference between https://bugzilla.novell.com/tr_show_run.cgi?run_id=19162 and https://bugzilla.novell.com/tr_show_run.cgi?run_id=19163 - it is for different versions, yes, but I mean in basic idea. After short experimentation I hope I'm familiar with this technology, but short how to would be nice. :-) Finally, here is my basic idea ("the null hypothesis") how to start work of openSUSE Core Testing Team. I try to start the discussion, not to make exact plane of the work. Everyone of us is interested in different areas (I suppose), so let's divide the field of all applications. For example I use KDE, I like its graphical software (digiKam, ...), I use, I'd say, "scientific" applications (R, Kile, ...) and I run a LAMP server. So I would test basically this class of applications. And like this we can divide whole distribution. Some groups, like games :-), might be wished by more people, but I hope we will be able to cover whole field. I hope everyone of us has some deeper knowledge about his favorite applications, so he can say what should be tested, what might be problematic, what is important and so on. I have sens our role should be partially coordinating the testing, shouldn't it? Is it usable basic idea? In Testopia we can then create plans similar to those for YaST (already presented). It can be the coordinating place, right? But who will follow the plans we make in Testopia? Only our group plus developers? Finally, I hope our team will help openSUSE to be the best Linux distribution.

:-)

Have a nice day, Vojtěch Zeisek

-- ------------------------------------------------------ Jürgen Radzuweit Am Steinebrück 23 40589 Düsseldorf Telefon : 0211/788 5115 Mobil : 0172/210 4989 EMail : juergen@radzuweit.eu -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org