Agreed about test interdependency being rough. Internally at work, we have
a test runner that intentionally does not run tests in order. All the
autotest2 stuff I did should all be order independent. Sadly, my old tests
are using pythons normal test setup, not pytest.
On Mon, Feb 20, 2023, 7:57
I thought about writing something down, too, but didn't see anything about
writing tests at https://gdal.org/development/testing.html and I decided I
wasn't qualified to start a new section about testing standards.
On Mon, Feb 20, 2023, 10:52 AM Even Rouault
wrote:
> Hi Sean,
>
> I fully agree t
Hi Sean,
I fully agree that pytest.mark.parametrize() is cleaner and the way to
go, and I use it extensively in new tests. For what you were referring
too, this was a change in an existing test that used the old for looping
habits, so I felt it was a bit too much to ask the contributor to
ref
> Additionally, these loops fix the order that the checks are made, and bugs
> can hide in test order dependency.
As we're on the topic of pytest, I'll mention fixtures as a handy
feature for test setup: https://docs.pytest.org/en/6.2.x/fixture.html
I discovered a while back that some parts of t
Hi all,
I just saw a maintainer recommend to a contributor that the contributor
loop over test cases from within a test function and it prompted me to
speak up about a better practice: using pytest parameterization
https://docs.pytest.org/en/6.2.x/parametrize.html#pytest-mark-parametrize-parametri
Hi Mike,
no you can't specify configuration options in a VRT, since some of them
have security implications (particularly the GDAL_VRT_ENABLE_PYTHON one
that could lead to arbitrary code execution, but other ones might also
have impacts).
One possibility would be to have a syntax like the fo
Hello,
I've been trying to build GDAL from source to add KEA support. The
configuration goes well and the compilation doesn't report any issue.
However, gdalinfo keeps outputting the following message:
~/gdal-3.4.3$ gdalinfo --version
GDAL 3.4.3, released 2022/04/22
HDF5-DIAG: Error detected in HD
Is there a method to add gdal configuration options to a VRT so that they are
carried around with it?
For example:
gdalbuildvrt openlandmap_dtm.vrt
/vsis3/openlandmap/dtm/dtm.bareearth_ensemble_p10_30m_s_2018_go_epsg4326_v20230210.tif
--config AWS_NO_SIGN_REQUEST YES --config AWS_S3_ENDPOINT
