[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    Re: [kde-edu-devel] Test framework already used?
From:       Dominique Devriese <dominique.devriese () student ! kuleuven ! ac ! be>
Date:       2004-02-20 0:45:24
Message-ID: 874qtminob.fsf () student ! kuleuven ! ac ! be
[Download RAW message or body]

Sebastian Stein writes:

> Dominique Devriese <dominique.devriese@student.kuleuven.ac.be>
> [040219 21:45]:
>> > I could also use some big testing framework like the testing
>> > classes in boost. If I do so, should I also put this into CVS?
>>
>> Absolutely not.  You can't put an entire boost library in KDE CVS
>> just to do some tests.

> I would only put the test cases online, the boost lib would be on
> the local maschine. It is just like linking against glibc, it isn't
> in KDE CVS as well.

Oh, then I misunderstood you, sorry.  Then of course, the tests
themselves belong in KDE CVS.
 
>> > Is there already a generic way for testing KDE apps? Any other
>> > ideas?
>>
>> Do you really need more infrastructure than a simple test app ?

> I just don't want to reinvent the wheel so I ask, if there is
> already a common way to do automatic testing in KDE. I know there
> are test cases for khtml, but I had not the time to look at it.

Yes, I know about this, but I have no idea how it works either.
Anyway, I don't think there is a KDE testing infrastructure.

Off topic, but I personally think very thorough unit testing should
only be done for large libraries, for which it is important that their
public API is stable and consistent.  For apps, a simple test
framework should be more than enough.

cheers
domi
_______________________________________________
kde-edu-devel mailing list
kde-edu-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-edu-devel
[prev in list] [next in list] [prev in thread] [next in thread]