Process assumes Test Plan has been created and approved
  1. Test cases organized and kept in Confluence KFS Test Case Repository
    1. Naming convention
  2. Jiras created in kfsqa project as tasks
    1. Make sure correct Component is selected
      1. do we need to add another component for "general" issues that are discovered?
    2. broken down by sections that reflect naming convention
      1. need to identify naming conventions
  3. Test cases are added to Jiras as attachments (use Excel 2003 .xls version) use latest version from repository
    1. Sub-tasks if can be divided up that way, or a single Jira for each test case? (See CoA)
      1. I'm leaning towards a separate Jira for each test case assigned. They need to be created anyway whether it is a task or a subtask. If a particular test (spreadsheet) is failing it will be easier to assign and track I think. Also, you could then attach the test case as soon as the Jira is created
        Unknown macro: {float}

        Don't forget info on using Jira (attaching files, screens shots, etc.)
        [KFSIMPL:Modifying an existing JIRA Issue]

  4. Once all Test Cases have been identified and organized for a particular Test Plan; they are attached to Jiras and can be assigned.
    1. Identify who has been assigned to run which tests
      1. We need to identify testing resources during the discovery phase
  5. Tests will show as "Open" in Jira if they are unassigned.
  6. The Testing Coordinator assigns the Jiras to the appropriate tester.
    1. Jira will still show as "Open" in Jira
      1. created an additional saved filter to show "Open" and "Assigned"
  7. Tester selects "Start Progress" in Jira workflow
    1. Status changes to "In Progress" and is reflected in the dashboard.
      1. Tester can change to:
        1. Stop Progress (Status changes back to "Open" and "Assigned" in dashboard
          1. Will we have a way to mark progress? What should they do with the spreadsheet? Save locally and add comment to Jira?
        2. Resolve Issue (Status is marked as "Passed")
          1. Have tester re-attach spreadsheet to Jira changing the name by appending their NetID at the end
        3. Mark as Failed
          1. Have tester identify failed steps and document in the spreadsheet. Add comments to Jira with as much information as possible.
          2. Testing coordinator will attempt to identify problem and assign to correct support person
            1. Linked Jira or should we assign directly to appropriate person? If so do we leave status as failed and reassign? When ready for re-test support person could then assign to "unassigned" then status would change back to "Open" and "Unassigned" meaning ready for test
            2. May want to create an additional saved filter to show "Failed" and "Assigned"?
            3. What happens when support person does a "Start "Progress" if they are working on it? It will look like is is in testing status
        4. Mark as Blocked
          1. Need to have make sure this is "followed" by as many as folks possible. Maybe have it send email to "kfsqa-feedback", I know that would create a Jira in a separate queue, but blocked issues need to be resolved quickly.
        5. Mark as Deferred
          1. Need to make sure that comments are added to Jira to identify the reasons this test wont be run
  8. Testing Coordinator would then monitor the appropriate Jira dashboards to track testing progress
    1. Set up filters and dashboards ahead of time for all testing and each module
    2. Monthly we would take metrics and update the KFS Test Case Trending charts that we will use for status and tracking overall progress
    3. At the bi-weekly QA Status meetings we will provide updates to module leads (and others) using the Jira dashboards and Test Case Status Charts
  • No labels