Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Final Data Conversion Planning Meeting notes
- Jules Levin
- Manpreet Sidhu
- Brad Fernandes (Unlicensed)
Date
Dec 16, 2020
Participants
@Jules Levin
@Sidra Zafar
@john.humphreys
@Rachel Forbes
@alexia nicholson (Unlicensed)
@Yeng Sembrano
@Manpreet Sidhu
@Brad Fernandes (Unlicensed)
@The Ho Trang
@AlainGasquet
@Monica Kluegel
Copies
@Griffin Homan (Deactivated)
@Lori Stirling (Deactivated)
Agenda
Entry criteria (Counts, Test scenarios for AQ to test before handing over to USYD)
Test cases to be completed
Priority sequence of test execution
Test tools (Scripts, ??)
Exit criteria (what needs to pass in order to commence PVT and turning on integrations)
Discussion
Entry criteria (Counts, Test scenarios for AQ to test before handing over to USYD)
After Advance is in Read-only mode, create a count of all objects and provide to AQ to use for validating the record count.
Counts check
Accounts/ Contacts
Chart of Accounts
Once count check is complete, load other objects
Opportunities
Gifts
Activity report
Campaigns
Education
Check objects for mandatory fields -
Accounts
Name
Address
Contact number
Recognition credit
Relationships
Do not contact (Inactive account)??
Contacts
Name
Address
Contact number
Link to Account
Relationships
Chart of Accounts
Account name on the Chart of Account
Mandatory codes should be RC/PC codes (Segments 1, 2, 3)
Opportunities
Name
Amount
Close date (could be future dated)
Owner
Link to Account
Gifts
Gift Pledge records -> should have a designation
Transaction records -> should have a designation
Transaction -> Recognition credit
Link to Account
Activity report
Campaigns
Education
Alumni should have 1 education record
Data conversion testing and Priority sequence of test execution
Test cases to be loaded in Jira based on mapping of Objects (64 tables). Action for @Bradley Fernandes
Assignment of test cases and execution priority as follows -
Object | Who | Comments | |
|---|---|---|---|
| 1 | Accounts/Contacts | Yeng/Rachel and Everyone | On Morning of 4 January, everyone will commence Account/Contact testing. If results positive, by midday COA testing will commence |
| 2 | Chart of Accounts | Monica/The-Ho | Testing to commence on 4 January after initial Account/Contacts testing. @Monica Kluegel to identify allocations codes for testing |
| 3 | Gifts | Monica/The-Ho Rachel/Yeng John | Monica, Rachel, John to meet and select IDs for testing Rachel, Monica, John test from for business perspective. The-Ho, Yeng will do second pass of counts. Second group do basics on a range of accounts and blanks and global checks, reversal tables. |
| 4 | Campaigns | Rachel/ Manpreet | Appeals Is priority but will test all mapping. No prep required |
| 5 | Opportunities | Alexia/ Sidra | Tested in parallel with Campaigns. @alexia nicholson (Unlicensed) will find relevant ten IDs for testing. @Sidra Zafar Sidra will look at totals and other counts. Opportunity owners, relationship management, stages, - After migration will be updated. Stages will be updated before the 4th by @Yeng Sembrano . |
| 6 | Education | Rachel/ Manpreet | @Manpreet Sidhu to call out what Rachel should test from front end. |
| 7 | Reports | Alain | If report testing is blocked, @Rachel Forbes will provide 10 IDs for @AlainGasquet to test |
3. Defects to be assigned to @Griffin Homan (Deactivated)
4. Daily meeting to be scheduled at midday to review testing progress