Knowledge Base

What functionality should I test before an upgrade?

By Alexander posted 02-20-2015 20:51

Although we strive to make the upgrade process as painless and transparent as possible, new versions of Jama Software will contain new functionality and enhancements that may alter the way certain parts of the software behave. This is especially true if your current production version is more than one version back from your target version. Jama Software recommends that, before applying any upgrade to your production server, you run through the upgrade process on a test environment to make sure your organization's configuration and functionality will not be negatively impacted by any of these changes.

  • Create some dummy data. Run through your normal process, making sure to test the parts of the application your organization frequents. If your users spend most of their time in the Review Center, create some reviews and revisions, comment and approve and close them. If you use the collaboration stream, make some comments on an item, flag questions and answers and filter to find old comments. If there have been any changes to Jama Software's functionality that will impact your workflow, you'll likely find them here.
  • Test new features. If you plan on utilizing any new features Jama Software has rolled out since your last update, try configuring them roughly how you plan to use them in production and go through your normal workflow with them enabled. We're very excited about our new features and want you to make use of them; however, some of our new tools solve complex product delivery problems and may require best practices to be developed that are particular to how you use Jama Software. It's best to get these vetted and clearly understood before they are released to a wider userbase.
  • Get information into and out of Jama Software. Try importing and exporting via different methods. You may find that something is not working as expected, such as images not showing properly in Word exports. Most of the time, these are configuration issues arising from updating one or more components along with Jama.
  • Test custom reports. Because these reports hook into low-level internal data structures we use to develop the product, Jama Software cannot guarantee that the calls and resources used in these reports will remain consistent between versions. We'll do our best to call out any major changes in release notes, but if you rely on any custom reports for your work you should test them thoroughly to ensure there have been no breaking changes.
  • Test Jama Software integrations. If syncing Jama Software items with other applications is part of your normal process, you should test the integration prior to upgrading your production instance. Whether your Jama Software is integrated with other applications using Jama Software Integration Hub or Jama Software's legacy connectors, it is best to test the integration for one or two sets of items first in a test environment. Make sure you sync items in test instance of Jama Software against a test environment of the connected application. For example, if you sync with JIRA and you also have a JIRA test instance, create one project mapping similar to what you have in your Jama Software production and test your Jama-JIRA sync. 
  • Test custom API integrations. We will not make changes to API calls without warning, but new features can sometimes impact the way those calls operate and return data. For example, in Jama Software 2014.1, we introduced relationship rules, which added some new restrictions to how items could relate to each other and affected the SOAP API's relateItems(...) call. Review any custom integrations to make sure you understand how new features might impact their operation, and test them against the new version to ensure they're still working as expected.