Fulfillment Orders UAT 3 (sales-engaged use cases missed from Orders UAT 2)

### Problem
Sales-engaged [end-to-end Orders UAT](https://gitlab.com/gitlab-com/business-technology/enterprise-apps/intake/-/issues/554) is not yet completed for the estimated 2022.05 go-live. 

### Proposal

https://gitlab.com/groups/gitlab-com/business-technology/enterprise-apps/-/epics/80#note_887981775

- Fulfillment to define Fulfillment Purchasing and Licensing expected behavior (current state behavior) for the following sales-engaged use cases
- Fulfillment to observe sales-engaged use cases and provide approval for the deploy of Orders Harmonization to production

| TC #      | Business Line | Business Type | Type of Sale | Term        | Ramping  | Ramp Segment | License Type                       |
|-----------|---------------|---------------|--------------|-------------|----------|--------------|------------------------------------|
| TC-OH-F01 | Sales-Engaged | 1 - New       | Partner      | Standard 12 | Non-Ramp | N/A          | SaaS + Add On (Storage)            |
| TC-OH-F02 | Sales-Engaged | 1 - New       | Direct       | MY          | Ramp     | 1            | SaaS + Add On (CI Minutes) |
| TC-OH-F03 | Sales-Engaged | 1 - New       | Direct       | MY          | Ramp     | 2            | SaaS + Add On (CI Minutes) |
| TC-OH-F04 | Sales-Engaged | 1 - New       | Direct       | Standard 12 | Non-Ramp | N/A          | Add On (Professional Service)      |
| TC-OH-F05 | Sales-Engaged | 1 - New       | Direct       | Standard 12 | Non-Ramp | N/A          | Self-Managed |
| TC-OH-F06 | Sales-Engaged | 2 - Add On    | Partner      | Standard 12 | Non-Ramp | N/A          | SaaS + Add On (Storage) |
| TC-OH-F07 | Sales-Engaged | 2 - Add On    | Direct       | MY          | Ramp     | 1            | SaaS + Add On (CI Minutes) |
| TC-OH-F08 | Sales-Engaged | 2 - Add On    | Direct       | Standard 12 | Non-Ramp | N/A          | Self-Managed |
| TC-OH-F09 | Sales-Engaged | 3 - Renewal   | Partner      | MY          | Non-Ramp | N/A          | SaaS + Add On (TrueUp) |
| TC-OH-F10 | Sales-Engaged | 3 - Renewal   | Direct       | Standard 12 | Non-Ramp | N/A          | Self-Managed + Add On (TrueUp) |
| TC-OH-F11 | Sales-Engaged | 3 - Renewal   | Partner      | Standard 12 | Non-Ramp | N/A          | SaaS |

#### Test Case Steps

<details><summary>TC-OH-F01</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a SaaS product, plus a storage add-on. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-2     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-3     | Complete the provision through Support | Since this is a subscription purchased from a reseller, the customer is not supposed to be able to log in to CustomersDot to link their subscription. The email instructs to contact Support so we should go through the steps detailed in the [Provisioning subscriptions for reseller customers](https://about.gitlab.com/handbook/support/license-and-renewals/workflows/saas/associate_subscription_and_namespace.html#provisioning-subscriptions-for-reseller-customers) guide. | Purchased subscription should be linked to the correct namespace | Y |
| T-4     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). | Y | |
| T-5     | View Storage on Usage Quotas page | Navigate to Group's Usage Quotas page in staging.gitlab.com, then click the Storage tab. | Verify the purchased storage synced and the amount shown is correct based on the order. | Y | |

</details>

<details><summary>TC-OH-F02</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a SaaS product, plus a CI Minutes add-on. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592). This subscription will be setup as a sales-assisted ramps workaround, where this subscription represents the first ramp year. | The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  There should be an option to link the subscription with a namespace. | The Manage Subscriptions page shows the subscription.  | Y | |
| T-4     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-5     | Link the CustomersDot Customer with the GL.com User account | Back in CustomersDot, you should be able to link your CustomersDot Customer Account with your newly created GL.com User (staging).  Click the "My Account" button in the top nav bar, then click the "Account details" option.  Expand the "Your GitLab.com account" section and follow the steps for linking the account. | The CDot customer account should be linked with the GL.com user account. | Y | |
| T-6     | Link the Subscription with a namespace | Navigate to the "Manage Subscription" page in CustomersDot staging and find the subscription. Click the "Change linked namespace" button.  Select the group created on step T-4 and confirm the changes. | The subscription should now be linked to the group.  You should see the group name listed on the Manage Subscriptions page. | Y | |
| T-7     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). | Y | |
| T-8     | View Pipeline Minutes on Usage Quotas page | Navigate to Group's Usage Quotas page in staging.gitlab.com, then click the Pipelines tab. | Verify the purchased minutes synced and the amount shown is correct based on the order. | Y | |

