summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Lapierre <mlapierre@gitlab.com>2019-04-02 15:06:17 +0000
committerMark Lapierre <mlapierre@gitlab.com>2019-04-02 15:06:17 +0000
commit79bb9b4f5def0ee788eb1e21660765b3b84abf2e (patch)
treecc35c378f8a387e462232585e8e5c15776cc3073
parent5a81c1d910129276816c70aefe4ad903c178f290 (diff)
downloadgitlab-ce-ml-add-testing-to-feature-proposal-template-docs.tar.gz
Apply suggestion to .gitlab/issue_templates/Feature proposal.mdml-add-testing-to-feature-proposal-template-docs
-rw-r--r--.gitlab/issue_templates/Feature proposal.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
index 48889e36aca..8a49715e0e8 100644
--- a/.gitlab/issue_templates/Feature proposal.md
+++ b/.gitlab/issue_templates/Feature proposal.md
@@ -26,7 +26,7 @@ Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/de
### Testing
-<!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ -->
+<!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ -->
### What does success look like, and how can we measure that?