Instance Post Upgrade Check
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2016 03:35 PM
Hi All,
I created a request from Service Now for my Dev instance upgrade, Which is done now.
Upgraded from Eureka to Helsinki.
can anyone provide me the checklist which i should be going through after the up gradation??
and also suggestions on what might have broke? What precautions should i take before i update my Prod instance.
Thanks,
Nanda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2016 04:43 PM
Going through that many versions at once, I'd be doing a full on regression test of the entire kit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2016 04:45 PM
Robert,
What do you mean by regression test? How do you suggest me to test everything?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2016 05:20 PM
So you're jumping over two significant UI updates, at the very least things are going to *feel* different for your users, so the primary users / stakeholders of the app should test for usability. If you're using GRC, that product basically got nuked from orbit and remade in the very image of the Almighty (morganhunter). It would need significant re-testing. Custom apps? Nothing will do but a full test of all features.
The best people can give you here, knowing nothing about the specifics of your deployment, is give you some generalized platform checks, but I can almost guarantee you that any significant failures due to upgrade will be caused by instance specific configurations. A jump that size should really have a testing project behind it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2016 05:29 PM
This is small, but caused me a lot of corrective work.
If you have a variable that pulls from a choice list, in Pre-Helsinki it would obey either the "Mandatory" rule (making sure the choice list had a null value) or obeyed the source choice field's dictionary attribute of "include none". In Helsinki you need to declare the variable to specifically have none, even if your source choice field has it.