</details>

<details><summary>TC-OH-F03</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a SaaS product, plus a CI Minutes add-on. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592). This subscription will be setup as a sales-assisted ramps workaround, where this subscription represents the second ramp year. | The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  There should be an option to link the subscription with a namespace. | The Manage Subscriptions page shows the subscription.  | Y | |
| T-4     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-5     | Link the CustomersDot Customer with the GL.com User account | Back in CustomersDot, you should be able to link your CustomersDot Customer Account with your newly created GL.com User (staging).  Click the "My Account" button in the top nav bar, then click the "Account details" option.  Expand the "Your GitLab.com account" section and follow the steps for linking the account. | The CDot customer account should be linked with the GL.com user account. | Y | |
| T-6     | Link the Subscription with a namespace | Navigate to the "Manage Subscription" page in CustomersDot staging and find the subscription. Click the "Change linked namespace" button.  Select the group created on step T-4 and confirm the changes. | The subscription should now be linked to the group.  You should see the group name listed on the Manage Subscriptions page. | Y | |
| T-7     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). | Y | |
| T-8     | View Pipeline Minutes on Usage Quotas page | Navigate to Group's Usage Quotas page in staging.gitlab.com, then click the Pipelines tab. | Verify the purchased minutes synced and the amount shown is correct based on the order. | Y | |

</details>

<details><summary>TC-OH-F04</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should only have a profesional service add-on. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password.  You should not receive any other emails from CDot related to this purchase. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  The subscription should not show an option for linking the subscription with a namespace since it is a professional service. | The Manage Subscriptions page shows the subscription.  | Y | |

</details>

<details><summary>TC-OH-F05</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a Self-Managed product. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592). | The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive license email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot with activation instructions (e.g. activation code unless cloud licensing is disabled). | Verify the email was received with instructions on how to activate. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  You should see the activation code (unless cloud licensing is disabled). | The Manage Subscriptions page shows the subscription with correct information and license activation code and/or license file. | Y | |

</details>

<details><summary>TC-OH-F06</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should start with a SaaS product, and a storage add-on as well (confirm with Mark). The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592). | The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-2     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-3     | Complete the provision through Support | Since this is a subscription purchased from a reseller, the customer is not supposed to be able to log in to CustomersDot to link their subscription. The email instructs to contact Support so we should go through the steps detailed in the [Provisioning subscriptions for reseller customers](https://about.gitlab.com/handbook/support/license-and-renewals/workflows/saas/associate_subscription_and_namespace.html#provisioning-subscriptions-for-reseller-customers) guide. | Purchased subscription should be linked to the correct namespace | Y |
| T-4     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). | Y | |
| T-5     | View Storage on Usage Quotas page | Navigate to Group's Usage Quotas page in staging.gitlab.com, then click the Storage tab. | Verify the purchased storage synced and the amount shown is correct based on the order. At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted add-on order. | Y | |
| T-6     | Sales-assisted add-on deal created | Ent Apps to create a sales-assisted add-on deal to add seats to the subscription in the staging environment (Zuora Central Sandbox). | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-7    | View Billing page | Refresh the Group's Billing page in staging.gitlab.com. | The Group should still show "currently using the Premium SaaS Plan (Formerly Silver)" but with additional seats in the subscription. | Y | |

</details>

