From 132c0824644b31ca1b3b14343fcc2a34d72bd7f6 Mon Sep 17 00:00:00 2001 From: Alexander Todorov Date: Fri, 23 Apr 2021 18:50:38 +0300 Subject: [PATCH] tests: Document examples of good/bad BZs for qa_ack+ --- test/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/test/README.md b/test/README.md index 65046ec28..7186d5d13 100644 --- a/test/README.md +++ b/test/README.md @@ -306,7 +306,11 @@ can be used to review the test automation state during a PR lifecycle. `qa_ack+` on RHBZ will be granted **after** a reproducer has been identified and with the mutual understanding that PRs related to -that RHBZ must include an automated test reproducer. +that RHBZ must include an automated test reproducer. A good example is +[BZ #1951192](https://bugzilla.redhat.com/show_bug.cgi?id=1951192#c3) while +a bad example is +[BZ #1942029](https://bugzilla.redhat.com/show_bug.cgi?id=1942029#c0) b/c +is is missing lots of details! ## Cron jobs for internal builds testing