[gdal-dev] Motion: adopt RFC 72: Run tests with pytest

[Jonathan Moules]

Hi,

PyTest is a great test-suite.

If I may make one suggestion as someone who has used it for a while - 
it's worth spending a little thought on coming up with a scheme for 
test-ids. Especially if you're going to use parameterisation.

Otherwise PyTest comes up with names that may be accurate (they're a 
concatenation of the parameters), but are relatively meaningless. For 
example "gdaladdo--100", "gdaladdo-foo", etc, as compared to more useful 
ids like "gdaladdo-too-low-input", "gdaladdo-bad-string-input" which 
tell you immediately what the test is actually meant to be testing.

There's a hook called pytest_make_parametrize_id which allows you to 
create your own ids (I find the built-in methods of id generation either 
cumbersome, or bit-rot prone).

I'm suggesting it now because it's more helpful if you do it from the start.

Cheers,

Jonathan



On 2018-12-05 22:40, Craig de Stigter wrote:
> Hi
>
> I appreciate your comments on the pytest proposal and all the support 
> to help get it this far. Given no actionable improvements have been 
> suggested, and the feedback thus far seems encouraging...
>
> I move to adopt RFC 72: Run tests with pytest.
>
> https://trac.osgeo.org/gdal/wiki/rfc72_pytest
>
>
> Cheers
> Craig de Stigter
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20181208/f1759c7b/attachment.html>