Skip to content
Snippets Groups Projects
Verified Commit 6d3a398d authored by Fiona Neill's avatar Fiona Neill :wave: Committed by GitLab
Browse files

Merge branch 'ag/add-uat-issue-template' into 'master'

Add new Issue template for User Acceptance Tests

See merge request !171559



Merged-by: default avatarFiona Neill <fneill@gitlab.com>
Approved-by: default avatarFiona Neill <fneill@gitlab.com>
Co-authored-by: default avatarAngelo Gulina <agulina@gitlab.com>
parents 9d2757f6 24ee14f1
No related branches found
No related tags found
1 merge request!171559Add new Issue template for User Acceptance Tests
Pipeline #1531392070 passed
# Test case name: TC-XX-## <!-- Example: TC-MH-1 -->
## Test case scenario
_Describe the test scenario this task corresponds to_
<!-- Example: New customer buys new SaaS Premium subscription via CDot between April 3, 2023 and April 2, 2024. -->
<table>
<tr>
<th>Deal Type (select everything that applies)</th>
<th>Product Type (select everything that applies)</th>
<th>Product Tier</th>
<th>Deal Term (months)</th>
<th>Ramped segments</th>
<th>Initial Purchase Discounted?</th>
<th>Purchase Method</th>
<th>Purchase Path</th>
</tr>
<tr>
<td>
<ul>
<li>- [ ] New</li>
<li>- [ ] Add-on (Storage, CI minutes)</li>
<li>- [ ] Add seats</li>
<li>- [ ] Manual renewal</li>
<li>- [ ] Auto-renewal</li>
<li>- [ ] Upgrade</li>
<li>- [ ] Cancellation</li>
<li>- [ ] First order</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] SaaS</li>
<li>- [ ] Self-managed</li>
<li>- [ ] True-up</li>
<li>- [ ] Add-on (Storage, CI minutes)</li>
<li>- [ ] Extra seats</li>
<li>- [ ] Professional services only</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] Premium</li>
<li>- [ ] Ultimate</li>
<li>- [ ] Premium > Ultimate (upgrade)</li>
<li>- [ ] Legacy Premium</li>
<li>- [ ] Legacy Ultimate</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] 12</li>
<li>- [ ] 24</li>
<li>- [ ] 36</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] Non-Ramp</li>
<li>- [ ] 2</li>
<li>- [ ] 3</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] Yes</li>
<li>- [ ] No</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] Web store</li>
<li>- [ ] Sales-assisted</li>
<li>- [ ] Automated</li>
</ul>
</td>
<td>
<ul>
<li>- [ ] Direct</li>
<li>- [ ] Partner</li>
</ul>
</td>
</tr>
</table>
## Artifacts
_Add various artifacts for this test scenario for reference_
1. Account (SFDC):
1. Opportunity (SFDC):
1. Quote (SFDC):
1. Order form (SFDC):
1. Subscription (Zuora):
1. Test case dependency (if any):
## Test steps
_List the steps to be performed to verify this scenario_
<!-- Example:
1. **GitLab.com:**: Purchase a subscription for a group
2. **CustomersDot:** Visit Customers Portal at http://customers.staging.gitlab.com
3. **CustomersDot:** Verify subscription details for purchased subscription
-->
## Expected result
_Describe the expected outcome of this test scenario_
### Screenshots
| Step | Screenshot |
|---|---|
| | |
<!--
You might want to create a comment or a separate issue for each of the following items, to ensure sign-off from all departments:
- [ ] Deal Desk sign-off
- [ ] Billing sign-off
- [ ] Revenue sign-off
- [ ] Fulfillment sign-off
- [ ] Data sign-off
-->
/confidential
/label ~"devops::fulfillment" ~"section::fulfillment"
<!--
You might also want to add some of the following labels, or weight:
/label ~workflow::
/label ~estimation::
/label ~group::
/label ~Category:
/label ~maintenance::
/weight
-->
<!--
This Issue template is meant to provide guidance for User Acceptance Tests.
1. Create the Issue and assign a title referring to the tested feature.
1. Fill the below details when relevant.
-->
# User Acceptance Testing
# Summary
Manual testing for the <issue-link> feature.
# Pre-requisite
_Add any steps to be performed before end to end testing can begin_
- [ ] Set a milestone for the test session issue to inform all the DRIs about the upcoming testing session.
- [ ] System leaders identify a DRI to participate in the testing session.
- [ ] Completion of Staging Rollout issue ([example](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/6202)).
- [ ] Ensure all testers have the right access/permissions in all our Staging applications (Zuora, Salesforce, CDot, etc) for testing purposes.
- [ ] Ensure all system DRIs have reviewed the new test scenarios and approved the changes.
- [ ] Sales Systems: `@handle`.
- [ ] Sales Ops: `@handle`.
- [ ] Enterprise Apps: `@handle`.
- [ ] Data: `@handle`.
- [ ] Billing: `@handle`.
- [ ] Revenue: `@handle`.
- [ ] Fulfillment: `@pm-handle` and `@em-handle`.
- [ ] Communicate an estimated time for the testing session to all the DRIs.
- [ ] **{-Enable feature flag:}** {feature-flag-name} on {environment-name}: [Feature flag rollout issue](<link to feature flag rollout issue>).
- [ ] Clear any caches.
# Useful Links
_Add any links that are helpful to carry out testing such as links to the flows involved, etc._
<!--
Example below:
1. [Zuora Staging](https://test.zuora.com/)
1. [Salesforce Staging](https://gitlab--test1.sandbox.my.salesforce.com)
-->
1. ...
# How to
1. Create a [**Task**](User%20Acceptance%20Test%20Task.md) for each scenario mentioned in the list.
- The Task holds each relevant Test Case for the scenario in its own section.
- Each section holds that case's testing outcome and artifacts. (E.g. screenshots, screen recordings, or text notes.)
1. Create a [**Test Case**](https://gitlab.com/gitlab-org/customers-gitlab-com/-/quality/test_cases) for each variation of the scenario, if one does not already exist. (E.g. testing across product tiers or user roles.)
- The Test Case outlines the testing scenario, the test steps involved, and the expected result.
- **Make sure to set the Test Case to be confidential if applicable when it's created**, as it might not be confidential by default.
1. Before testing a Task, assign yourself to it to avoid multiple people testing the same scenario.
1. **\[Optional\]** assign a tested Task to a PM for review.
- Use the `Task` comments section to discuss any unexpected behaviour and create follow-up Issue(s).
1. **\[Optional\]** A PM should sign-off the test scenario if everything looks good. The, close the Task, and mark it as complete in this issue.
1. Add [Bug(s)](#identified-bugs) and/or [Question(s)](#open-questions) to the corresponding sections below.
# Test Cases
<table>
<tr>
<th>Scenario #</th>
<th>Task</th>
<th>Test Case</th>
<th>Scenario</th>
<th>Expected Outcome</th>
<th>Product Sign-off</th>
<th>UX Sign-off</th>
</tr>
<tr>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
<td>
</td>
</tr>
</table>
# Identified Bugs
| Bugs | Testing type (Automated/ Manual) | Resolution | MR | DRI |
|------|----------------------------------|------------|-----|-----|
| | | | | |
| Question | Related Test Case | Answer | DRI |
| -------- | ----------------- | -------| --- |
| _Summary of question here (can have link to discussion from comments)_ | _Test case link_ | _Final answer / resolution_ | _Person responsible for answering question_ |
## Sign-offs
_Once all scenarios have passed validation, stakeholders will provide final sign-off below_
- [ ] Sales Systems: `@handle`
- [ ] Sales Ops: `@handle`
- [ ] Enterprise Apps: `@handle`
- [ ] Data: `@handle`
- [ ] Billing: `@handle`
- [ ] Revenue: `@handle`
- [ ] Fulfillment: `@pm-handle` and `@em-handle`
/label ~"devops::fulfillment" ~"section::fulfillment"
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment