Wednesday, August 10, 2016

Test Case Management using JIRA Customization - Version 2.0

In the last Post we have seen how we can do Test Management by creating a Custom field "Test Status at Build". But due to change in requirements I tried another approach.

 Now go to Issues page from JIRA Administration->Issues as shown in below picture

Then Add Issue Type like below

Now go to Issue Type Schema and associate it with some Issue Type Schema

Now go to Workflows and Import from Marketplace a new Workflow called "Test Case Management Workflow" 

Assign this workflow to Workflow Scheme at Workflow Schemes and Assign "Test Case" issue type to this Workflow Scheme

Add a new Screen 

Now Add a New Screen Scheme

Associate Issue Type with a Screen Scheme

Create following Custom Fields and associate with Screens

  • In JIRA Project will be top level entity
  • Every Project will be having several Components
  • Stories will be created per Project and will be associated with one or more Components
New IssueType called Test Case added into JIRA with CFs 

Screen Shot 2016-08-10 at 6.49.32 PM.png

Requirement Traceability

Test Case should be linked to Requirement

Screen Shot 2016-08-10 at 6.48.18 PM.png

 This allows Requirement Traceability

Screen Shot 2016-08-10 at 6.47.01 PM.png

Test Cases for Different Platforms(OS)

Screen Shot 2016-08-10 at 3.55.43 PM.pngScreen Shot 2016-08-10 at 3.57.06 PM.png

Test Cases for Different Platforms(OS)

  • Create Test Case for a Platform and upon review Clone them if Test Steps are same for all the Platforms
  • Create Different Test Cases for different Platforms if they are platform dependent Test Cases
  • Link a Test Case of different Environments

Screen Shot 2016-08-10 at 3.58.21 PM.png

Test cycle creation

Screen Shot 2016-08-10 at 4.01.08 PM.png

Clone Regression Tests from Previous Test Cycle

  • Get All Test Cases from Test Case Repository which are not invalid
  • Clone them
  • Change the Test Cycle and Assign them

Assign Test Cases for Execution - Using JQL and Bulk Upload

Screen Shot 2016-08-10 at 4.03.30 PM.png

Test case assignment for automation

  • Change Automation Status as “To be Automated” in Test Case
  • Create a Sub-Task for Test Case
  • Add to appropriate Test Cycle
  • Assign it to a QA Engineer

Test cycle execution assignments
Screen Shot 2016-08-10 at 4.07.31 PM.png
Automation assignments
Screen Shot 2016-08-10 at 4.09.27 PM.png
User Dashboard
Screen Shot 2016-08-10 at 4.14.01 PM.png
Test Execution
Screen Shot 2016-08-10 at 4.15.58 PM.png
Automation Activity

  • QA Engineer looks at User Dashboard for Automation ActivitiesScreen Shot 2016-08-10 at 4.18.41 PM.png
  • QA Engineer will put it in Progress
  • Complete it and mark it as Done
  • Change Automation Status as “Automated” in Test Case
  • Update “Automation Code” with Fully Qualified Class Name and @Test Method Name

Test progress in a Test cycle
Screen Shot 2016-08-10 at 4.20.13 PM.png

Test progress at Component level
Screen Shot 2016-08-10 at 4.22.55 PM.png

Test progress at Feature Level
Screen Shot 2016-08-10 at 6.50.13 PM.png

Automation Progress
Screen Shot 2016-08-10 at 4.24.41 PM.png

Test execution report with teststeps
Screen Shot 2016-08-10 at 4.27.12 PM.png

No. of Test Cases added in Latest Release
Screen Shot 2016-08-10 at 4.28.56 PM.png

No. of Regressions across Versions

  • Bug should be linked to Test Case with “is regressed by” link type, if it a regression Bug.
  • If not it should be linked to Test Case with “is caused by”

Screen Shot 2016-08-10 at 4.38.55 PM.pngScreen Shot 2016-08-10 at 4.42.14 PM.png

No. of regressions within Release
Screen Shot 2016-08-10 at 4.44.06 PM.png

Test execution history for a Test Case

Add-ons Required

Issue Links Used
Screen Shot 2016-08-10 at 6.52.11 PM.png

Filters Used
Filter Name
Bugs with Test Cases
project = MFS AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0"
Test Case Repository
project = MFS AND issuetype = "Test Case" AND (linkType not in (clones) OR linkType is EMPTY)
Test Cases Added in Latest Version
project = MFS AND issuetype = "Test Case" AND affectedVersion = "Version 4.0"
Test Cases Caused Regression
project = MFS AND linkType = regresses AND issuetype = "Test Case"
Test Cases With Open Bugs
project = MFS AND issuetype = "Test Case" AND status = "TC - Failed" AND linkedIssueType = Bug AND linkedIssueStatus = "To Do"
Test Execution of Latest Test Cycle
project = MFS AND issuetype = "Test Case" AND "Test Cycle" = "Version 4.0 - Cycle 1"
Requirement Traceability
project = MFS AND issuetype = Story AND linkType = "is requirement of"
All Bugs with Test Cases
project = MFS AND (linkType = "is caused by" OR linkType = "is regressed by") AND issuetype = Bug AND affectedVersion = "Version 3.0"
Automation Progress
project = MFS AND issuetype = Sub-task AND "Test Cycle" = "Version 4.0 - Cycle 1"
Regression Bugs with Test Cases
project = MFS AND linkType = "is regressed by" AND issuetype = Bug AND affectedVersion = "Version 3.0"


1 comment:

  1. Hi Yagna,

    On behalf of Test Triangle, I am pleased to invite you to our Meetup that will be held on November 10th, 2016.

    We would be delighted to have your presence at this conference to hear what the technology gurus and researchers have to share about the JIRA Agile Project Management and their impact on your business.

    We would also love to hear your thoughts and opinions.

    Please find the below link for the meetup:

    Kindly respond to this invitation before November 1st, 2016 to secure a place.

    We look forward to your confirmed presence at the conference.