Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Preamble

This page serves as a plan for parallel testing EAS and AVS.
During this exercise, we will use DBI QA (concrete name is DEV3) and EAS PROD.
DBI reserves the right to run in parallel for longer than 3 weeks if necessary.
During this testing, EAS support shall available during business hours.

  • Paul 415-889-3963
  • Jeff 415-722-0061

Refresh AVS QA from AVS PROD Prepare Databases (Nov 1) (DONE)

  • Copy the DBI production database(s) to the DBI QA environment.

Penultimate AVS-EAS ETL (Dec 2)

  • Run this ETL for the second to last time, then disable it.

Populate AVS QA with primary keys from EAS.

After penultimate AVS-EAS ETL, DBI must do the following:

  • get the avs load results data from the FTP server
  • add the "eas_id" column to the AVS addresses table
  • use the avs load results data to update the eas_id column

Begin Parallel Testing (Dec 5 through Dec 23)

  • confirm that the Change Notification is configured with DBI QA as target.
  • For every address modified in AVS PROD, make the same changes in EAS PROD.
  • At the end of each day, confirm that AVS QA and AVS PROD are materially the same.
  • TODO - does AVS have a way to extract "changes since yesterday"?
  • No labels