Testing a live upgrade
It's a good idea to discuss testing requirements with the customer before you upgrade the system. Your post-upgrade testing should focus on the following:
- Functionality that's used frequently by the customer.
- Advanced customizations. In general, testing customer customizations should take a large amount of the allotted test time.
- Data integrity. Carry out data checks to ensure that upgraded data appears as expected.
Test Action |
Success |
---|---|
Log on is successful |
|
Mail merge and document drop functionality working |
|
Report writer presenting in all formats (HTML, PDF, CSV, XLSX) |
|
Email management functioning as expected, including customizations |
|
Functionality regularly used by the customer working as expected |
|
Previous functional integration with third-party database functioning as expected |
|
Advanced customizations (.ASP pages) functioning as expected |
|
Custom icons copied to new install location |
|
Outlook and Exchange Integration functioning as expected |
|
Library location is correct |
|
Add/Find/Edit/Delete records for each entity working as expected |
|
System help functioning as expected |
|
Data upload functioning as expected |
|
Interactive dashboard loads successfully (My CRM | Dashboard) |
|
Interactive dashboard loads successfully in the Company context (Company context | Dashboard), and the default dashboard is the Company Summary dashboard |
|