From 1e3599072f2f1c01abbe26efc4a6e98244c20ffc Mon Sep 17 00:00:00 2001 From: williamlardier Date: Thu, 12 Dec 2024 15:02:25 +0100 Subject: [PATCH] Update PR message Issue: ZENKO-4944 --- .github/PULL_REQUEST_TEMPLATE.md | 13 ++++++------- tests/ctst/HOW_TO_WRITE_TESTS.md | 2 +- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 9703402b4d..61da8c9f07 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,13 +1,12 @@ - - **What does this PR do, and why do we need it?** **Which issue does this PR fix?** -fixes # +Fixes ZENKO-XXXX. **Special notes for your reviewers**: + + diff --git a/tests/ctst/HOW_TO_WRITE_TESTS.md b/tests/ctst/HOW_TO_WRITE_TESTS.md index 82c73e8a61..34a4634fef 100644 --- a/tests/ctst/HOW_TO_WRITE_TESTS.md +++ b/tests/ctst/HOW_TO_WRITE_TESTS.md @@ -14,7 +14,7 @@ parallel with other tests. In parallel, the tests can run in any order. It's not because a test works at a given time, that it will work if the test order changes after adding new ones or renaming files. You must ensure the scenarios are fully idempotent. -"Flakies" are, mostly due to non-idempotent tests, then bugs. It is rarely due +"Flakies" are mostly due to non-idempotent tests, then bugs. It is rarely due to the platform. **Rule #2**