Hi, due to the number of plugins, plugin vendors, etc it's hard to create test scripts. A lot of issues happen at the UI level as well. It's even harder with JIRA due to a lot of custom post functions, conditions, validators, etc that can all break.
Unfortunately there aren't any test scripts due to the complexities and level of customizations.
I think the most critical thing you need to test are your workflows, integrations/automations, plugins, and other customizations. You need to trade off cost versus risks and usually this means focusing on things that are more unique for your environment versus general things that more likely coverted by Atlassian or plugin vendors testing. This usually means that unique test scripts are likely needed. You need a test environment that represents your production setup where where you can easily create issues and make configuration changes. Allow some of your more advanced users to interact with the new environment to discover any UI or functional areas that may need additional education or warnings.
For test scripts, consider using Groovy Integration Test Framework (GINT) with it specific JIRA testing support. This can fairly easily (low cost) cover your some of your workflow testing (create and progress issues) and other things. Having at least some automated tests can help lessen the burden of your upgrades.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG