The following steps should be followed when testing issues reported by libraries:
-
Ensure you have all the relevant information from the library.
Attempt to replicate the issue on Sitka’s testing server.
-
Make sure to use the same or equivalent accounts, records, items, etc.
-
Do not use your Sitka Staff account for testing.
-
Make sure to use a test server running the same version of Evergreen as production.
-
Detail your testing as a comment in the RT ticket. Include the steps you took, the barcodes etc. you used, and
the results you got.
Search Launchpad to see if a bug already exists for the reported issue. If a
bug report doesn’t exist yet further testing is needed.
-
If you find an existing bug click This bug affects X people. Does this bug affect you? to indicate that
we are affected by the bug. If not already in the bug, add a comment to indicate that it affects the version of Evergreen you tested.
-
Add the Launchpad bug number to the RT ticket and let the library know it’s a known issue.
-
When available test the issue on a Sitka test server running a newer version of Evergreen (this will generally
be available in the lead up to the annual upgrade).
-
Test the issue on an Evergreen community test server running the same or newer version of Evergreen.
-
If the issue can be replicated on an Evergreen community test server
report the issue to Launchpad.
-
Follow the procedure to move the ticket into the Sitka Bugs queue.
Note
If you are unable to replicate the issue on a Sitka test server escalate the ticket to the Support Operations Lead.
