Kubuntu Laptop Testing

[Stephan Hermann]

On Sunday 02 July 2006 16:37, Matthew Garrett wrote:
> On Sun, Jul 02, 2006 at 03:42:44PM +0200, Stephan Hermann wrote:
> > Sure, but it's there...and if we have those special things in KDE or
> > in any other desktop flavour, we need to be sure, that it doesn't
> > clash with the underlaying technology.
>
> The answer to "Our desktop has this pile of gash that doesn't integrate
> with the rest of the system and does things differently" is not "WE MUST
> TEST THIS", it's "We should fix it so it integrates with the rest of the
> system".

If nobody is testing it, there won't be anything to fix. I never said: "Test 
it on all machines", but "test it on all desktop flavours".

> > Well, I can test the underlaying functionality most of the time without
> > any desktop environment...no problem. But what would that give us, if
> > it's not working on any desktop?
>
> So test it. Once. On one machine. That's all that's necessary.
>
> Or, to put it differently:
>
> We *need* to test basic functionality on every machine. We *do not need*
> to test desktop functionality on every machine.

That's what we want..nothing else.

>
> > Think about the regression now in dapper of KDE...it's really sad to tell
> > the users: "Sorry, it doesn't work, because we just tested it on GNOME,
> > nobody cared about KDE or XFCE".
>
> I'm concerned about hardware support. The desktop used is irrelevent.

That's more then OK.

>
> > *Ubuntu != Ubuntu Server is all about the desktop. And all the
> > functionality which is included in the ubuntu-base should be tested on
> > all desktop flavours. That's my POV, just because it's all about the
> > user.
>
> Yes, but not on every single piece of hardware.

That's what I said. We should test the desktop, not all machines. If the 
underlaying technology is working on all machines without any glitch, then it 
should work on the desktops as well, but we all know, that this is not the 
case.

>
> > And you can believe me, the userbase of {K,X}Ubuntu I have to work with
> > is pretty big.
>
> That doesn't mean we need to test Kubuntu on every piece of hardware.

But we need to test Kubuntu/Xubuntu at least, and that's not the way right 
now. Most people test the laptop hardware support with their desktop, not on 
the CLI.

> This is my final word on the matter. The role of the laptop testing team
> is to test laptop functionality, not Kubuntu functionality. Providing
> that Kubuntu provides the appropriate functionality (that is, it
> responds to hotkeys in the correct way and so on), I will guarantee that
> everything that works on Ubuntu will work on Kubuntu. I will do this
> without testing every laptop. If Kubuntu does not do things properly,
> then it must be fixed - I refuse to ask people to waste their time
> dealing with poor design decisions. Use HAL. Use the input layer. Don't
> layer everything over insane custom protocols. Everyone ends up happy,
> because bugs get fixed in one place rather than having to be fixed in
> several. If you're not happy with that, then please feel free to raise
> it with the tech board.

Then we need to change the focus how we test laptop functionality.
See above. We need to test the functionality without the focus on any desktop 
environment, and test once on the different desktop flavours.

Nothing else we need. There is no need to call the TB for that. It's only a 
matter of how we do the testing.

Regards,

\sh

-- 
SysAdmin and Linux Specialist
Freelancer, http://linux.blogweb.de/pages/cv.html
JID: sh at linux-server.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/laptop-testing-team/attachments/20060702/67344df2/attachment-0001.pgp