great, I was just writing two new python tests I'll give a look to your addition
tnx Luigi Pirelli ************************************************************************************************** * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com * LinkedIn: https://www.linkedin.com/in/luigipirelli * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli * GitHub: https://github.com/luipir * Mastering QGIS 2nd Edition: * https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition ************************************************************************************************** On 3 November 2017 at 14:52, Matthias Kuhn <[email protected]> wrote: > Fellow developers, > > we all spend our precious time on writing unit tests. And we want to do > this as efficiently as possible. > > One thing that can really kill fun is if a python unit test segfaults. > Mainly because there is no hint by default, where to start looking for > what's gone wrong. > > I just drafted a new section in the developer docs, how to run python > unit tests from within QtCreator, to help you spend less time on > debugging python tests and have more time on writing additional tests. > > https://github.com/qgis/QGIS-Website/pull/479/files > > Any feedback and improvement welcome. > > Thanks > Matthias > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
