Test Phase Issue Handling Process

Owned by Thomas Amsler
Last updated: Jun 20, 2007Version comment
2 min read

D R A F T

In case somebody finds an issue during the upgrade's test phase, the following process should be used to try to resolve the potential problem.

1. Issue Reporting

  • Create a JIRA and provide as much information as possible including screen captures if appropriate
    • When creating a JIRA, in the "Create Issue Step 1 of 2" screen select:
      • Project = Sakai
      • Issue Type = Bug
    • In the "Create Issue Step 2 of 2" screen make sure that you select
      • Affects Version/s: = Upgrade-2-4-x
      • Fix Version/s: = none
    • Assign the issue to Sandra Stewart

2. Resolving Issue

  • Everybody is encourage to periodically check the following JIRA filter to make sure that we don't miss any newly created issues for some reason.
  • As Sandra gets notified of a new issue, she will meet with Kirk and the programming team to discuss the issue in order to determine if the issue falls into any of the following JIRA priorities:
    • "critical" or "blocker".
  • If an issue is prioritized as "critical" or "blocker" and management decides that the issue needs to be resolved before we release SmartSite Prod v2.4.x to the public, the programming team will consult on how to best resolve the issue.
  • As the programming team tries to fix the issue, the team will update the corresponding JIRA with as much information as possible. The team will also provide an ETA for fixing the issue.
  • Fixes are made to sakai-trunk
  • Programming team should add comments that will help the Q/A team to create simple test plans if applicable
  • Once the programmers have committed a solution to the issue, the corresponding JIRA will be updated and assigned to Thomas Amsler for migrating the code to sakai-test

3. Code Migration Test

  • As JIRA's get marked as "Awaiting Migration for Testing" Thomas Amsler will prepare sakai-test with the latest code snapshot and change the JIRA status to "Migrated to sakai-test". An email will be sent to "sakaiprogrammingteam@smartsite.ucdavis.edu" notifying which JIRAs are ready for testing.
    • We will use sakai-test to stage any new code that resulted from fixing issues
    • We will run sakai-trunk on sakai-test, which will allow us to quickly build and bring up the test server with the latest code changes.

4. Q/A JIRA issues

  • Upon notification, the Q/A team will test the specified issues and mark them as "pass" or "no pass"
  • Management, Q/A, and programmers will review test results and discuss any unresolved issues
  • If an issue passes, Sandra changes the JIRA's Status to "Awaiting Migration to Smartsite"
  • If an issue does not pass, Sandra changes the JIRA's Status to Programming, the programming team will try to resolve the issue again.

5. Code Migration Production

  • Any issue that has a status of "Awaiting Migration to Smartsite" will be processed the following way:
    • Merge trunk source code changes to sakai_2-4-x branch
    • Create new production tag once all JIRA changes have been merged
    • Deploy new production tag on SmartSite Production nodes

6. Q/A SmartSite Production (if needed)

  • Once SmartSite production nodes are back online, Q/A team can verity fixes if needed