mirror of
https://github.com/rsyslog/rsyslog.git
synced 2026-06-04 23:22:58 +02:00
2b2fcd5ef5
Why: Test assertions should prove the observable behavior operators rely on, not just that rsyslogd wrote a message to its process streams. Impact: Clarifies test-authoring and babysitting guidance for rsyslog diagnostics. Before/After: Tests could use stdout/stderr oracles without a clear exception; guidance now prefers configured rsyslog output destinations after synchronized shutdown. Technical Overview: Add the authoritative rule to tests/AGENTS.md. Point rsyslog_test at that rule when explaining test oracle documentation. Add a review-time reminder to rsyslog_pr_babysitting so PR feedback catches weak stdout/stderr diagnostic oracles. Exceptions remain allowed when the tested behavior is process output or configuration is not usable yet, but they must be documented in the test header. With the help of AI-Agents: OpenAI Codex