[Qgis-developer] Deliberate errors, but Travis passes

[Matthias Kuhn]

Hi Tom,

In this case please read my question as "where exactly do you expect the
tests to fail?" :-)

I did a short check and it looks like it causes a segfault at the moment
and this is somehow not picked up properly?

Though looking at your commit for the deliberate error you are looking
for an exception but it is unclear to me via which codepath the tests
should get from the test file to the point in the code where you
introduced the deliberate error.

Matthias

On 09/08/2015 03:36 PM, Tom Chadwin wrote:
> Hi Matthias
>
> This is the very early stages of implementing unittest. In time, I will test
> for expected results using assert methods. At the moment, though, all I want
> this to achieve is to catch Python errors, to prevent my making releases
> which crash. This is what I was doing before, and it worked as I needed: if
> the plugin gave a Python error, Travis failed - if not, it passed. This no
> longer seems to work, though - as I say, if I introduce a deliberate error
> to the code, and confirm that the plugin gives a Python error, Travis
> nevertheless passes.
>
> Thanks
>
> Tom
>
>
>
> --
> View this message in context: http://osgeo-org.1560.x6.nabble.com/Deliberate-errors-but-Travis-passes-tp5223114p5223142.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20150908/5d18aa26/attachment.pgp>