Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Testing CRM Features for YARDI Data Migration

Test Cases and ResultsDate CompletedJIRA Ticket
Household Member Changes (DOC)25/05/2021

Jira Legacy
serverJIRA
serverId171541f2-d15a-30f9-88a2-170d76c90864
keyHSIF-2930

File Merging (DOC)

Jira Legacy
serverJIRA
serverId171541f2-d15a-30f9-88a2-170d76c90864
keyHSIF-2941


Data Synchronization Test scenarios to confirm the following:

  • Does the client information accurately reflected in the CRM
  • Client information mapped to the accurate fields in the client profile and the RGI service delivery
  • Are the accurate household members linked to the right RGI service delivery

Test Scenario 1: New applications created in YARDI (new client)

StepStep DescriptionExpected ResultActual Result

Additional Notes

Steps:

  • Create application in YARDI
  • Data import to CRM
  • Review Client Profile & service delivery created in CRM
    • YARDI Client information is mapped to new CRM profile and RGI service delivery
    • Confirmed Accurate

    Test Scenario 2: Existing applications created in TAWL, now in YARDI (existing client)

    • YARDI client information (Applicant Code) is mapped to existing CRM profile and RGI service delivery
    • No duplicate client profile is created

    Steps:

    Find existing Client application in YARDI (from TAWL)
    • *Household ID to be updated to YARDI Applicant Code
    • Remaining Fields are all confirmed accurate

    Test Scenario 3: Existing applications created in TAWL, now in YARDI (existing client); Client profile in CRM were merged with other profiles from legacy systems

    • YARDI client information (Applicant Code) is mapped to existing CRM profile and RGI service delivery
    • No duplicate client profile is created

    Test Scenario 4: File updates in Existing applications

    • Existing applicants information is mapped to the existing CRM profile 
    • Check for duplicate profiles
    • Updated information is saved in CRM CRM

    Steps:

    1. Get applicant Code to view existing application
    2.  Select a tab to edit applicant information 
    3. Update information 
    4. Save and continue 
    • Confirmed Accurate

    Test Scenario 5: File updates in New applications

    • New applicants information and updates are saved 
    • Status is updated if required required

    Steps:

    1. Open "Service Tickets" 
    2. Select "In-Progress" 
    3. Select "Tasks" to complete or update information for a new application
    • Confirmed Accurate

    Test Scenario 6: File Splitting - Household Member establishes new application (assigned new Applicant Code)

    • Does Household Member with a new application create a new client profile in CRM - requiring a manual merge
    • Can new client record be matched with and update existing CRM client profile instead
    • *CRM behaviour to be adapted - household member to be removed from RGI service delivery

    Test Scenario 7: Removing Household Members

    • Remove household member on RGI service delivery
    • *CRM behaviour to be adapted - household member to be removed from RGI service delivery

    Test Scenario 8: Application status in YARDI no longer Eligible, Applied, or On Offer

    • Client record no longer appears in CSV data file
    • Client's RGI waitlist file is assumed 'Cancelled', 'Ineligible', or 'Housed'
    • CRM to change RGI service delivery status to 'Closed' & End Date
    • Confirmed Accurate

    Test Scenario 9: Only variance data updates existing CRM client profiles and RGI service deliveries

    • Client record that is 'Eligible', 'Applied', or 'On Offer' is present in the csv data file
    • Client record that is identical to previous copy does not override/update CRM profile & RGI service delivery
    • Only client records where data varies from previous copy updates CRM profile & RGI service deliveries
    • Confirmed Accurate