Process assumes Test Plan has been created and approved
- Test cases organized and kept in Confluence KFS Test Case Repository
- Naming convention
- Jiras created in kfsqa project as tasks
- Make sure correct Component is selected
- do we need to add another component for "general" issues that are discovered?
- broken down by sections that reflect naming convention
- need to identify naming conventions
- Make sure correct Component is selected
- Test cases are added to Jiras as attachments (use Excel 2003 .xls version) use latest version from repository
- Sub-tasks if can be divided up that way, or a single Jira for each test case? (See CoA)
- 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]
- 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
- Sub-tasks if can be divided up that way, or a single Jira for each test case? (See CoA)
- Once all Test Cases have been identified and organized for a particular Test Plan; they are attached to Jiras and can be assigned.
- Identify who has been assigned to run which tests
- We need to identify testing resources during the discovery phase
- Identify who has been assigned to run which tests
- Tests will show as "Open" in Jira if they are unassigned.
- The Testing Coordinator assigns the Jiras to the appropriate tester.
- Jira will still show as "Open" in Jira
- created an additional saved filter to show "Open" and "Assigned"
- Jira will still show as "Open" in Jira
- Tester selects "Start Progress" in Jira workflow
- Status changes to "In Progress" and is reflected in the dashboard.
- Tester can change to:
- Stop Progress (Status changes back to "Open" and "Assigned" in dashboard
- Will we have a way to mark progress? What should they do with the spreadsheet? Save locally and add comment to Jira?
- Resolve Issue (Status is marked as "Passed")
- Have tester re-attach spreadsheet to Jira changing the name by appending their NetID at the end
- Mark as Failed
- Have tester identify failed steps and document in the spreadsheet. Add comments to Jira with as much information as possible.
- Testing coordinator will attempt to identify problem and assign to correct support person
- 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
- May want to create an additional saved filter to show "Failed" and "Assigned"?
- What happens when support person does a "Start "Progress" if they are working on it? It will look like is is in testing status
- Mark as Blocked
- 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.
- Mark as Deferred
- Need to make sure that comments are added to Jira to identify the reasons this test wont be run
- Stop Progress (Status changes back to "Open" and "Assigned" in dashboard
- Tester can change to:
- Status changes to "In Progress" and is reflected in the dashboard.
- Testing Coordinator would then monitor the appropriate Jira dashboards to track testing progress
- Set up filters and dashboards ahead of time for all testing and each module
- Monthly we would take metrics and update the KFS Test Case Trending charts that we will use for status and tracking overall progress
- 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