Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing Checklist - User Profile Part 4: Moving Module 1 Content to User Profile #1212

Open
6 of 11 tasks
sonyekere opened this issue Feb 13, 2025 · 1 comment
Open
6 of 11 tasks

Comments

@sonyekere
Copy link
Collaborator

sonyekere commented Feb 13, 2025

Hello Everyone. Please see the checklist below for testing. We ask that you review the task list, check off each item, and provide your initials and the date of completion.

  • @mnataraj92 to create test scenarios and @robertsamm to review
  • @cunnaneaq to create test ppts in dev and stage ( DONE in dev, but needs to be done in stage as well)
  • @JoeArmani will backfill module 1 alternate contact test data for one ppt prior to user profile migration
  • @rohanjay10 will send out the test invite for dev and stage (DONE for Dev and Stage)
  • Once confirmed all test ppts are created and data has been backfilled, @JoeArmani to migrate module 1 to user profile prior to dev testing and alert @robertsamm when migration is complete
  • @jacobmpeters to collaborate with Joe to flatten the BQ data in dev and stage. (@jacobmpeters please confirm with Joe on accurate timing of this event)
  • @rohanjay10 will lead testing for dev and stage
  • @robertsamm to fill out module 1 surveys during or offline of the dev testing call ( scenario 6 and 7 to ensure that Ops does not see alternate contacts)
  • @depietrodeanna to check the Spanish content during the live testing in dev and stage
  • @JoeArmani will verify the ppts during dev and stage testing and will check the data in the backend
  • Ops/ @robertsamm to alert @jhflorey or Tony to run data destruction at the end of dev and stage testing ( we are not retaining any variables within the stub records)
@jacobmpeters
Copy link
Collaborator

@jacobmpeters @sonyekere Adjusting the flattening for this issue needs to take place after the release. I will run a script that will read the updated schema in the raw Connect dataset and will update the flattening configuration files for the corresponding tables in the FlatConnect dataset. I will complete this after the release and will update this issue when done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment