From deb4878dbe18b06881bb6e2fc4f0a60b8d96f417 Mon Sep 17 00:00:00 2001
From: Rory Abraham <rory@expensify.com>
Date: Thu, 25 Mar 2021 15:05:16 -0700
Subject: [PATCH] Add QA steps to the pull request template

---
 .github/PULL_REQUEST_TEMPLATE.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 352329970049..d4a851edda6f 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -11,7 +11,19 @@ Fixes GH_LINK
 <!--- 
 Add a numbered list of manual tests you performed that validates your changes work on all platforms, and that there are no regressions present.
 Add any additional test steps if test steps are unique to a particular platform.
-Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes.
+Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes in the development environment.
+
+For example:
+1. Click on the text input to bring it into focus
+2. Upload an image via copy paste
+3. Verify a modal appears displaying a preview of that image 
+--->
+
+### QA Steps
+<!--- 
+Add a numbered list of manual tests that can be performed by our QA engineers on the staging environment to validate that your changes work on all platforms, and that there are no regressions present.
+Add any additional QA steps if test steps are unique to a particular platform.
+Manual test steps should be written so that the QA engineer can repeat and verify one or more expected outcomes in the staging environment.
 
 For example:
 1. Click on the text input to bring it into focus