What is the most effective way to test our existing automations in the lower environments before upgrading production orchestrator and the production robots?
Do we start with upgrading our studio environments first or do we start testing the existing compiled packages on the test orchestrator first?
At first I thought we should test the existing automations on the test orch first, but chatgpt says you have to upgrade the studio first. That kind of makes sense because if the packages break in the orchestrator, the only way is to fix them is with the 2025 studio. However, the links that chatgpt used to give this decision was just a link on how to upgrade the studio and how to upgrade the robots, not how to test after upgrading.
By effective I mean, you do not need to run all the transactions in every bot just to test the upgrade, right? So, I am looking for the most comprehensive ways of testing that can be done quickly.
Just run the automations as you normally would. If they work, there’s nothing to do. If they don’t work, then you have to figure out why and fix it - which could mean upgrading dependencies, fixing code, etc.
There are several automations and they are all very long. To check compatibilities, is it necessary to run the entire process or is a version upgrade more about certain specific touch points, like library versions?
Library versions are definitely something that could be an issue if they’re old. Yes you should run the entire process. Just run it like you normally would to test it.
Do you have separate orch for lower and prod environments or useing different tenant for lower and prod environment?
If different orch then upgrade lower environment and then test it
If tenant separation then it will be difficult do test directly but you can find the equivalent version of cloud enterprise trail version it’s kind of similar but not exact one
&Yes we do. Our lower environments are separated by tenants and the production orch is on a different server. I am not sure how this makes a difference, but in case you are asking if we could use Automation Ops, No, we are not using it. Moreover this is all on-prem installation.
