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

List:       kwin
Subject:    Re: [GSoC] Unit Testing Framework
From:       Christoph Feck <christoph () maxiom ! de>
Date:       2011-03-17 22:37:38
Message-ID: 201103172337.38548.christoph () maxiom ! de
[Download RAW message or body]

On Thursday 17 March 2011 15:11:25 Jon Ander Peñalba wrote:
> I'm interested in creating the Unit Testing Framework for GSoC.

Cool, looking forward to any new contributor!

Regarding the testing, what I would like to see is some tests that verify if 
operations do not cause unnessary "blits" (i.e. copies of pixel data).

First, every function that can cause a blit should have a way to record the 
rectangle of the modified region, and (unless transparency is involved) verify 
that this region, or a part of it, is never modified again. On my system, 
screen updates get really slow with multiple overlapping windows, even if only 
the frontmost window changes (and it isn't transparent) and having a way to 
track such unneccessary blits would be awesome.

Second, many operations currently cause repaints in regions that aren't 
affected by the operation at all. While we have to "Show Paint" effect to see 
such repaints, there should be unit tests that verify that indeed only a 
specific region is updated by a particular operation.

Finally, a way to track uninitialized pixel data would be nice. In earlier 
releases, and even today, I am seeing blits of either random, gray, black, or 
white pixels, depending on moon phase. Having tests that ensure that nothing 
is ever copied to the screen that isn't "approved" to be generated application 
content would be very nice. This means attaching additional test information 
to internal pixmaps, framebuffers etc. and ensure they are never blitted to 
screen unless they contain data.

Of course it should be possible to disable all such instrumentation for 
release mode to get maximum speed.

Christoph Feck (kdepepo)
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

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