<details><summary>TC-OH-F07</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should start with a SaaS product, and a CI Minutes add-on as well (confirm with Mark). The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592). This subscription will be setup as a sales-assisted ramps workaround, where this subscription represents the first ramp year. | The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  There should be an option to link the subscription with a namespace. | The Manage Subscriptions page shows the subscription.  | Y | |
| T-4     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-5     | Link the CustomersDot Customer with the GL.com User account | Back in CustomersDot, you should be able to link your CustomersDot Customer Account with your newly created GL.com User (staging).  Click the "My Account" button in the top nav bar, then click the "Account details" option.  Expand the "Your GitLab.com account" section and follow the steps for linking the account. | The CDot customer account should be linked with the GL.com user account. | Y | |
| T-6     | Link the Subscription with a namespace | Navigate to the "Manage Subscription" page in CustomersDot staging and find the subscription. Click the "Change linked namespace" button.  Select the group created on step T-4 and confirm the changes. | The subscription should now be linked to the group.  You should see the group name listed on the Manage Subscriptions page. | Y | |
| T-7     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). | Y | |
| T-8     | View Pipeline Minutes on Usage Quotas page | Navigate to Group's Usage Quotas page in staging.gitlab.com, then click the Pipelines tab. | Verify the purchased minutes synced and the amount shown is correct based on the order. At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted add-on order. | Y | |
| T-9     | Sales-assisted add-on deal created | Ent Apps to create a sales-assisted add-on deal to add seats to the subscription in the staging environment (Zuora Central Sandbox). | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-10    | View the subscription | Refresh the "Manage Purchases" page in CDot.  You should see the subscription with valid product and quantity listed. | The Manage Subscriptions page shows the subscription with correct product and quantity.  | Y | |
| T-11    | View Billing page | Refresh the Group's Billing page in staging.gitlab.com. | The Group should still show "currently using the Premium SaaS Plan (Formerly Silver)" but with additional seats in the subscription. | Y | |

</details>

<details><summary>TC-OH-F08</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a Self-Managed product. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive license email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot with activation instructions (e.g. activation code unless cloud licensing is disabled). | Verify the email was received with instructions on how to activate. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  You should see the activation code (unless cloud licensing is disabled). | The Manage Subscriptions page shows the subscription. At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted add on order.  | Y | |
| T-4     | Sales-assisted add on created | Ent Apps to create a sales-assisted add on order to add seats to the subscription in the staging environment (Zuora Central Sandbox). | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-5    | View the subscription | Refresh the "Manage Purchases" page in CDot.  You should see the subscription with valid product information listed with correct quantity. | The Manage Subscriptions page shows the subscription with correct product and quantity. | Y | |

</details>

