Upgrade Testing

Extensive testing is done ahead of Sitka’s annual upgrade.

  1. Use the testing checklist for the upgrade as a guide.

    1. This include a list of the new and existing features and functionalities that need to be tested.
  2. Test on the upgrade server and compare the behaviour with current documentation and the production server.
  3. Record the results of your testing in the checklist.

When an issue is identified:

  1. Create an RT ticket in the Testing queue.
  2. Link the RT ticket to the parent ticket for the upgrade.
  3. Report only one issue on a ticket.
  4. Add the "3.x Upgrade" tag and any relevant EG-tags
  5. Include the steps to take to replicate the issue.

    1. Be as specific as possible describing your issue:
    2. What were you doing? What did you expect to happen? What actually happened? How does it differ from the current behaviour on the production server?
  6. Include screenshots.
  7. Attempt to replicate the issue on a Sitka upstream server or an Evergreen community test server running the same version of Evergreen.

    1. If it can be replicated it’s an upstream bug and needs to be reported to Launchpad.

Copyright © 2008-2018, BC Libraries Cooperative