Dev Instance QA

Dev Instance QA

Internal Testing is important! If this step is skipped, the upgrade is not guarenteed to go smoothly.

1. Internal Team should use the Testing Plan created in the Kick-off Meeting to test the upgraded instance.
2. Each item in the Testing Plan should be tested. A team member should sign off that each item is working as exptected.
3. The following testing steps should be followed:
   1. If a bug is found, a ticket should be created as a subtask of the upgrade project. 
   2. A resource should be assigned to fix the issue (BED or FED)
   3. When the resource has fixed the issue, it should be sync to the repo if it is a code change and reassigned to the AD for verification. 

Document Manual Updates that cannot be scripted

1. If any changes cannot be scripted, they should be documented in the upgrade project. All team members should be aware of the manual steps and someone should be responsible for implementing the when the upgrade is installed.
2. There are rare instances of fixes that cannot be scripted. If you are making a change in the workstaiton, it can likely be scripted.

Dev Instance QA Sign-off (Internal)

1. When all issues have been closed and the Internal Team agrees, Internal Testing is complete.
2. External Testing cannot begin until this step is completed.