#2998: m.nviz.image fails with X Error BadValue integer parameter out of range
for
operation
-------------------------+-------------------------------------------------
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.2.4
Component: LibOpenGL | Version: svn-trunk
Resolution: fixed | Keywords: m.nviz.image, NVIZ, 3D, GLX,
| X_GLXCreateContext, g.gui.animation
CPU: x86-64 | Platform: Linux
-------------------------+-------------------------------------------------
Comment (by wenzeslaus):
Replying to [comment:31 hcho]:
> Replying to [comment:30 wenzeslaus]:
> > Would you mind creating an automated test? (Perhaps testing at least
dimensions of created PPM.)
>
> How does an automated test work?
You write a Python class using `grass.gunittest` package in the best case
(and a shell script in the worst case). See documentation here and let me
know if you are missing some info there:
https://grass.osgeo.org/grass74/manuals/libpython/gunittest_testing.html
Here is an example, see the directory called `testsuite`:
source:grass/trunk/raster/r.mapcalc
> Is it automatically invoked by make?
No, something like `make test` is still to be implemented, but it should
be fairly straightforward to do so.
> Different modules have different folder names for test scripts.
Yes, there are some legacy tests (or tests which can't be automated) in
directories with different names (or not in a subdirectory). The name
which is picked by the automated tests is `testsuite`.
If everything is done right, the tests will appear every day at:
http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/index.html
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2998#comment:33>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev
