Home Home > Quality-assurance
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Archive for the ‘Quality Assurance’ Category

Call for openSUSE Core Test Team

July 24th, 2009 by

In addition to well-developed code, testing is a major part of ensuring a rock-solid openSUSE Linux distro. To make sure testing of openSUSE 11.2 (and beyond) are done in a well-organized way, we’re improving the way the openSUSE Core Test Team works together to ensure top quality for openSUSE.

In the next couple of days Milestone 4 of openSUSE 11.2 will be available. This is a very good moment to have a closer look into the next openSUSE release: some new features are already implemented and there is enough time to fix reported problems.

Thus we are looking for 15 members of the openSUSE Community that are willing to contribute to the openSUSE project by joining the openSUSE Core Test Team and operate in the following areas:

  • Check if new features are implemented and working as requested
  • Have a deeper look into the install and update system of openSUSE and ensure a broad hardware coverage
  • Creating, improving and executing test cases for various areas of the distribution

Repository for test cases and tracking system for all test results will be Testopia, the test case management extension of Novell’s Bugzilla. Members of the Core Test Team will get access to the openSUSE test plans and will so be able to contribute. Beside storing test results they are also able to create or modify test cases.

If you are really interested in joining the openSUSE Core Test Team and willing to spend a reasonable amount of time to move the openSUSE project forward please get in contact with Holger Sickenberg <holgi at suse.de> providing following information:

  • Your Linux experience
  • Previous testing experience, if any
  • Areas you are interested in testing

The number of members is limited to 15 at the moment to ensure we are able to adequate support everyone of them. We will add more once we’ve figured out in the smaller group whether everything works.

Of course everybody is still able to contribute to the openSUSE project by testing parts of the distribution. Enabling the openSUSE Core Test Team will not have any impact on that. Further information on testing is available at www.opensuse.org/Testing.

We are looking forward to your application. Deadline for applications is August, 15th 2009.

openSUSE-GNOME BugDay Weekend Wrapup

May 18th, 2009 by

As posted to the openSUSE-GNOME Mailing List.


Greetings!

Thanks to all who showed up to help on the bug day on
Friday, your efforts are greatly appreciated.

We started with just over 70 bugs and left the *obby
session available over the weekend.  By the end of the
weekend, we had reviewed 14 bugs (9 of which we closed).

These were all Critical and Major bugs listed for openSUSE
11.1.

I will be closing the *obby session this afternoon at about
1700 CDT.

Thanks again!

Christopher M. Hobbs [chobbs@siloamsprings.com]
Network Administrator, City of Siloam Springs

openSUSE-GNOME BugDay: “Community Effort”

May 14th, 2009 by

PSA sent to opensuse-gnome@opensuse.org, opensuse-project@opensuse.org, opensuse-announce@opensuse.org


Greetings!

Please join us for the openSUSE-GNOME BugDay code named “Community Effort” tomorrow
(Friday 14 MAY 2009) at 1100EDT/1500UTC.

We’ll be squashing blocker, critical, and major bugs in 11.1 related to GNOME.

More information can be found on the wiki:
http://en.opensuse.org/GNOME/BugDays/20090514

A Gobby session will be announced at the beginning of the meeting to assign/close
bugs. Should you have any questions, feel free to ask in #openSUSE-GNOME on Freenode,
or email me directly.

We hope to see you there!

Christopher M. Hobbs [chobbs@siloamsprings.com]
Network Administrator, City of Siloam Springs

ARM support in openSUSE Buildservice – fixed

April 27th, 2009 by

The issue caused by the OBS worker update on arm builds is fixed by a new qemu.

This new qemu version also has fixed the Fedora 10 @ ARM build problem.

So we have the following working ARM target distros available for ARM: Fedora 10, Debian 5.0 and Ubuntu 9.04.

Have fun.

How to search more efficiently in Bugzilla with pybugz

June 19th, 2008 by

If you just want to search for bugs in Bugzilla, it’s (a bit?) painful: start the browser, type in the URL, insert your login and password and try to find out where to go. There is an easier way to do: pybugz for commandline lovers!

Thanks to Peter Poeml, get this very useful Python script from here. After you have installed it you need only two steps to configure it:

  1. Create a file ~/.bzuser and insert your Bugzilla login.

  2. Login into Bugzilla and insert your password. This creates the file ~/.bugz_cookie:

    $ /usr/bin/bugz-login

The script knows several subcommands, its interface is similar to CVS or Subversion. You can search, get, post, modify, attach and download an attachment, all with this utility. For example, if you want all bugs about “XML”, regardless of the product or component, you just type:

$ bugz search xml

That gives the following output:

 * Using https://bugzilla.novell.com/
 * Searching for 'XML'
 [ deleted a lot of lines ]

Maybe you want to narrow your search for KDE and specific products? No problem, here is an example:

$ bugz search KDE --product="openSUSE 11.0"
 * Using https://bugzilla.novell.com/
 * Searching for 'KDE' with the following options:
 * product = ['openSUSE 11.0']
113512 kde-maintainers Firefox in KDE - Only Uses GNOME Programs
170055 dmueller Firefox sets desktop background for Gnome under KDE
176179 kde-maintainers User can't edit properties for default notifications under KDE Storage Media and entries disepeared !
203548 sbrabec workrave-kde is an empty applet by default
[... and many more ...]

Of course, if you know the bug number you can retrieve it with:

$ bugz get 378240

and it will list all the details of the bug. Very useful! I haven’t tried the other subcommands yet, but I think they are also very convenient.

There are many more things to discover. So, when was your last time searching for bugs? 🙂

openSUSE 11.0 and Vista Users (Poor souls): How’s Dual-booting?

June 4th, 2008 by

Stephan Kulow asked on the Factory mailinglist if anyone was dual-booting Windows Vista and openSUSE 11.0:

Both me and the reporter of bug 396444 have a broken vista
boot after RC1 instalation (I ignored the problem as I did
not boot vista since quite some time, so it could just as well
be broken with alpha0).

So I wonder if other's vista is still functional? Unless I
know what's causing this, this bug is one of those that will
delay 11.0, so please help me.

Since there weren’t many people on the mailinglist who were, if you do boot Vista and SUSE 11.0, with success or otherwise, please let us know on the opensuse-factory@opensuse.org mailinglist 😉

Help With Bug Hunting

May 20th, 2008 by

So far from what I’ve heard and seen, people really like the upcoming 11.0 release – yes it is now only a month away 🙂

To try and make sure it is even better come release date the guys and gals need good bugreports, and preferably not duplicate bugs. One handy tool for searching for your bug is Martin Vidner’s Bugzilla search tool. This has been formed into an OpenSearch plugin by the maestro that is Benji.

Basically all you need to do is head over to here and then select your search engine drop down menu and choose “Add openSUSE 11.0 Bug Search”. I have tried it in FireFox 2 and 3, but Konqueror should be pretty much the same.

Thanks to Martin and Benji for this lovely facility, and now there is no excuse for not filing correct bug reports 😉 Happy bug hunting.

UPDATE
Thanks again to Benji, he has corrected my mistake for adding the search option in Konqueror. Just do the following:
settings -> configure konqueror -> web shortcuts -> new
bnc search settings in konqueror