Testing in Development and QA

Below are some basic test cases that support groups will want to test before moving changes into production.  The results will help ensure that both the configurations and roles are working as expected.

  1. Each person in the support group can log in
  2. Each person in the group can see change tickets
  3. Change managers can enter and self approve changes (Impact Level = 4)
  4. Change approvers can approve changes in terms of timing (Impact Level > 3 and Class = Standard)
  5. Change approvers can approve changes in terms of content and timing (Impact > 3 and Class = Normal)
  6. Change viewers cannot change or modify tickets
Quality Assurance in Production

Below are the fields that the Service Advocate and Service Coordinators should pay close attention to to ensure that the information is accurate and helpful:

  1. Correct service is listed
  2. Notes have enough information for managers to understand the change and impact on other services
  3. Any relevant components (CI = servers, applications, etc) that are being changed are listed in the notes for reference
  • No labels