[Unify Premium/Ultimate] UAT

• Summary
• Pre-requisite
• Useful Links
• Recommended Procedure
• Test Cases
• Bugs Identified
• Open Questions
• Sign-offs

Summary

This issue is to perform UAT for migrating SaaS and Self-Managed subscription to the unified version.

Epic: [Unify purchase flows] SaaS/Self-Managed Premiu... (&18567)

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).
• 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.
• Clear any caches.

Useful Links

Add any links that are helpful to carry out testing such as links to the flows involved, etc.

Recommended Procedure

1. Create a Task 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.)
2. Create a Test Case 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.
   • Apply the appropriate labels following the test case management labels documentation.
3. Before testing a Task, assign yourself to it to avoid multiple people testing the same scenario.
4. If needed, assign a tested Task to a PM for review.
   • Use the comments section in the Task to discuss any unexpected behaviour and co-ordinate on follow-up actions.
5. PM signs off on the Task if everything looks good, closes the Task, and marks it as complete in this issue.
6. Document bugs and general questions in this issue's description.

Test Cases

Test cases covered by automated E2E tests can be marked with ⚙️ and linked to the test

Create new tasks for each test case using the User Acceptance Test Task template. Refer to the master spreadsheet for test case ideas.

Scenario #	Task	Test Case	Scenario	Expected Outcome	Product Sign-off	UX Sign-off

Bugs Identified

Bugs	Testing type (Automated/ Manual)	Resolution	MR	DRI

Open Questions

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