Testing Confluence upgrades


I upgraded confluence from 3..02 to 4.2.6

I had to upgrade to 3.5.17 to get to 4.2.6

Question is do I have to test the upgraded version of confluence in 3.5.17 and then upgrade to 4.2.6 and test

Or is it just sufficient to test upgraded version in 4.2.6

What is the recommended approach.

I know testing is always good, but want to know where to spend my time in testing.

1 answer

1 accepted

1 vote
Accepted answer

I would concentrate mostly on 4.2.6 although because of the usermanagement changes in 3.5 I would keep the 3.5 instance around for comparison and testing in case issues do crop up in 4.2 that you can't narrow down to a 4.2 issue

1. Upgrade to 3.5.x

2. Run up 3.5.x, update plugins and do some user tests such as logging in as various users and ensuring access. Making sure the same users/groups are present and everything appears to be in order

3. Backup in parrallel the 3.5 instance

4. Upgrade to 4.2.6

5. Run 4.2.6, update plugins and start extensive testing here

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Organizing your space just got easier - Page Tree Drag & Drop is here

Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...

60 views 3 2
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you