Testing status and behavior of Jira instances after a change

[Gaston Valente]

Hi,

I'm working with several Jira instances, some of them with large and complex workflows.

I'd like to know and discuss about the testing techniques that are being used to enforce correct status and behavior after a change like:

1. Add-On update
2. Jira update
3. Change in business rule or requirment

With certain projects we use some automated scripts that consumes the rest api to test and validate the instance after an update, something like a homemade "ci".

Do you use similar or different solutions?  

Thanks!