[Qgis-developer] rendering tests, what's the latest approach ?

[Nyall Dawson]

On 13 November 2015 at 02:48, Sandro Santilli <strk at keybit.net> wrote:
> On Thu, Nov 12, 2015 at 04:42:07PM +0100, Matthias Kuhn wrote:
>> Simple answer: don't use rendering tests and find other means to check
>> it ;-)
>
> How could I check that an arror is not flipped and does not move
> to the other side of the line ?
>
> To be honest, I like the idea of rendering tests. I know they are
> fragile in their current incarnation, but being a graphical
> application having tests actually check what the user would see
> is a good way to catch many issues.

I personally think we've reached a good level of stability with the
rendering tests. They now perform consistently across all platforms
(passing when they should and failing when they shouldn't). So I'm
keen to hear any thoughts on why you think these are still fragile?

Nyall



>
>> If you still need, use the MultiRenderChecker, it is based on the
>> RenderChecker but adds more possibilities for anomalies. At least that's
>> the latest state of rendering tests I'm aware of...
>
> Ok, great. How about the distinction between these two files ?
>
>   * testqgsstylev2.cpp
>   * testqgssymbolv2.cpp
>
> Actually, the second one is _not_ in the 2.8 branch (which I'm
> targetting). Should it be back-ported ?
>
> --strk;
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer