Jody Garnett ha scritto:
> Andrea Aime wrote:
>> Jody Garnett ha scritto:
>> ...
>>> Two ideas:
>>> - you can capture the font handling code by providing a custom
>>> labeler (like we do from uDig) and then just doing normal unit tests
>>> on the labeler to make sure it has collected the expected
Andrea Aime wrote:
> Jody Garnett ha scritto:
> ...
>> Two ideas:
>> - you can capture the font handling code by providing a custom
>> labeler (like we do from uDig) and then just doing normal unit tests
>> on the labeler to make sure it has collected the expected information
> Yeah, that could w
Jody Garnett ha scritto:
...
> Two ideas:
> - you can capture the font handling code by providing a custom labeler
> (like we do from uDig) and then just doing normal unit tests on the
> labeler to make sure it has collected the expected information
Yeah, that could work, thought only for labels
Andrea Aime wrote:
> Some years ago rendering tests were made against simple,
> manually verified exemplars, that is, generated images that
> were stored on disk and then compared pixel by pixel against
> the result of a test render operation. To put it in other words,
> it was checked that the ren
Andrea Aime ha scritto:
...
> Soc is already gone, we'd have to wait for next year.
> As a quick measure of distance, we could do the following. For each
> pixel, extract the R G B A components, make a difference, component
> by component, against the expected value, and sum up the absolute
> value
Andrea Aime ha scritto:
> Rob Atkinson ha scritto:
...
> Yet, the visual comparison could be included in the release producers
> making sure we don't have busted releases like 2.4.3.
Typo: release procedures, not producers
Cheers
Andrea
--
Rob Atkinson ha scritto:
> One could create a index page of output artefacts, for a quick visual
> scan. The human brain is pretty good. If this index page included static
> "expected" samples it would be pretty quick to eyeball.
Hum... one of the major features we want out of a build is to
be h
Hi,
this is a mail I have been meaning to write for quite some time,
the 2.4.3 release issues give me enough reason to take the time
and dump my toughts on a mail.
GeoTools has quite a big problem, we have the rendering modules
(renderer and shapefile-renderer) that have some unit tests, but
none
