diff options
| author | Rémy Coutable <remy@rymai.me> | 2019-04-04 10:57:30 +0000 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2019-04-04 10:57:30 +0000 |
| commit | 60a0ef21d385e1943f9e6a68adc9d7e04e8d69c8 (patch) | |
| tree | 180444a45ddd495c03646eb3e346f25a4b2cfc83 | |
| parent | 0b74876a18a8ede2e8391794b13430da4c32671c (diff) | |
| parent | f5be4189acc8c03ace256b15108704eb78d8c9e2 (diff) | |
| download | gitlab-ce-60a0ef21d385e1943f9e6a68adc9d7e04e8d69c8.tar.gz | |
Merge branch 'ml-add-testing-to-feature-proposal-template-docs' into 'master'
Add testing to feature proposal template
See merge request gitlab-org/gitlab-ce!26779
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index b4007c1ba7b..8a49715e0e8 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -24,6 +24,10 @@ Personas can be found at https://about.gitlab.com/handbook/marketing/product-mar <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> +### 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? 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? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> |