In this second episode I will try to go deeper in technical informations. It is a important step to prepare our system to design test case management workflows. First episode link : www.testandtry.com/2009/07/01/test-case-management-in-jira-1/
1. New issue and sub-task types
Test Case
Main issue for collecting test cases in out solution. We can design and add new icon for good looking factor.
Test Case Step
New subtask for collecting steps to reproduce the test scenario. Steps are some kind of project tasks for low level testers.
Test Case Result
We must add new subtask to obtain good reporting level. If tester is closing the test case with pass or fail result this subtask must be created including comments.
2. Custom Fields
Adding new custom fields for my solution is not necessary, it is just a prompt of things You may need it sometimes.
Build Run Against
New field to gain knowledge about build number test case is run against. In JIRA we often have only three version places 1.1.1.x but in testing we must know the last one.
Field type = text.
3. Screens
Test Case Screen
Create new screen for test case create and edit with following configuration. Make this screen default for test case issue type in Screen Schemes.
- Issue Type
- Summary
Short description of test case. - Description
Long description of software feature being tested or requirements summary. - Affects Version/s
Application version to which test case is written. - Component/s
Application component to which test case is written. - Priority
How important this test case is ? - Assignee
Test case steps executor – tester. - Due Date
Deadline of test case execution. - Build Run Against
Custom field – description above.
Test Case Prepare Screen
This is workflow screen but we must create it first. Test case life cycle is longer than one application version test process, so we must have the chance to modify some properties when doing test planing.
- Affects Version/s
- Due Date
- Assignee
- Priority
Test Case Step Screen
Default screen for create and edit test case step subtask.
- Summary
Test activity to do by tester. - Description
Expected results / behaviors. - Issue Type
- Attachment
We can add files on that screen but also screen shots JIRA feature is very helpful at this point. - Build Run Against
4. Workflow announce
Just a glimpse, description in the part 3 – comming soon…
Good article! We are new Jira users. We chose Jira mostly to manage our trouble tickets with our customers. This gives me an approach to use it for our QA process overall.
One thing I suggest you add to the workflow is a way to support operational test data. For example, as one tests an application from development, to testing, to staging, to production the test data changes too.
-Frank
Test case step process is interesting. Will the aggregated test results from the steps be rolled up to give the overall test case result or will it be a manual part of the test management process to update the overall test case result?
Was wondering if that Came with the Self Hosted Package of JIRA or if it was a separate module and what are the costs associated with it?
I found your post very interesting. I have been able to follow your posts but I found missing details like the screens linking and related stuff. Maybe I’m just a JIRA newbie but couldn’t figure out how to link all that. Also an example on how to create Test Cases for an existing project would be great!