| Table of Contents |
|---|
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.
We can use EAS PROD because it is not in PROD.
EAS will be in PROD after this release.
| Table of Contents |
|---|
...
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.Run
Penultimate AVS-EAS ETL
...
Confirm Readiness (October 12, 2011)
The database preparation may take overnight.
Here we just want to confirm that we are ready to go into parallel on Monday Morning.
...
(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
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.
- Jeff and Paul will be available on site at DBI for training as needed.
- At the end of each day (or week), confirm that AVS QA and AVS PROD are materially the same.
- TODO - We'll need some SQL to generate a list of changes that we can easily compare.
- TODO - does AVS have a way to extract "changes since yesterday"?