Bugtracking

Test Case Management in JIRA #1

testcasesOnce you have ready and running JIRA instance, which deals with our products issue handling, we would like to do more, especially we have free and waiting great Enterprise version features like custom workflows, plugins, user defined fields, etc. Often issue handling process is placed inside quality assurance department, which manages the tests, if we have tests we have test cases too, how to administrate them in JIRA environment? Can be successful? Let’s see:)

For now I found a several white papers on the web, which covers the subject but none of them is a complete solution. My idea is based on the following articles:

in series of articles on my blog I will try to digest the problem, starting from requirements, through design, to implementation. Wish me a success :)

As in every project we have to have a list of requirements which meet the target solution, I will try to determine them for a very broad spectrum.

Test Case Management can be divided into five activities:

1. Test Case Creation
2. Test Case Planning
3. Test Case Execution
4. Test Case Reporting
5. Test Case Change Management

Now let’s try to identify the requirements in a simple manner.

1. Test Case Creation
Dedicated person or group should have the permission to add / edit Test Case with properties:

  • Product / project
  • Version
  • Description
  • Component
  • Priority
  • A list of test steps

Test Case Step should include:

  • Operation to perform – a description
  • Expected outcome – a description
  • Attachments
  • Screenshots
  • A result : Fail or Pass

additional requirement may include the separation of the test case creation / modification and further processing by introducing the need for acceptance. The person in the appropriate project role, usually test manager, should normally accept test cases created or changed, which can then be planned and executed by the testers.
Test Case Steps should have the possibility to set the order of theirs execution.

2. Test Case Planning
Dedicated person or group should have permission to plan Test Case throughout:

  • An indication of the date of which is to be done
  • Identification the person who will perform the test
  • Identification the version of targeted product
  • Add comment
  • Determine priority

Only after the planning process the assigned tester can performs the test steps. Tester shall be notified by e-mail about a given test case.

3. Test Case Execution
People in a given project role can perform each test case step. The beginning of the test execution should be explicitly marked, each step test can be either Passed or Failed. In the case of failure need to add a comment about reason of incorrect operation.

Tester executes test steps in order, marking them as Passed or Failed. After all steps are completed he has the possibility to finish entire test with Pass or Fail result.

4. Test Case Reporting

Quality Assurance department should have access to the following reports:

  • The number of tests by the product version
  • The number of tests completed successfully / unsuccessful
  • The amount of time needed to execute a list of test cases – hard to determine
  • How many cases remain and how much has been realized by version or date

5. Test Case Change Management

The actual production hundreds of test scenarios are worth nothing without further supervision of compliance with the real, changing software functionality. The test case workflow should allow “Change” status, Test Manager makes a change request to testers or analysts. Once again, provided change requires test manager acceptance.
You cannot request change when test case is running or scheduled.

In next part I will try to draw some workflow diagrams and describe detailed implementation on JIRA Enterprise platform with a bunch of additional.

In third part I will try to simultate real world example based on my implementation.

Discussion

8 comments for “Test Case Management in JIRA #1”

  1. [...] 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 : http://www.testandtry.com/2009/07/01/test-case-management-in-jira-1/ [...]

    Posted by Test Case Management in JIRA #2 | Test And Try | July 31, 2009, 11:07 am
  2. [...] let’s do some wrap-up: Test Case Management in JIRA #1 Test Case Management in JIRA [...]

    Posted by Test Case Management in JIRA #3 | Test And Try | October 17, 2009, 11:42 am
  3. I like the way you analyze these tools and systematically explain your thought process.

    Please consider posting a post with a link to this review (and your other two posts on JIRA) at http://testing.stackexchange.com/questions/3/what-is-the-best-free-test-management-tool-and-why

    Thank you!

    Justin Hunter
    Founder of
    http://testing.stackexchange.com (a Q&A forum for testers)
    and
    http://hexawise.com (a simple but sophisticated software test case generator for black box test design)

    Posted by Justin Hunter | November 3, 2009, 6:28 pm
  4. [...] subject on this blog, it is great and proves the importance of such tools. In article titled “Jira Test Case Management” I have described my idea of the test management software structure based on JIRA architecture. [...]

    Posted by TestRail – Web 2.0 Test Case Management Review | Test And Try | May 3, 2010, 10:05 am
  5. I completely agree with your break down into Test Case Creation, Planning, Execution, Reporting
    and Change Management categories. From my experience though I’ve only really been able to work the defect/test validation process into Jira with any great success. Diagram of the procss implemented can be found here
    http://www.softwaretestingclub.com/forum/topics/online-defect-tracking?xg_source=activity

    Posted by Bill Echlin | July 30, 2010, 3:57 pm
  6. QMetry test management software provides a good integration with JIRA. Following are some features.

    * Create a New QMetry test case from a JIRA Issue
    * Create a new JIRA Issue from QMetry test case/requirement
    * Link an existing JIRA Issue to an existing QMetry test case/requirement
    * Add custom JIRA fields in QMetry
    * Update JIRA Issue from QMetry
    o Update the Issue status
    o Add attachments
    o Add comments
    * Search for JIRA issues from QMetry and link test cases and requirements
    * Advanced reports

    You can get a free demo of the this integration at http://www.QMetry.com or by writing to sales@qmetry.com

    Posted by Software Tester | February 6, 2011, 8:09 pm
  7. Can the following be done?

    The main task is for a new feature request.

    This main task will have sub tasks as follows

    - A sub task for approval department (with its own workflow)
    - A sub task for development (with its own workflow)
    - A sub task for QA where the test case managment task (as you have outlined in your article) will be included.

    Thanks

    (JIRA newbie)

    Posted by Evaluating JIRA | April 11, 2012, 2:33 pm
  8. The various test cases that should be automated are:
    • Frequent test cases
    • Cases that can be easily automated
    • Cases where the result can be predicted
    • Manual cases that are tedious
    • Cases that are impossible to manually perform
    • Cases that require several different configurations, software platforms and hardware
    • Cases that have frequently used functionalities

    Posted by Stephanie Reinhardt | November 12, 2016, 7:22 am

Post a comment