Examples

Test Case Management in JIRA #3

Last but not least part of JIRA test case management tutorial, sorry for some time shift but when You provide new technology it accommodates for a while.

First let’s do some wrap-up:
Test Case Management in JIRA #1
Test Case Management in JIRA #2

Below You find last miles on the road to fine test case management in JIRA.

Statuses
Some statuses with some description and icons, add missing ones to your JIRA installation.

  • New
    When test case is created
  • Open
    When test case is waiting for planning
  • Dropped
    When test case is wrong or out of date
  • Planned
    When test case is ready to run
  • In Progress
    When test case is in tester hands
  • Reopened
    When test case must be changed due to functionality
  • Closed
    When test case is completed for current software version
  • Verification
    When test case is ready to verify by business owner or test manager
  • Pass
    When test case step is good and executed
  • Failed
    When test case step is bad and executed

Workflows

Test Case Workflow
Main workflow for our needs, eight steps shown below.
jira_test_case_workflow
and the diagram:

jira_test_casefinal1
After successful create we need to add it to test case issue type in JIRA workflow scheme.

Test Case Step Workflow
Three steps very simple but important:

jira_test_case_step_workflow
Test Case Result Workflow
Again very simple but important :):
jira_test_case_result_workflow

Closing comments
Workflows need to be connected with issue types and screens then to projects etc. I already have these solutions working, so wait for tester and test manager comments.
Let me know your test case management solutions, especially in JIRA.

Discussion

7 comments for “Test Case Management in JIRA #3”

  1. Hi,

    First of all congratulations and thanks for your posts. I’ve just over read your posts and I was thinking if you have tried your workflow and what about your experience. I am worried about how to manage new executations about test plan and how to manage the buids.

    Thanks for all.

    Marta

    Posted by Marta | March 3, 2010, 12:51 pm
  2. Hi Marta,

    Thanks for a comment. Great to hear I’ve helped someone :)

    If you have any QA questions, just ask…

    regards
    Marcin

    Posted by Marcin Zręda | March 3, 2010, 2:01 pm
  3. Thanks for the great articles! Can you tell how is it works? If you are using thing for now, i think you cant tell about some improvements?

    Posted by Alex | March 9, 2011, 8:11 am
  4. Hi Marcin,

    Thank you for your posts, the three combined gives a good high level overview.

    Can you share more details about how to execute tests and record results from release to release?

    Thanks
    Jitendra

    Posted by Jitendra Barlinge | May 24, 2011, 5:03 am
  5. I completely new to JIRA. 1st week of learning and coming from QTP world. From waterfall to agile. Can you please share more on how your TCM using JIRA has been. OR if any more info that explains more of agile TCM using JIRA.

    Thanks!

    Posted by Sanjeev Singh | December 18, 2011, 12:56 am
  6. I know this article is dated but I’m doing research on JIRA and TCM and stumbled onto it. Now that JIRA is a bit more mature I’d be curious if you have any additional insight into how you’d use JIRA today for TCM.

    Right now we use epics and user stories. User stories move along a board with the usual suspects as their statuses. To-Do through Testing and of course done.

    Right now once development has completed a feature they put the story associated with the feature into the Testing lane. We link a confluence page with acceptance criteria to the user story.

    Given that setup, how would QA create test cases and complete them? As separate issues, subtasks on the user story or some other means.

    Posted by Hans Grueber | November 1, 2016, 9:17 pm
  7. Hi, thanks for a question. Regarding today JIRA features like Agile boards etc. I think that test cases should be separate issues, linked with features, stories. Why ? To create some kind of product test book, reachable from everywhere, easily to read and run, grouped into komponents or parent TC tasks. Such book should live with product updates so you can create reports shows which of TC should be changed after new stories around features.

    Posted by admin | November 2, 2016, 8:05 am

Post a comment