Hi, I've mostly finished the labeling unit test framework (at least for *nix). You can read about the setup in its README [0] and about the local test server [1], if interested.
I'm happy to report that there is considerably good parity between all outputs now (at least from my testing on Mac), especially since the advent of mulit-threaded rendering. However, there are only a few actual unit tests right now. The only outstanding issues revolve around too much antialiasing in test renders. There is still some CMake coding to do, adding modules for the now-required utilities when ENABLE_TESTS=ON. These are currently: * lighttpd (local HTTP server) * spawn-fcgi (qgis_mapserv.fcgi spawner) * poppler, with cairo support (composer PDF -> image rasterizer, for comparisons) There still needs config files set up for lighttpd/spawn-fcgi on Windows. I'll be triaging labeling bugs and trying to fix them, while ensuring regression tests are in place and passing. Then I'll add more unit tests for general API stuff. Lastly, I will be putting forth a proposal concerning a redesign of the labeling classes, which includes rule- and style-based labeling. That will come after an effort on the previously noted bug fixing. Any help with the bug squashing (or anything related to this stuff) would be greatly appreciated. :-) [0] https://github.com/qgis/QGIS/tree/master/tests/testdata/labeling [1] http://osgeo-org.1560.x6.nabble.com/New-Python-QgsLocalServer-and-standard-fonts-for-testing-td5104818.html Regards, Larry Shaffer Dakota Cartography Black Hills, South Dakota
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
