Skip to content

UAT Test Scenarios Review

VIDEO TRANSCRIPT | Recorded: 2024-08-15 | Verify against current system state

Abstract

Documents concerns with UAT test scenarios for Salesforce migration. Test scripts are unclear about which Salesforce objects to use, reference fields that don't exist (e.g., "subscriber field" on orders), and don't match the expected order-driven workflow from Aptify. Additional issues with test documents not matching ClickUp tasks and missing navigation guidance.

Key Procedures

  • Execute UAT test scenarios from shared documents
  • Record pass/fail results on test document
  • Copy completed scenarios to ClickUp
  • Create new orders in Salesforce Orders object
  • Navigate between related objects (Orders, Subscriptions)
  • Identify missing fields and document as failures

Notable Statements

  • 0:00:23 "The team is filling out pass or fail on this document and then I'm copying it over to ClickUp"
  • 0:00:52 "We're running into issues following the steps"
  • 0:01:24 "When you open a new order... it's not going to have an ID field to begin with"
  • 0:01:34 "They didn't understand what they needed to do next and I also wasn't really clear on what was supposed to happen"
  • 0:01:54 "We haven't been given information on how the order process works"
  • 0:02:54 "There's no subscriber field on here so then people are getting confused"
  • 0:03:22 "We don't normally set up subscriptions manually in Aptify. All of this happens when you order a product"
  • 0:03:35 "If you order an NP membership a subscription gets created based off of that product"
  • 0:03:54 "McKenna has just been making some assumptions but I don't want them to do that"
  • 0:04:38 "At least if there was an object column or something... that showed us where that object lives" ACTIONABLE
  • 0:05:17 "The steps that are listed here don't match up with the steps that are listed in this link"
  • 0:05:43 "I just don't know what to do there"
  • 0:06:00 "I think some training on the expectations maybe some video demonstrations of how we're supposed to go through this would help" ACTIONABLE

Systems & Configurations

Systems Mentioned

  • Salesforce (Orders object, Subscriptions)
  • ClickUp (test tracking)
  • Aptify (current system reference)
  • Shared documents (Google Docs or similar)

Specific Configurations

Item Value/Setting Timestamp Notes
Order status Draft 0:02:00 Default for new orders
Order number field Auto-generated on save 0:02:14 After required fields filled
Required order fields Account name, Start date 0:01:49 Minimum to save
Test workflow Document > Completed folder > ClickUp 0:00:40 Current process

Credentials/Access Mentioned

  • Super admin access for all testers

Vendor Contacts Mentioned

None mentioned in this recording.

Errors & Troubleshooting

  • Issue: Test scripts reference non-existent fields
  • Cause: Documentation not updated for actual Salesforce configuration
  • Resolution: Need test script revision with correct field names

  • Timestamp: 0:02:51

  • Issue: Test steps don't specify object location

  • Cause: Missing navigation context in test documents
  • Resolution: Add object/location column to test scripts

  • Timestamp: 0:04:38

  • Issue: ClickUp tasks don't match test documents

  • Cause: Documents maintained separately
  • Resolution: Need to reconcile and sync test steps
  • Timestamp: 0:05:17

Transcript Gaps & Quality Notes

  • Feedback recording for vendor team before scheduled meeting
  • References to McKenna as tester making assumptions
  • Screen sharing of test documents and Salesforce not captured
  • Recording mentions upcoming discussion "tomorrow"
  • Some test scenarios have no ClickUp link