| contributing: Add a testing guide (#7851) 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. Trim the testsuite README to minimum. testsuite/README.md described which testing frameworks exist and how to run pytest, which testing.md now covers, and the export commands in its Running tests section had stray backslashes which made them set literal strings when copied. The directory still needs a README since it is a top level and has unclear content (a shell script). This keeps what the directory is for and the pointer to the CI, names raster_md5test.sh, and links testing.md for everything else. The North Carolina sample dataset URL moves to testing.md, next to the command which uses the dataset. | 1 个月前 |