<details><summary>TC-OH-F09</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a SaaS product. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-2     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-3     | Complete the provision through Support | Since this is a subscription purchased from a reseller, the customer is not able to log in to CustomersDot to link their subscription. The email instructs to contact Support so we should go through the steps detailed in the [Provisioning subscriptions for reseller customers](https://about.gitlab.com/handbook/support/license-and-renewals/workflows/saas/associate_subscription_and_namespace.html#provisioning-subscriptions-for-reseller-customers) guide. | Purchased subscription should be linked to the correct namespace | Y |
| T-4     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted renewal order. | Y | |
| T-5     | Sales-assisted renewal created | Ent Apps to create a sales-assisted renewal in the staging environment (Zuora Central Sandbox).  The subscription will now have renewed term along with a true up product. | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-6    | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should still show "currently using the Premium SaaS Plan (Formerly Silver)". Depending on when the renewed term starts, the subscription start and end date may not be updated yet.  If the renewal date is in the future, CDot would wait to sync this on the term start date. | Y | |

</details>

<details><summary>TC-OH-F10</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a Self-Managed product. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive welcome email | The email address referenced in the UAT spreadsheet should have received a welcome email from CustomersDot instructing the customer to reset their password. | Reset the password for this customer account and you should be able to login to CustomersDot.  | Y | |
| T-2     | Receive license email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot with activation instructions (e.g. activation code unless cloud licensing is disabled). | Verify the email was received with instructions on how to activate. | Y | |
| T-3     | View the subscription | Login to CustomersDot after resetting your password.  You should see the subscription with valid information listed on the "Manage Subscriptions" page in CustomersDot.  You should see the activation code (unless cloud licensing is disabled). | The Manage Subscriptions page shows the subscription. At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted renewal order.  | Y | |
| T-4     | Sales-assisted renewal created | Ent Apps to create a sales-assisted renewal in the staging environment (Zuora Central Sandbox).  The subscription will now have renewed term along with a true up product. | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-5    | View the subscription | Refresh the "Manage Purchases" page in CDot.  You should see the subscription with valid product information listed.  The term start and end dates should reflect the renewed term. | The Manage Subscriptions page shows the subscription with updated terms.  | Y | |

</details>

<details><summary>TC-OH-F11</summary>

| Step ID | Test Step   | Description | Expected Outcome | Testable? | Pass/Fail |
|---------|--------|----|----------|:---:|:---:|
| T-0     | Sales-assisted deal created | Ent Apps to create a new sales-assisted deal in the staging environment (Zuora Central Sandbox).  The subscription should have a SaaS product. The Sold To Contact for the subscription will use an alias of @a_luna's email which you can reference in [this spreadsheet](https://docs.google.com/spreadsheets/d/1NDtGfwqOOpZN534RHJjG9vrAMxM9jfY8ilgMklr0FQ4/edit#gid=326551592).| The subscription and customer can be found in Zuora Central Sandbox.  Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-1     | Receive namespace instructions email | The email address referenced in the UAT spreadsheet should have received an email from CustomersDot instructing the customer to link their new subscription with a GL.com namespace. | Verify the email was received with instructions to link the subscription with a namespace. | Y | |
| T-2     | Register a GL.com User | Navigate to https://staging.gitlab.com/ and register a new user with the testing email address.  Create a new group with this user.  This will be used later to link to the subscription. | The Billing page for this new Group shows a Group is able to be upgraded to Premium or Ultimate.  | Y | |
| T-3     | Complete the provision through Support | Since this is a subscription purchased from a reseller, the customer is not supposed to be able to log in to CustomersDot to link their subscription. The email instructs to contact Support so we should go through the steps detailed in the [Provisioning subscriptions for reseller customers](https://about.gitlab.com/handbook/support/license-and-renewals/workflows/saas/associate_subscription_and_namespace.html#provisioning-subscriptions-for-reseller-customers) guide. | Purchased subscription should be linked to the correct namespace | Y |
| T-4     | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should be shown as "currently using the Premium SaaS Plan (Formerly Silver)". The subscription details table should show  "Seats in subscription" as 1 (unless more were purchased in the order). At this point, we should reach out to Ent Apps to inform them we are ready for the sales-assisted renewal order. | Y | |
| T-5     | Sales-assisted renewal created | Ent Apps to create a sales-assisted renewal in the staging environment (Zuora Central Sandbox).  The subscription will now have renewed term. | Verify the Order callout was triggered and successful from the Customer Account page in Zuora. | Y | |
| T-6    | View Billing page | Navigate to Group's Billing page in staging.gitlab.com. | The Group should still show "currently using the Premium SaaS Plan (Formerly Silver)". Depending on when the renewed term starts, the subscription start and end date may not be updated yet.  If the renewal date is in the future, CDot would wait to sync this on the term start date. | Y | |

</details>

### Testing Status

Update the table below with the testing status (see legend below) as you progress through your use cases.

| Use Case ID | Tester | Status | Test Results |                                                                                       
|-------------|--------------|-----|-----|
| TC-OH-F01 | `@a_luna` | :white_check_mark:  | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_916077786 | 
| TC-OH-F02 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_916112125 |
| TC-OH-F03 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_919077837 |
| TC-OH-F04 | `@a_luna` | :white_check_mark:| https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_917240828 |
| TC-OH-F05 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_917368701 |
| TC-OH-F06 | `@a_luna` | :x: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_918876662 <br> Failure explained [here](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_923108372) and not related to OH specifically |
| TC-OH-F07 | `@a_luna` | :x: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_918942014 <br> Failure explained [here](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_923108372) and not related to OH specifically |
| TC-OH-F08 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_919089342 |
| TC-OH-F09 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_919090475 |
| TC-OH-F10 | `@a_luna` | :white_check_mark: | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_921481406 |
| TC-OH-F11 | `@a_luna` | :white_check_mark:  | https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4157#note_921511297 |

<details><summary>Testing Status Legend</summary>

| Emoji | Status |
| ------ | ------ |
| :white_check_mark: | Completed & Passed |
| :x: | Completed with some failures |
| :no_entry: | Blocked |
| :hourglass: | In progress |
| :white_large_square: | Not started |

</details>

### Documenting Testing Results

Each test case should have a single comment in this issue to document the results. 

- Create issues for anything noticed during testing.
- In the comment cell, add a link for each object created during the test (e.g. salesforce account, opportunity, subscription, group, etc.)

Utilize the following template for your comment:

| Step ID | Comments | Pass/Fail | Issues Created |
|---|---|---|---|
| T-7 | Followed steps as described | Fail | `#12345` <br> <br> `#98765` |

Story points: 5.0