From f6da4749f9795cfff0b3bf60240c4f946d07cdec Mon Sep 17 00:00:00 2001 From: Samuel Hawksby-Robinson Date: Thu, 14 Mar 2024 01:35:45 +0000 Subject: [PATCH] Added reporting flowchart --- _docs/policies/tests.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/_docs/policies/tests.md b/_docs/policies/tests.md index d7785779c..1cb497cff 100644 --- a/_docs/policies/tests.md +++ b/_docs/policies/tests.md @@ -67,3 +67,26 @@ flowchart TB - The issue should use the https://github.com/status-im/status-go/labels/E%3AFlaky%20Test label - Detail that you have experienced the test being flaky and in what context (local vs CI, link to the PR or branch). +```mermaid +flowchart TB + A([Ready to report a flaky test]) --> B[Check the `status-go` GitHub repo
issues for the test name failing.] + B --> C{Does the test appear in
the list of `E: Flaky Test` issues?} + C -->|No| D[ + Create a new issue + - The issue title should include the flaky test name + - The issue should use the https://github.com/status-im/status-go/labels/E%3AFlaky%20Test label + ] + D --> E[ + Detail which test is flaky and in what context: + local vs CI, link to the PR or branch. + ] + E --> J + C -->|Yes| F{Is the issue open?} + F -->|No| G((Either)) + H --> E + G --> I[Reopen the issue] + G --> D + I --> H + F -->|Yes| H[Add a comment to the issue] + J([End]) +``` \ No newline at end of file