doc: add Testing.md - #5420
Conversation
Used LLM to write the first draft and to cross-check the accuracy of the final version against the codebase. The draft was far too verbose, and cutting it down to something people would actually read took me quite a bit of time. Assisted-by: Claude Code / claude-opus-5 Signed-off-by: Jinnie Kim <jinhgkim@gmail.com>
|
I wrote it in a way that makes sense to me, but am not sure if it would make sense to others as well. Feedback welcome. |
| - For platform-specific diffs, add a variant ref (e.g. `out-win.txt`) rather | ||
| than overwriting | ||
| - Be conservative loosening image diff thresholds — use the minimum needed | ||
| - Check uploaded CI artifacts before changing references when local | ||
| reproduction is unclear |
There was a problem hiding this comment.
In theory, we could drop these as they now live in Testing.md, and the coding assistant will read Testing.md as stated on line 75, BUT it may not prioritize those points as heavily as before. If we want to remove redundancy, we should remove it, and if we want those critical points to be prioritized by the agent, we should keep them. Let me know what you think, @lgritz.
|
@jinhgkim It's not that I'm ignoring this... I just need time to think really hard about it and mull it over for a while. This might be one where I really want to write a first draft, or at least a detailed outline, before the bots go anywhere near it. |
2 participants
Description
Fixes #4760.
Replaced
testsuite/TESTSUITE-README.mdwith a more complete version atdocs/dev/Testing.md.Used LLM to write the first draft and to cross-check the accuracy of the final version against the codebase. The draft was far too verbose, and cutting it down to something people would actually read took me quite a bit of time.
Assisted-by: Claude Code / claude-opus-5
Tests
No test needed.
Checklist:
and if I used AI coding assistants, I have an
Assisted-by: TOOL / MODELline in the pull request description above.
behavior.
PR, by pushing the changes to my fork and seeing that the automated CI
passed there. (Exceptions: If most tests pass and you can't figure out why
the remaining ones fail, it's ok to submit the PR and ask for help. Or if
any failures seem entirely unrelated to your change; sometimes things break
on the GitHub runners.)
fixed any problems reported by the clang-format CI test.
corresponding Python bindings. If altering ImageBufAlgo functions, I also
exposed the new functionality as oiiotool options.