Update Testing. Full test or just go with it?
I am interested in hearing from other users about the amount of testing that is done within your Finance and IT areas to upgrade OneStream to a higher version.
Do you perform minimal testing of Cub...
Forum Discussion
Hi Bill,
We have a testing script that we run through for version upgrades. Our company process is to run upgrades through a change control ticketing procedure which means we need testing documentation/proof attached for others to review and sign off on. Some of the things we test after upgrading our development environment (not in any particular order):
- UAT script for OSMA (the master data/security tool originally named RequestIt, developed by FInit)
- Compile rules
- Connectors and workflow steps
- Performance/timing on QV and CV refreshes and submissions
- Sample dashboard and data management job testing
- CV financial statement comparison before and after upgrade and consolidation for limited time frame
Depending on how significant and user-facing the changes are, we may involve users and UAT scripts for their areas of work. All this is done in DEV then submitted for approvals before the prod upgrade is scheduled (we’re cloud based). OS is owned by finance so the financial systems team takes care of all of the above. Hope that’s helpful!
-Nicole
Hi Nicole,
We're very interested to hear more about your testing script since we are also cloud based. Is this something you have developed in your OneStream environment or is it an external tool?
-Sara
Hi Sara,
The UATs started as implementation testing scripts and were developed with the users to mimic their normal processes. Over the years we've added and adjusted as processes change or new tools are implemented. We built the scripts and we run through the steps prior to every upgrade. Let me know if that answers your question!
