I don't know the code base you're working on. I think what you need to do is to narrow down which test that produces that error. You can split the tests like binary search or whatever method you like (running the tests for each package etc). In InaSAFE, for testing purposes, there's a handy function called get_qgis_app that will instantiate a QgsApp. It is used in the tests which also to prevent that error. See here for the usage of that function https://github.com/AIFDR/inasafe/search?utf8=%E2%9C%93&q=get_qgis_app
Regards On Wed, Jun 24, 2015 at 5:01 PM, Tom Chadwin <tom.chad...@nnpa.org.uk> wrote: > So Google has told me repeatedly. My issues are: > > - I have not previously done this because the plugin works fine in QGIS, > and > this issue has only shown up in tests > > - I don't know how (or where) to instantiate QApplication (or > QgsApplication?) > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Using-TravisCI-integration-in-Github-for-QGIS-Python-plugin-tp5207646p5212636.html > Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > -- *-------------------* *Akbar Gumbira* *Software Engineer* *Geospatial, NLP, Data Mining, Machine Learning, Artificial Intelligence*
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
