So we have a test/developer environment set up for Confluence as a place to test various plugins/upgrades etc. rather than doing it directly in the live/production Confluence instance. Both environments are a mirror copy of each other.
This is to prevent the situation where a Confluence plugin might cause system instability that would impact existing users.
My question is, based on these practices what is the best way to go about adequately testing a plugin in the test environment/instance of Confluence? Just play with it and see if Confluence goes down??
Any tips/guidelines? Thanks in advance.
Hi @Adam ,
We do perform similar tasks like what you mentioned. Basically what all we do is
Hi @Adam ,
it is great that you're doing this at all! This is a great practice and highly recommended of course. Now as far as how to test the answer is hard to definitively state since there are so many variables here. What I would say is first and foremost verify that the application does what you wanted to do. After that the real testing comes - making sure of the application doesn't do something that it shouldn't. Here are some of my thoughts: