[Digikam-users] You're awesome

[Peter Shute]

Yes, surely there are tools to click the buttons for you.

But testing for problems is one thing, how will this help the user who has innocently upgraded KDE, for example, and then finds digiKam has become erratic?

Do we need a webpage that lists which versions of digiKam work with which components, in order to warn users when not to upgrade them?  Or do we make it easier for users to obtain a new version of digiKam with the fixes for the upgraded components?

Either of these doesn't seem to be that simple.


--------------------------
Sent using BlackBerry

----- Original Message -----
From: Andi Clemens <andi.clemens at gmx.net>
To: digikam-users at kde.org <digikam-users at kde.org>
Sent: Fri Mar 05 05:57:24 2010
Subject: Re: [Digikam-users] You're awesome


On Thursday 04 March 2010 08:41:35 Gilles Caulier wrote:
> 2010/3/4 Peter Shute <pshute at nuw.org.au>:

> 
> As i'm working in computer science since a very long time, in industry
> and now in research, i know very well the problem. I'm trying to apply
> some QA mechanism in digiKam project, especially with bugzilla where
> we can follow development and progress, but it's not easy. Andy,
> Marcel, and Johannes as started to implement regression test programs
> to check digiKam core API, but it only work very well, in general, for
> non-gui code. GUI code need user interractions...
> 

You can do GUI unit tests, but I guess they work best with single widgets. But 
it general this is possible. 

Andi
_______________________________________________
Digikam-users mailing list
Digikam-users at kde.org
https://mail.kde.org/mailman/listinfo/digikam-users