[GRASS-git] [OSGeo/grass] ea1a7c: contributing: Add a testing guide

[Vaclav Petras]

  Branch: refs/heads/docs-pytest-testing-guide
  Home:   https://github.com/OSGeo/grass
  Commit: ea1a7cb63e54ea9e2c611b46e792ecbd454a7224
      https://github.com/OSGeo/grass/commit/ea1a7cb63e54ea9e2c611b46e792ecbd454a7224
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2026-08-25 (Tue, 25 Aug 2026)

  Changed paths:
    M AGENTS.md
    M CONTRIBUTING.md
    M doc/development/CMakeLists.txt
    M doc/development/Makefile
    M doc/development/README.md
    M doc/development/style_guide.md
    A doc/development/testing.md
    M man/mkdocs/docs/development_intro.md
    M testsuite/README.md

  Log Message:
  -----------
  contributing: Add a testing guide

The most complete statement of GRASS testing conventions lived in AGENTS.md, written for AI agents, and a contributor following the documented path never saw it. style_guide.md had no testing section, testsuite/README.md gave pytest a single sentence, and the Testing section in development_intro.md linked only the gunittest manual.

This adds testing.md covering the choice between pytest and gunittest, test placement and naming, session fixtures, grass.tools, test data, running the tests, and tests which cannot run in parallel. AGENTS.md now points at the guide and keeps only its agent-specific notes, so the two cannot drift too much.

This change was drafted with the help of Claude Code (Fable 5).



To unsubscribe from these emails, change your notification settings at https://github.com/OSGeo/grass/settings/notifications